cos-upload — Claude Code skill: what it does, how to install
cos-upload uploads local files to AceData Cloud CDN and returns a public URL for downstream APIs or asset sharing.
Apache-2.0 211 installs ★ 17 updated 2026-10-25
npx skills add AceDataCloud/Skills --skill cos-upload -a claude-codeWhat cos-upload does
Sends a local image, video, or document to https://platform.acedata.cloud/api/v1/files/ via a synchronous multipart POST request. The service stores the asset under an uploads/<uuid> path and provides a public file_url on AceData CDN.
Each request handles one file, with a default size ceiling of 100 MB. Authentication requires ACEDATACLOUD_PLATFORM_TOKEN rather than individual service keys.
Uploaded URLs are completely public without authentication, so sensitive data must stay off this endpoint. Storage follows platform retention rules rather than acting as a permanent archive.
What it helps with
- Upload local files to AceData CDN to pass URLs into other APIs
- Send a generated still into image-to-video services like Kling or Seedance
- Persist intermediate run outputs so subsequent tasks can fetch them
- Publish a rendered video or image to get an accessible web link
Example prompts for the agent
- Upload
cover.pngto AceData Cloud and return the CDN URL - Push
render.mp4to the files endpoint so I can pass it to Kling - Upload the generated audio file
speech.mp3to AceData CDN
How to install cos-upload
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill cos-upload -a claude-code2Manually: put the files in place
~/.claude/skills/cos-upload/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cos-upload/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill cos-upload -a codex2Manually: put the files in place
.agents/skills/cos-upload/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill cos-upload -a cursor2Manually: put the files in place
.cursor/skills/cos-upload/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/cos-upload2Manually: put the files in place
.github/skills/cos-upload/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill cos-upload -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/cos-uploadManually: put the files in place
.devin/skills/cos-upload/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill cos-upload -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cos-upload
How to install cos-upload in Claude Code?
Run npx skills add AceDataCloud/Skills --skill cos-upload -a claude-code in your terminal.
What does cos-upload do?
It sends a local file to the AceData Cloud platform endpoint via multipart curl and returns an accessible CDN link.
What credentials and limits apply to uploads?
You need ACEDATACLOUD_PLATFORM_TOKEN set in your environment; requests take one file at a time up to the default 100 MB limit.
Source text
SKILL.md · Apache-2.0
--- name: cos-upload description: Upload a local file to AceData Cloud CDN and get back a public URL. Use whenever you produce a local artifact (image, audio, video, doc) that another API needs as a URL, or that you need to return/persist (e.g. feed a generated image into an image-to-video API, or publish a finished video). license: Apache-2.0 metadata: author: acedatacloud version: "1.0" compatibility: Requires ACEDATACLOUD_PLATFORM_TOKEN (see _shared/authentication.md). Some runtimes instead provide a bundled uploader — prefer that when present. --- # Upload a file → AceData CDN URL Turn a local file into a public `https://cdn.acedata.cloud/...` URL. ## Upload (multipart, synchronous) ```bash curl -s -X POST https://platform.acedata.cloud/api/v1/files/ \ -H "Authorization: Bearer $ACEDATACLOUD_PLATFORM_TOKEN" \ -F "file=@/path/to/video.mp4" ``` On HTTP 200, use the returned `file_url` rather than constructing a URL. The platform generates a unique `uploads/<uuid>` path and preserves the uploaded filename's safe extension. The returned `mime` is the MIME type written to object-storage metadata. One file per request (loop for several); the default limit is 100 MB per file. Use a filename whose extension matches the actual content. The upload part's MIME type is stored as supplied; if omitted or `application/octet-stream`, the platform infers it from the filename using standard MIME mappings. Neither extension handling nor MIME inference converts the file's bytes. ## When to use - **Feed a generated asset into another API by URL** — e.g. upload a gpt-image-2 still, then pass its URL to `seedance` / `kling` image-to-video. - **Publish/return a finished artifact** (final video, cover image). - **Persist intermediate artifacts** so a later run can re-download and continue. ## Notes - Auth uses the **platform token** (`ACEDATACLOUD_PLATFORM_TOKEN`), not the per-service API token — the files endpoint is on `platform.acedata.cloud`, not `api.acedata.cloud`. - If your runtime ships a bundled uploader (e.g. a worker that owns the storage creds), prefer it — it avoids handling the platform token directly. - The returned URL is publicly accessible without authentication; do not upload sensitive data. Retention follows the platform's current storage policy, not a permanent-archive guarantee; use your own object storage for long-term archiving.
© acedatacloud · Apache-2.0 · AceDataCloud/Skills