PricingAPI keys
  • Overview
  • Quickstart
  • Authentication
  • CLI overview
  • Install and update
  • CLI authentication
  • Command reference
  • Configuration
  • Generation workflows
  • Jobs and media inputs
  • Agent skills
  • Security
  • Troubleshooting

CLI

Agent skills

Agent-safe Sume CLI usage patterns and bundled skills install.

We designed the Sume CLI commands to make agent automation explicit and auditable.

Use read-only first

While you plan, use read commands first:

bash
sume doctor --agent --json
sume catalog list --json
sume tools list --json
sume jobs status <job_id> --agent --json
sume jobs result <job_id> --agent --json

Require confirmation for writes

Agents must not create resources without explicit operator confirmation. Agents must not submit paid provider work without explicit operator confirmation.

GateUse for
--confirm-submitNon-paid writes such as job cancellation or asset registration.
--confirm-paidGeneration that can reserve or spend credits (Avatar / Avatar Video).

At this time, the CLI has no submit commands for Image, Video, and Music generation. For those families, agents must call the Developer API. Agents can still use CLI job recovery when it helps.

Redact sensitive output

When automation reads command output, use --agent --json. Where the CLI supports it, agent mode redacts or summarizes URL-like fields and account/workspace details.

Bundled skills

Use these commands to install or refresh the packaged Sume skill in the local agent skill directories:

bash
sume skills list
sume skills install
sume skills update
sume skills export sume
sume skills remove sume

sume skills install writes into .agents/skills or .claude/skills. Use export to examine the source files before a custom install.

MCP for agents

For Cursor/Claude remote connectors, the best choice is hosted MCP (https://mcp.sume.com/mcp). Local sume mcp is not available in current CLI releases. Refer to sume mcp doctor --json and the CLI command reference.

Recommended loop

  1. Examine the catalog and the local readiness.
  2. Use a read-only/schema command to validate the payload.
  3. Before writes or paid work, ask for confirmation.
  4. Submit one bounded job (the CLI for Avatar, the API for Image/Video/Music).
  5. Use the job status/events/result commands to recover.
  6. Summarize the outputs. Do not paste secrets or signed URLs.

On this page

  • Use read-only first
  • Require confirmation for writes
  • Redact sensitive output
  • Bundled skills
  • MCP for agents
  • Recommended loop