跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
部署与云服务

Temps

The PaaS you actually own

gotempsh · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add gotempsh/temps

技能说明


name: temps description: Manage, deploy, operate, and instrument applications with Temps. Use this skill whenever the user mentions Temps, @temps-sdk/cli@0.1.36, deploying or migrating an app to Temps, projects, environments, services, domains, backups, logs, monitoring, analytics, browser Performance Insights/Core Web Vitals, observability, error tracking, OpenTelemetry, tracing, session replay, or Temps Cloud. Also use it when preparing an application for production on Temps even if the user does not explicitly ask for the CLI. Route to focused references, proactively detect missing observability during create/link/deploy journeys, and use pinned bunx or npx CLI invocations with explicit target contexts.

Temps

Treat Temps as a product workflow, not a command catalog. Understand the user's desired outcome, inspect the application or platform read-only, load only the relevant reference, make the smallest authorized change, and prove the result.

Runtime requirements: a shell and either bunx or npx for CLI operations; Python 3.9+ for the bundled read-only capability detector.

Required workflow

  1. Classify the task: application preparation, deployment, platform operation, observability, recovery, or diagnosis.
  2. Inspect before changing anything. Identify the repository framework, current Temps context, target project/environment, and existing setup.
  3. Read only the references named in the routing table below. Do not load the complete command index or unrelated observability pillars.
  4. For CLI work, use the pinned zero-install invocation and the safety contract in references/cli-runtime.md.
  5. Before a state change, explain its target and effect. Ask for confirmation when the change is destructive, secret-bearing, or otherwise requires new authority.
  6. Verify the outcome using a read-only CLI command, application test, and—when telemetry is involved—a real synthetic signal.

Application capability checkpoint

When creating, linking, migrating, reviewing, or deploying an application, inspect its observability setup before the final deployment step:

python3 skills/temps/scripts/detect_project_capabilities.py --root .

Resolve the script relative to this skill directory when the current working directory is elsewhere. The detector is read-only and reports missing, partial, or configured static evidence for analytics, error tracking, and OpenTelemetry without reading secret values. Treat partial as missing setup, not as working instrumentation.

If one or more capabilities are missing, ask once:

The app is ready for Temps, but I don't see [missing capabilities] configured. Would you like me to add the recommended observability setup, choose individual capabilities, or continue without it?

This checkpoint is an offer, not a deployment gate. Respect a decline for the rest of the task. Do not ask when the project is infrastructure-only, has no application runtime, or the user explicitly scoped observability out.

When the user opts in:

  1. Read howtos/observability-onboarding.md.
  2. Read only the detected framework guide.
  3. Describe dependency and source changes before applying them.
  4. Keep secrets in the platform/secret manager; never request their values in chat or commit them.
  5. Verify one synthetic event/error/span reaches Temps. Package presence alone is not proof of a working integration.

Route by intent

IntentRead
Authenticate, select a server, or execute CLI operationsreferences/cli-runtime.md, then references/commands/INDEX.md
Create, link, deploy, or migrate an applicationhowtos/deploy-application.md, references/runtime-contract.md
Configure a database, cache, or object storehowtos/managed-services.md
Configure, verify, or restore backupshowtos/backup-recovery.md
Diagnose an unhealthy deploymenthowtos/diagnose-deployment.md
Automate Temps from CIhowtos/ci-automation.md
Add or review observability end to endhowtos/observability-onboarding.md, then one framework guide
Add browser/product analyticsreferences/observability/analytics.md
Review Performance Insights, Core Web Vitals, or desktop/mobile speedreferences/commands/analytics.md, then references/observability/analytics.md only when capture/setup also needs review
Add exception capturereferences/observability/error-tracking.md
Add distributed tracesreferences/observability/tracing.md
Add metrics or structured logsreferences/observability/metrics.md or references/observability/logs.md
Diagnose missing/noisy telemetry or review privacyreferences/observability/hygiene.md
Prepare Next.js, React, Vite, or Nodehowtos/javascript-typescript.md
Prepare Pythonhowtos/python.md
Prepare Rusthowtos/rust.md
Use another frameworkhowtos/framework-routing.md

CLI discovery

Do not read a monolithic CLI manual. Open references/commands/INDEX.md, select one command-group file, and confirm uncertain syntax with runtime help:

bunx @temps-sdk/cli@0.1.36 <group> <command> --help

Use npx @temps-sdk/cli@0.1.36 only when Bun

阅读完整来源 ↗