Individual skill
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). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.
skills/temps-best-practices/SKILL.md
Source commit 9c5f782f466f81a77a4fb3877e19c58c635184c6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 904
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- analytics Repository topic
- ci-cd Repository topic
- deployment-platform Repository topic
- devops Repository topic
- docker Repository topic
- error-tracking Repository topic
- monitoring Repository topic
- open-source Repository topic
- paas Repository topic
- rust Repository topic
- legal Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,356 bytesSKILL.mdcore · 12,356 bytesevals/evals.jsonasset · 3,881 bytesreferences/analytics.mddoc · 10,176 bytesreferences/error-tracking.mddoc · 6,534 bytesreferences/logs.mddoc · 3,444 bytesreferences/metrics.mddoc · 3,388 bytesreferences/opentelemetry-traces.mddoc · 16,840 bytesreferences/runtime-contract.mddoc · 7,278 bytesreferences/telemetry-hygiene.mddoc · 7,039 bytes
Read excerpt
# Temps Best Practices
Best practices for application code that runs on Temps. This skill owns the **runtime contract** and **production observability**; use `temps-cli` for platform operations.
## Required workflow
1. For any deployable application, read [references/runtime-contract.md](references/runtime-contract.md).
2. When any telemetry or replay is enabled, read [references/telemetry-hygiene.md](references/telemetry-hygiene.md).
3. Read only the reference for each observability pillar in scope.
4. Determine the deployment source. For repository builds, inspect and merge `.temps.yaml`; for image/static deployments, inspect the deployment health-path override because no repository config is available.
5. Run the runtime and telemetry verification checklists before considering the work complete.
## Runtime contract summary
