signal-write

Emit structured JSON agent signals to .signals/ directories for dashboard consumption.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill signal-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-write
Source: https://github.com/github/awesome-copilot/tree/main/skills/signal-write
Command: npx skills add https://github.com/github/awesome-copilot --skill signal-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-agent workflows lack a structured way for agents to report state changes like blockers, completion, or disagreements, leaving operators without machine-readable visibility into coordination quality.

Core Features & Use Cases

  • Structured Signal Emission: Write JSON signal files (hands-up, blocked, done, checkpoint, partnership) to a desk's .signals/ directory with ISO 8601 timestamps for dashboard ordering.
  • Self-Assessment Scoring: Include intent, confidence, accuracy, and completeness scores so coordination quality is measurable rather than anecdotal.
  • Outcome Calibration: Pair execution signals with reviewer outcome signals via a shared run_id to compute the honesty gap between self-assessed confidence and delivered quality.
  • Use Case: An agent desk finishes a code review task and emits a done signal with self-assessment scores; a reviewer later emits an outcome signal with the same run_id, and the signals-dashboard displays the calibration gap.

Quick Start

Emit a checkpoint signal for the current desk by writing a JSON file to its .signals/ directory and noting it in the journal.

Frequently Asked Questions about signal-write

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I emit an agent signal for dashboard consumption?

Write a JSON file to the desk's .signals/ directory containing signal_type, subtype, an ISO 8601 UTC timestamp, and self-assessment scores. Also append a short marker to the desk's journal for persistence.

What signal types can an agent emit?

Five signal types exist: hands-up and blocked (escalations), done and checkpoint (execution), and partnership (coordination quality from the TA). The subtype field preserves the specific state while signal_type controls dashboard sort priority.

How does the signals dashboard order signals?

The dashboard orders signals by the ISO 8601 timestamp field and falls back to file mtime only when the timestamp is absent. Since git clones reset mtimes, always include an explicit timestamp.

How do outcome signals measure agent self-assessment accuracy?

A reviewer emits an outcome signal with the same run_id as the execution signal it rates, plus a quality_rating from 0 to 5. The dashboard compares this against the desk's self-assessed confidence to compute the honesty gap.

When should an agent not emit a signal?

Do not signal routine progress or minor preferences. Signals are for state changes affecting the room, and blocked means truly unable to proceed, not merely wanting input when a reasonable default exists.