Tencent Cloud COS Workflow

What Problem It Solves

In real operations, an agent or script often needs to work directly with Tencent Cloud COS. The concrete tasks are narrow but annoying: upload local files or directories, generate temporary links for artifacts, browse a prefix and perform copy, move, rename, or cleanup operations, upload videos, models, or backups with slicing and concurrency, and diagnose config failures involving credentials, region, bucket, or custom domains. This skill packages those frequent object-storage actions into reusable workflows instead of asking the model to invent SDK calls each time.

How It Works

Execution leans on existing scripts in scripts/. The normal flow first runs scripts/check_config.js to verify required configuration; if essential values are missing, it reports the missing items instead of proceeding with upload or deletion. For specific tasks, the skill selects scripts such as scripts/upload_file.js for single files, scripts/upload_batch.js for directories, and scripts/upload_large_file.js for large-file multipart uploads. scripts/generate_signed_url.js creates temporary signed URLs, scripts/list_objects.js returns a grouped view of objects and folders under a prefix, scripts/manage_objects.js handles deletion, copy, move, rename, and folder creation, while scripts/get_folder_stats.js reports object count, total size, and type distribution. The output is human-oriented: success state, object key, URL, ETag, size, count, and actionable repair hints, rather than raw SDK dumps.

Boundaries

The skill assumes an environment with valid Tencent Cloud COS access. COS “directories” are usually simulated with Prefix and a / delimiter. Deletion, batch deletion, and recursive deletion require explicit scope confirmation; move or rename is often implemented as copy followed by delete, and cross-bucket operations require target permission checks. Signed URLs are time-limited, and public sharing needs separate confirmation. When the user’s intent is vague, such as “delete the old files,” clarify scope before acting instead of assuming bucket, region, or object path.