# Temps CLI

Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx.

- Repository: https://github.com/gotempsh/temps (887 stars)
- Category: DevOps
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add gotempsh/temps --skill temps-cli -g -a claude-code -y`
Codex: `npx skills add gotempsh/temps --skill temps-cli -g -a codex -y`
Cursor: `npx skills add gotempsh/temps --skill temps-cli -g -a cursor -y`
Gemini CLI: `npx skills add gotempsh/temps --skill temps-cli -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

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.38 --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.38 <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/WORKFLOWS.md](references/WORKFLOWS.md).

## Safety contract

The rest: https://github.com/gotempsh/temps/blob/HEAD/skills/temps-cli/SKILL.md