Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/signal-write
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.
Passed 19 of 20 test cases with the skill, and 4 of 20 without it.
and 30 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When custom tooling reads signal JSON files generated under .signals/, which field should be checked first for specific signal state before falling back to signal_type?
| Checked | Without skill | With skill |
|---|---|---|
| The answer states that subtype should be checked first. | Missed | Passed |
The instructions your model reads when the skill loads.
Emit structured signals from a desk to the operator or other desks.
hands-upTwo desks disagree and can't settle it against external facts. This is the system working — the operator reads where desks disagree, not where they perform confidence.
blockedA desk can't proceed without input — missing access, ambiguous scope, need a decision only the operator can make.
doneWork is complete and ready for review. Artifacts are on the bench.
checkpointSignificant progress worth the operator knowing about, but work continues. Not blocked, not done — just a marker.
partnershipUsed by the TA (room coordinator) to report coordination quality. Self-assessment scores reflect coordination, not code accuracy:
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.