Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/temps-best-practices
Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries).
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 14 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which specific platform token string prefix is authorized for infrastructure metrics ingestion into the platform?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies si_ integration tokens as the authorized token for infrastructure metrics | Missed | Passed |
The instructions your model reads when the skill loads.
Best practices for application code that runs on Temps. This skill owns the runtime contract and production observability; use temps-cli for platform operations.
.temps.yaml; for image/static deployments, inspect the deployment health-path override because no repository config is available.Every web application should expose a dedicated health endpoint. Repository builds configure it in .temps.yaml under the project's effective Temps Root Directory / Docker build context:
health:
path: /healthz
Use health.path; do not rely on the currently parsed-but-unapplied status, interval, timeout, or retries fields. If OpenTelemetry server tracing is enabled, exclude the exact health path from incoming spans and routine access-log/request-metric noise. Keep the route, .temps.yaml, and filters synchronized.
Image and static deployments cannot read .temps.yaml; set the same route through their deployment health_check_path / CLI --health-check-path override instead.
Also require the app to read PORT, bind to HOST/0.0.0.0, align a custom image's EXPOSE, handle SIGTERM, flush telemetry, and exit inside Temps' 10-second shutdown window. See the runtime reference for readiness semantics, scale-to-zero caveats, replicas, migrations, stdout/stderr, and cron authentication.
Temps replaces Sentry + Datadog/Honeycomb + PostHog with one ingestion surface. This section is the map across all five pillars — use it to decide which pillar a signal belongs in, and to find the concrete endpoint/auth/gotcha details for each. It complements, not replaces, the narrower setup skills:
@temps-sdk/react-analytics hook usageGoal: an app in any language gets runtime health, error tracking, and traces working safely.
Temps auto-injects exporter destinations and credentials; it does not install or initialize an SDK. Apps deployed through Temps receive these variables at Docker build time and container runtime, but application instrumentation still has to be installed, initialized, filtered, and verified:
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.