القائمة
Set up and verify Sume CLI authentication safely, including browser login, API-key readiness, doctor checks, and headless-terminal caveats without exposing secrets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create, batch-plan, watch, inspect, and select current Sume Avatar 1.0 resources by avatar_handle with safe paid gates and agent-redacted readback.
Create, batch-plan, watch, and inspect Sume Avatar Video 1.0 jobs from selected avatar handles, including productless/product-image flows, metadata readback, and paid gates.
Run the fastest safe Sume Avatar/Avatar Video iteration loop using async submits, batch state files, parallel polling, deferred downloads, and explicit quality/cost tradeoffs.
Router for current Sume.com public API workflows. Use for auth, schema discovery, Avatar 1.0, Avatar Video 1.0, jobs, spend-capped dogfooding, minimum-latency generation loops, media QA, and selecting focused Sume skills.
Run paid Sume dogfood QA under an explicit USD cap using idempotency, max_spend_usd where available, cost readback, and no duplicate paid submissions.
Use advanced compatibility Sume asset upload/download helpers only when explicitly requested; launch Avatar and Avatar Video inputs should use stable public HTTPS URLs directly.
| name | sume-auth |
| description | Set up and verify Sume CLI authentication safely, including browser login, API-key readiness, doctor checks, and headless-terminal caveats without exposing secrets. |
Use this skill for local CLI readiness, login, and API-key configuration.
sume --version
sume auth status --json
sume doctor --agent --json
Use browser login only when the browser is on the same machine as the CLI process:
sume login
sume auth status --json
In remote/headless terminals, avoid long foreground login waiters because
approval URLs/codes can be hidden until timeout or retained in logs. Use the
short-lived process-log pattern in sume/references/safety.md, surface the
approval URL/code only to the requesting user, and delete logs after approval.
Prefer approved local config or environment variables. Do not ask the user to paste API keys into chat unless they explicitly choose manual key setup.
Do not run paid generation, uploads, downloads, MCP setup, or production infrastructure work from this skill. Do not print auth URLs/codes, API keys, or local config contents in final reports, issues, PRs, or persistent logs.