aliyun-oss-ossutil
Use when installing, configuring, or operating Alibaba Cloud OSS from the command line with ossutil 2.0, based on the official ossutil overview.
What this skill does
Category: tool # OSS (ossutil 2.0) CLI Skill ## Validation ```bash python skills/storage/oss/aliyun-oss-ossutil/scripts/check_ossutil.py --output output/aliyun-oss-ossutil/validate.txt ``` Pass criteria: command exits 0 and `output/aliyun-oss-ossutil/validate.txt` is generated. ## Output And Evidence - Save command outputs, object listings, and sync logs under `output/aliyun-oss-ossutil/`. - Keep at least one upload or listing result as evidence. ## Goals - Use ossutil 2.0 to manage OSS: upload, download, sync, and resource management. - Provide a unified CLI flow for install, config, credentials, and region/endpoint handling. ## Quick Start Flow 1. Install ossutil 2.0. 2. Configure AK/SK and default region (`ossutil config` or config file). 3. Run `ossutil ls` to list buckets, then list objects using the bucket region. 4. Execute upload/download/sync or API-level commands. ## Install ossutil 2.0 - See `references/install.md` for platform-specific install steps. ## Configure ossutil - Interactive configuration: ```bash ossutil config ``` - Default config file paths: - Linux/macOS:`~/.ossutilconfig` - Windows:`C:\Users\issuser\.ossutilconfig` Main configuration fields include: - `AccessKey ID` - `AccessKey Secret` - `Region`(example default `cn-hangzhou`; ask the user if the best region is unclear) - `Endpoint`(optional; auto-derived from region if omitted) ## AccessKey configuration notes Use RAM users/roles with least privilege and avoid passing AK in plain text on command line. Recommended method (environment variables): ```bash export ALIBABACLOUD_ACCESS_KEY_ID="<your-ak>" export ALIBABACLOUD_ACCESS_KEY_SECRET="<your-sk>" export ALIBABACLOUD_REGION_ID="cn-beijing" ``` `ALIBABACLOUD_REGION_ID` can be used as default region; if unset choose the most reasonable region, ask user if unclear. Or use the standard shared credentials file: `~/.alibabacloud/credentials` ```ini [default] type = access_key access_key_id = <your-ak> access_key_secret = <your-sk> ``` ## Command structure (2.0) - High-level command example:`ossutil config` - API-level command example:`ossutil api put-bucket-acl` ## Common command examples ```bash ossutil ls ossutil ls oss://your-bucket -r --short-format --region cn-shanghai -e https://oss-cn-shanghai.aliyuncs.com ossutil cp ./local.txt oss://your-bucket/path/local.txt ossutil cp oss://your-bucket/path/remote.txt ./remote.txt ossutil sync ./local-dir oss://your-bucket/path/ --delete ``` ## Recommended execution flow (list buckets first, then objects) 1) List all buckets ```bash ossutil ls ``` 2) Get target bucket region from output (e.g. `oss-cn-shanghai`) and convert it to `--region` format (`cn-shanghai`). 3) When listing objects, explicitly set `--region` and `-e` to avoid cross-region signature/endpoint errors. ```bash ossutil ls oss://your-bucket \ -r --short-format \ --region cn-shanghai \ -e https://oss-cn-shanghai.aliyuncs.com ``` 4) For very large buckets, limit output size first. ```bash ossutil ls oss://your-bucket --limited-num 100 ossutil ls oss://your-bucket/some-prefix/ -r --short-format --region cn-shanghai -e https://oss-cn-shanghai.aliyuncs.com ``` ## Common errors and handling - `Error: region must be set in sign version 4.` - Cause: missing region configuration. - Fix: add `region` in config file, or pass `--region cn-xxx`. - `The bucket you are attempting to access must be addressed using the specified endpoint` - Cause: request endpoint does not match bucket region. - Fix: use endpoint of the bucket region, e.g. `-e https://oss-cn-hongkong.aliyuncs.com`. - `Invalid signing region in Authorization header` - Cause: signature region does not match bucket region. - Fix: correct both `--region` and `-e`; both must match bucket region. ## Credential and security guidance - Prefer RAM user AK for access control. - CLI options can override config file, but passing secrets on command line has leakage risk. - In production, manage secrets via config files or environment variables. ## Clarifying questions (ask when uncertain) 1. Is your target a Bucket or an Object? 2. Do you need upload/download/sync, or management actions like ACL/lifecycle/CORS? 3. What are the target region and endpoint? 4. Are you accessing OSS from ECS in the same region (intranet endpoint may be preferred)? ## References - OSSUTIL 2.0 overview and install/config: - https://help.aliyun.com/zh/oss/developer-reference/ossutil-overview - Official source list:`references/sources.md` ## Prerequisites - Configure least-privilege Alibaba Cloud credentials before execution. - Prefer environment variables: `ALIBABACLOUD_ACCESS_KEY_ID`, `ALIBABACLOUD_ACCESS_KEY_SECRET`, optional `ALIBABACLOUD_REGION_ID`. - If region is unclear, ask the user before running mutating operations. ## Workflow 1) Confirm user intent, region, identifiers, and whether the operation is read-only or mutating. 2) Run one minimal read-only query first to verify connectivity and permissions. 3) Execute the target operation with explicit parameters and bounded scope. 4) Verify results and save output/evidence files.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.