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.
Profile →npx skills add github/awesome-copilot --skill signal-write --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Signals Emit structured signals from a desk to the operator or other desks. ## When to use - A desk needs operator attention (hands-up, blocked) - Work is complete and ready for review (done) - Significant progress worth noting (checkpoint) - Two desks disagree and can't resolve it (hands-up) - The TA is reporting coordination quality (partnership) ## Signal types ### `hands-up` Two 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. ### `blocked` A desk can't proceed without input — missing access, ambiguous scope, need a decision only the operator can make. ### `done` Work is complete and ready for review. Artifacts are on the bench. ### `checkpoint` Significant progress worth the operator knowing about, but work continues. Not blocked, not done — just a marker. ### `partnership` Used by the TA (room coordinator) to report coordination quality. Self-assessment scores reflect coordination, not code accuracy: - **intent** — understood what the operator needed - **confidence** — right work went to the right desks - **accuracy** — dispatched work produced the righ
- When to use
- Signal types
- hands-up
- blocked
- done
- checkpoint
- partnership
- How to emit
- 1. Write a JSON signal file to .signals/
- Signal type mapping
- 2. Note the signal in the journal
- Outcome signals (calibration)
- Principles
What does the signal-write skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill signal-write --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.