Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/start-temps
Start (or restart) a local Temps control plane built from this checkout, and the web dev server (`bun dev`) in `<checkout>/web`.
Passed 15 of 18 test cases with the skill, and 5 of 18 without it.
and 13 more in the full report
13 fixed5 passed either way3 still failing1 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.
When testing sandbox features locally on macOS using Docker Desktop, network egress rules inside the sandbox fail due to differences in the Linux forwarding plane. What environment variable allows unrestricted sandbox networking for local development?
| Checked | Without skill | With skill |
|---|---|---|
| Sets TEMPS_ALLOW_INSECURE_SANDBOX_NETWORKING to 1 | Missed | Passed |
The instructions your model reads when the skill loads.
Boots the temps binary from source (cargo run --bin temps --package temps-cli -- serve ...) for quick local iteration, no debugger required. See
CONTRIBUTING.md for the one-shot manual version of this; this skill adds
port isolation across worktrees and a repeatable restart flow.
The database container from CONTRIBUTING.md ("Database" section) running
and reachable, e.g.:
docker run -d --name temps-db --restart unless-stopped \
-p 127.0.0.1:5432:5432 \
-v temps-db-data:/home/postgres/pgdata/data \
-e POSTGRES_USER=temps -e POSTGRES_PASSWORD=temps -e POSTGRES_DB=temps \
timescale/timescaledb-ha:pg18
If your container has a different name, user, password, or port, set
TEMPS_DEV_DB_CONTAINER / TEMPS_DEV_DB_URL_BASE before running step 0, or
just edit the generated slot env file afterwards.
bun install already run in <checkout>/web.
Docker running, if you'll exercise features that shell out to it (container deploys, agent sandboxes, etc.) — see the Docker precheck below.
If you keep multiple worktrees of this repo around (one per branch/PR), the
naive approach — hardcode :8080 / :3000 and kill whatever's listening —
means starting temps in worktree B kills the server another session was using
in worktree A. This skill instead assigns each checkout a slot (0–29) and
derives every port from it:
| Thing | Port | Slot 0 |
|---|---|---|
Backend HTTP (--address) | 8080 + slot*10 | 8080 |
Console (--console-address) | 8081 + slot*10 | 8081 |
TLS (--tls-address) | 8443 + slot*10 | 8443 |
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.