Operate deployments, telemetry, and sandboxes through Temps CLI skills
Use Temps when an agent needs to deploy applications, inspect production telemetry, and manage self-hosted sandboxes through a pinned CLI and bundled skills.
npx skills add agentskillexchange/skills --skill operate-deployments-telemetry-and-sandboxes-through-temps-cli-skills
Use Temps when an agent or platform operator needs a repeatable, supervised workflow for administering a self-hosted application platform from code and telemetry evidence. The workflow centers on selecting an explicit Temps context, using the pinned @temps-sdk/cli runtime, deploying or inspecting a project, reviewing errors, traces, analytics, session replay, monitors, domains, services, backups, sandboxes, MCP servers, or workflow resources, and verifying every state-changing operation with a read-only follow-up command. Invoke this instead of using the dashboard normally when the user wants an agent to carry out platform work from the terminal with auditable commands, explicit target contexts, confirmation gates for risky changes, and source-backed Temps skill instructions. The scope boundary is operator-grade app-platform automation around Temps’ CLI, bundled skills, and self-hosted runtime; it is not a generic PaaS listing, observability product card, Sentry/PostHog/Resend/E2B replacement card, SDK entry, or unrestricted autonomous infrastructure agent.
What this skill actually does
Inputs and prerequisites: Temps server, @temps-sdk/cli, bunx or npx, git repository or deployed project, and configured Temps authentication/context.
Setup notes: Install or access a Temps server, then use bunx @temps-sdk/cli@0.1.36 or npx @temps-sdk/cli@0.1.36. Verify the pinned CLI version, configure a named context with temps login or CI environment variables, use –target-context for agentic writes, and pair each mutation with a read-only verification command.
Source and verification boundary: use https://temps.sh/docs as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.