sume-tools

name	sume-tools
description	Use Sume tooling guidance for MCP setup, CLI schema discovery, skill install/update, Hermes local skill refresh, and Supercomputer-safe tool routing. Use when configuring Sume for agents or deciding which CLI, MCP, hosted MCP, or product-native tool path to use.

Sume Tools

Use this skill for Sume agent setup, MCP toolset selection, schema discovery, and local skill maintenance.

CLI And Skill Setup

sume --version
sume me --json

If sume me --json reports missing_api_key inside Hermes, Telegram, Modal, SSH, CI-like, or another remote/headless terminal, do not run a long foreground login command such as sume login --device --timeout 600 or sume login --no-browser --timeout 600. Hermes/Telegram may not surface intermediate stdout while the CLI polls, and timeout/error logs can retain sensitive auth material.

Start the device login waiter in the background, read the short-lived log after a few seconds, and surface the URL/code only to the requesting user:

login_log="$(mktemp -t sume-login.XXXXXX.log)"
(sume login --device --timeout 600 >"$login_log" 2>&1; echo $? >"$login_log.status") &
login_pid=$!
sleep 4
sed -n '1,80p' "$login_log"

After the user says they approved access, wait for the process and verify auth:

wait "$login_pid"
sume auth status --json
sume me --json
rm -f "$login_log" "$login_log.status"

If background processes or process logs are unavailable, do not start device login. Ask the user to run local sume login, provide SUME_API_KEY through an approved secret channel, or use a supported auth bridge.

Use plain sume login only when the browser is on the same machine as the CLI process. Do not ask the user to paste API keys into chat unless they explicitly choose manual key setup. Do not echo login URLs/codes in final reports, issue comments, PR bodies, persistent logs, or shared transcripts.

For throwaway remote sandboxes, use an ephemeral SUME_CONFIG_DIR or run sume logout after testing because ~/.sume/config.json can persist in snapshots or reused home directories.

sume skills list --json
sume skills install sume --json
sume skills update --json
sume update --check --json

Install focused skills as needed:

sume skills install sume-assets --json
sume skills install sume-brand --json
sume skills install sume-generation --json
sume skills install sume-ads --json
sume skills install sume-reference-analysis --json
sume skills install sume-tools --json

Hermes local experiments should refresh from this registry/source. Do not maintain a separate stale copy of Sume skills.

Schema Discovery

sume tools list --json
sume tools schema <tool_name> --json

Tool schemas include safety flags and MCP execution metadata. Treat them as the source of truth for inputs and gates.

MCP Defaults

sume mcp

Default MCP is read-only and includes account, credits, Brand read, avatars, jobs, Asset Library read, and schemas.

Use explicit gates for other toolsets:

sume mcp --toolsets brand --allow-write
sume mcp --toolsets uploads --allow-write
sume mcp --toolsets downloads --allow-write
sume mcp --toolsets generation --allow-paid
sume mcp --toolsets ads,face-swap --allow-paid

Read references/mcp-toolsets.md before enabling non-default toolsets.

Supercomputer Boundary

Prefer product-native Supercomputer tools when Sume provides them. Use local CLI/MCP only for public API workflows. Do not call internal Sume routes, DBs, Railway services, provider APIs, or hidden private tools.

Not For

Do not use this skill to execute paid generation or uploads directly. Use it to choose and configure the correct tool path, then use the workflow-specific skill.