360 Secure SkillHub
360 安全技能中心

AWS S3

核心功能：通过oo CLI调用aws_s3连接器，无需直接处理凭证，实现S3桶和对象的增删改查、生成预签名URL等全量操作。典型场景：管理S3存储桶、上传/下载文件、生成临时访问链接。输入为对应动作schema的JSON，输出含数据和执行ID的JSON结构。写操作需用户确认，首次使用需完成CLI安装、登录、连接AWS S3的步骤。

oomol
oomol
热度 56.46
最近更新 2026-09-20 11:23:00
分类：开发依赖：代码执行 / MCP 服务应用场景：API 集成 / DevOps / 数据处理

安装技能

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

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

AWS S3

Operate AWS S3 through your OOMOL-connected account. This skill calls the aws_s3 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 AWS S3. 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 "aws_s3" --action "<action_name>"

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

oo connector run "aws_s3" --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 S3 object. [destructive]
  • download_object — Download one S3 object into connector transit storage.
  • generate_presigned_url — Generate a pre-signed S3 URL for reading, uploading, or deleting one object.
  • head_object — Fetch structured metadata for one S3 object.
  • list_buckets — List Amazon S3 buckets visible to the connected AWS credential.
  • list_objects — List objects in an S3 bucket with the ListObjectsV2 API.
  • put_object — Upload one object to S3 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 AWS S3 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 — AWS S3 is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

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

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

Resources