Temps CLI
Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx.
Install
npx skills add gotempsh/temps --skill temps-cli -g -a claude-code -y- Repository
- gotempsh/temps887
- Category
- DevOps
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,855 tokens
- Runs scripts
- No, instructions only
What it does
Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx. Use when the user mentions Temps CLI, `@temps-sdk/cli`, a CLI command, or asks to deploy, configure, inspect, automate, or administer Temps from a terminal. Covers contexts, projects, deployments, environments, services, domains, monitoring, backups, telemetry, browser Performance Insights/Core Web Vitals, Cloud, platform administration, and read-only managed-data browsing. Apply the target-context, secret-handling, confirmation, and verification rules for every agentic CLI operation.
Temps CLI
Use the pinned zero-install package invocation to operate a Temps server. Prefer
bunx @temps-sdk/cli@0.1.38; use npx @temps-sdk/cli@0.1.38 when Bun is not
available. Treat this skill as procedural guidance and command documentation,
not as authorization to mutate a server.
Required workflow
- Run
command -v bunx || command -v npxto select an available package runner. Preferbunxwhen both exist. - Verify the reviewed package integrity as shown below, then run
bunx @temps-sdk/cli@0.1.38 --version(or its pinnednpxequivalent). Never omit the version. - Identify the requested operation and locate its command in references/COMMANDS.md. Search only the relevant command group instead of loading the entire reference.
- Run
bunx @temps-sdk/cli@0.1.38 <group> <command> --helpwhen flags or behavior may have changed. Runtime help is authoritative. - Classify the operation as read-only, state-changing, destructive, or secret-bearing.
- For every state-changing operation, name the intended server and insert
--target-context <name>immediately after the package specifier. - Explain the expected effect before executing a write. Obtain explicit confirmation for destructive or secret-bearing operations.
- 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/WORKFLOWS.md.
