| name | sume-assets |
| description | Use Sume Asset Library tools to search reusable scene clips, inspect asset metadata, upload local videos for indexing, and download safe public job or asset media. Use when the user asks for existing clips, hooks, product demos, CTA scenes, Asset Library uploads, media retrieval, or local downloads. |
Sume Assets
Use this skill for Asset Library retrieval, upload, and safe download workflows. Sume CLI and MCP schemas remain the source of truth.
Start With Discovery
sume tools schema assets.search --json
sume tools schema assets.get --json
sume tools schema uploads.presign --json
sume tools schema assets.finalize --json
For MCP clients:
sume mcp
sume mcp --toolsets uploads --allow-write
sume mcp --toolsets downloads --allow-write
Default MCP exposes assets.search and assets.get. Uploads and downloads are write-gated.
Read references/media-workflows.md for upload/download and clip/source handling details.
Search Workflow
Search first, then inspect one asset with the original search context.
sume assets search "good hook videos" --source-type generated --max-duration 15 --sort relevance --limit 5 --json
sume assets get <asset_id> --query "good hook videos" --search-mode <mode> --json
Useful filters include --source-type, --segment-type, --brand, --product, --tag, --keyword, --cta-present, --min-duration, --max-duration, and --sort.
Do not pass 0 as a placeholder search score. Include --search-score only when the previous result score is non-null.
Scene Media Semantics
clip_url means a scene-specific playable clip exists.source_media_url means the full source video.- If
clip_url is null, use source_media_url with scene.start_seconds and scene.end_seconds; do not pretend a standalone clip exists.
Upload Workflow
Preferred MCP path for local videos up to 512 MiB:
sume mcp --toolsets uploads --allow-write
Use uploads.asset_video with path, content_type, and optional file_name. MCP handles presign, PUT, and finalize internally and never returns the signed upload URL or object key.
For larger files or shell automation, use CLI presign/finalize:
sume uploads presign --purpose asset_library_video --file-name source.mp4 --content-type video/mp4 --size-bytes 12000000 --json
sume assets finalize --object-key "<object_key>" --file-name source.mp4 --content-type video/mp4 --size-bytes 12000000 --json
Treat upload_url, object_key, and required upload headers as sensitive. Do not print them in reports.
Download Workflow
Use download helpers only when the user wants files on disk.
sume jobs result <job_id> --download ./outputs/ --json
sume assets get <asset_id> --download ./assets/ --json
Do not curl media URLs manually. CLI and MCP download helpers filter unsafe URLs and summarize local files.
Not For
Do not use this skill for creating new paid image/video/ads jobs. Use schema discovery or future generation-specific skills for those workflows.
