temps-cli

# Temps CLI Use the pinned zero-install package invocation to operate a Temps server. Prefer `bunx @temps-sdk/cli@0.1.34`; use `npx @temps-sdk/cli@0.1.34` when Bun is not available. Treat this skill as procedural guidance and command documentation, not as authorization to mutate a server. ## Required workflow 1. Run `command -v bunx || command -v npx` to select an available package runner. Prefer `bunx` when both exist. 2. Verify the reviewed package integrity as shown below, then run `bunx @temps-sdk/cli@0.1.34 --version` (or its pinned `npx` equivalent). Never omit the version. 3. Identify the requested operation and locate its command in [references/COMMANDS.md](references/COMMANDS.md). Search only the relevant command group instead of loading the entire reference. 4. Run `bunx @temps-sdk/cli@0.1.34 <group> <command> --help` when flags or behavior may have changed. Runtime help is authoritative. 5. Classify the operation as read-only, state-changing, destructive, or secret-bearing. 6. For every state-changing operation, name the intended server and insert `--target-context <name>` immediately after the package specifier. 7. Explain the expected effect before executing a write. Obtain explicit confirmation for destructive or secret-bearing operations. 8. Verify the result with a read-only command and report the target context, changed resource, and evidence. Do not report secrets. For common multi-command journeys, read [references/WORKFLOW...