Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
Passed 20 of 21 test cases with the skill, and 6 of 21 without it.
and 12 more in the full report
15 fixed5 passed either way0 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to automate deployment previews and environment provisioning from our GitHub Actions pipelines using Temps. Which reference file contains the instructions for automated CI execution?
| Checked | Without skill | With skill |
|---|---|---|
| References howtos/ci-automation.md for CI pipeline integration. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.