360 Secure SkillHub
360 安全技能中心

Alibaba Cloud OSS

该 Skill 通过 oo CLI 调用 OOMOL 的 aliyun_oss 连接器，凭据由服务端注入，用户无需处理令牌。支持列举存储桶与对象、读取对象元数据、上传、下载、删除对象以及生成预签名 URL；其中上传与删除会改变数据状态，需先与用户确认。具体动作的输入字段需先用 schema 命令查询。

oomol
oomol
热度 56.67
最近更新 2026-09-23 18:54:53
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / API 集成 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-aliyun-oss
Metadata
name
oo-aliyun-oss
description
Alibaba Cloud OSS (alibabacloud.com). Use this skill for ANY Alibaba Cloud OSS request — reading, creating, updating, and deleting data. Whenever a task involves Alibaba Cloud OSS, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Alibaba Cloud OSS","author":"OOMOL","version":"1.0.6","services":["aliyun_oss"],"icon":"https://static.oomol.com/logo/third-party/aliyun_oss.svg"}

Alibaba Cloud OSS

Operate Alibaba Cloud OSS through your OOMOL-connected account. This skill calls the aliyun_oss connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Alibaba Cloud OSS. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "aliyun_oss" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "aliyun_oss" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • delete_object — Delete one OSS object. [destructive]
  • download_object — Download one OSS object into connector transit storage.
  • generate_presigned_url — Generate a pre-signed OSS URL for reading, uploading, or deleting one object.
  • head_object — Fetch structured metadata for one OSS object.
  • list_buckets — List OSS buckets visible to the connected Alibaba Cloud credential.
  • list_objects — List objects in an OSS bucket with the ListObjectsV2 API.
  • put_object — Upload one object to OSS from a public URL, plain text, or base64-encoded content. [destructive]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Alibaba Cloud OSS state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Alibaba Cloud OSS is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential, federated) at:

    https://console.oomol.com/app-connections?provider=aliyun_oss

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources