Install any skill in seconds. Free to start, no credit card required.
Get Started Free →blueberrycongee/using-termcanvas
Use when starting work in a TermCanvas-managed repo to route between direct work, Hydra, or a narrow TermCanvas skill.
Passed 12 of 19 test cases with the skill, and 9 of 19 without it.
and 5 more in the full report
6 fixed8 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just dispatched a developer worker for our workflow using `hydra dispatch dev`. What command must be executed immediately next to monitor the worker and pause at the decision point, without waiting or asking the user?
| Checked | Without skill | With skill |
|---|---|---|
| Executes hydra watch immediately after dispatch | Missed | Passed |
The instructions your model reads when the skill loads.
Route first. Choose the lightest path that preserves correctness.
challenge.investigate.security-audit.code-review.qa.hydra.hydra init-repo or the TermCanvas Hydra enable action.Lead-driven, decision-point oriented. The Lead reads the codebase, picks
the strategy, and dispatches workers for the steps that need a fresh
agent process. Roles available: lead (the decider — not itself dispatched),
dev (writes code AND its tests), reviewer (independent cross-model
check). No separate researcher — the Lead does its own research. No
separate tester — dev owns its own test surface.
hydra init --intent "..." --repo . then dispatch dev -> reviewer
for ambiguous, risky, or PRD-driven work
hydra watch after each dispatch to wait for the decision pointhydra spawn --task "..." --repo . for a single isolated worker
hydra spawn --task "..." --repo .
test cases passed, vs 9 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.