Trader Signal
ruvnet/ruflo
Generate trading signals using npx neural-trader anomaly detection engine with Z-score scoring and neural prediction
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership.
OfficialMITAuto-check passed
Install Signal Write
$ npx skills add github/awesome-copilot --skill signal-write -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot signal-write --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/signal-write .claude/skills/signal-write && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .claude/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/signal-writeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill signal-write -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot signal-write --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/signal-write .agents/skills/signal-write && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .agents/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill signal-write -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot signal-write --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/signal-write .cursor/skills/signal-write && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .cursor/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/signal-write--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill signal-write -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot signal-write --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/signal-write .gemini/skills/signal-write && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .gemini/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot signal-writeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill signal-write -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/signal-write .github/skills/signal-write && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .github/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill signal-write -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot signal-write --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/signal-write .opencode/skills/signal-write && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "signal-write" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/signal-write into .opencode/skills/signal-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-write", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
signal-write- GitHub stars
- 40k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 539 words
- Files
- 1
- Skills in repo
- 417
- Repo updated
- First seen
- Licence
- MIT
At a glance
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership.
- Works in 2 steps: Write a JSON signal file to .signals/ → Note the signal in the journal
- SKILL.md covers When to use, Signal types, How to emit and Outcome signals (calibration), plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Signal Write is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
Example prompts
- “/signal-write”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Signal Write loads about 1.3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 539 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 539 words, ~1,305 tokens.
Download SKILL.mdSave it as
.claude/skills/signal-write/SKILL.md (or your agent's skills folder).- name
- signal-write
- description
- 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.
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 right outcome
- completeness — nothing fell through the cracks
How to emit
1. Write a JSON signal file to .signals/
This is the primary output — it's what the dashboard reads.
Create desks/<desk-name>/.signals/<timestamp>.json:
{
"signal_type": "execution",
"subtype": "checkpoint",
"timestamp": "2026-07-19T21:30:00Z",
"run_id": "<optional; set to pair this with an outcome signal>",
"agent_name": "<desk-name>",
"self_assessment": {
"intent": 4,
"confidence": 5,
"accuracy": 4,
"completeness": 3
},
"patterns": {
"what_worked": "description of what went well",
"what_was_hard": "description of challenges",
"skill_gap": "areas for improvement"
},
"escalation": {
"reason": null,
"blocked_on": null,
"recommendation": null
}
}Signal type mapping
| Signal | signal_type | subtype |
|---|---|---|
| hands-up | "escalation" | "hands-up" |
| blocked | "escalation" | "blocked" |
| done | "execution" | "done" |
| checkpoint | "execution" | "checkpoint" |
| partnership | "partnership" | "partnership" |
The subtype field preserves the specific signal state for
dashboard consumers. signal_type controls sort priority
(escalation → top).
Note: The signals-dashboard canvas extension reads
subtypewhen present and falls back tosignal_typefor display. If consuming signals in your own tooling, prefersubtypefor the specific state.
Ordering: include a
timestamp(ISO 8601 UTC). The dashboard orders signals by it and falls back to file mtime only when it's absent — a git clone/checkout resets mtimes, so mtime alone is not a dependable clock.
2. Note the signal in the journal
Also append a short marker to the desk's journal for persistence:
## <date> — [signal:<type>] <summary>
- <key details>The journal note is the trail marker. The JSON file is the machine-readable signal.
Show full SKILL.md (205 more words)Show less
Outcome signals (calibration)
The signals-dashboard can pair a desk's self-assessment with an outcome — an independent rating of the realized result — and show the honesty gap (how far the desk's confidence was from the delivered quality). Outcome signals are optional and are usually emitted by a reviewer/evaluator, not the desk itself.
Write them to the same .signals/ directory:
{
"signal_type": "outcome",
"run_id": "<same run_id as the signal it rates>",
"agent_name": "<reviewer name>",
"quality_rating": 4,
"effort_to_merge": "minimal",
"issues_found": ["optional short strings"],
"timestamp": "2026-07-19T22:00:00Z"
}run_idcorrelates an outcome with the execution/partnership signal it rates — set the samerun_idon both. If it's absent, the dashboard falls back to the nearest outcome emitted shortly after the latest signal.quality_rating(0–5) is the realized quality; the dashboard compares it to the desk's self-assessedconfidenceto compute the honesty gap.effort_to_merge—"minimal","moderate", or"significant".issues_found— optional array of short strings.
Principles
- Signals are structured, not chatty. Short, factual, actionable.
- hands-up is not failure — it's the most valuable signal. It means the system caught something one frame alone would have missed.
- Don't signal for routine progress. Signals are for state changes that affect the room, not status updates.
- blocked means truly blocked — not "I'd prefer input." If you can proceed with a reasonable default, proceed and note it.
- Self-assessment scores should be honest, not optimistic. A 3/5 is fine. A 5/5 on everything is suspicious.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/signal-write of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
Compare with similar skills
Signal Write next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Signal Write this skillgithub/awesome-copilot | 40k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Trader Signalruvnet/ruflo | 74k | — | ~605 | Automated safety check: Notes | MIT | |
| Render Blockingthedaviddias/Front-End-Checklist | 74k | — | ~430 | Automated safety check: Pass | MIT | |
| Blocking IO Guardbytedance/deer-flow | 83k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Color Blockingsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Agent Signal Pipelinelobehub/lobehub | 83k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Render Blocking
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources.
Blocking IO Guard
bytedance/deer-flow
Adds a runtime test anchor for backend async code that could block the asyncio event loop, and proves the anchor fails when the blocking call returns.
Color Blocking
sickn33/agentic-awesome-skills
Web and App implementation guide for Color Blocking. An agent skill from sickn33/agentic-awesome-skills.
Agent Signal Pipeline
lobehub/lobehub
Guides building event-driven background work for LobeHub agents, with sources, signals, actions, policies, workflow handoff and deduplication.
Checkpoint Promotion
wshobson/agents
Gate fine-tuned checkpoints with drift budgets, paired comparison, and forgetting checks before promotion.
More from github/awesome-copilot
All 417 skills in this repo- Official
Acquire Codebase Knowledge
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
- Official
Draw.io Diagram Generator
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
- Official
Credit Risk Data Cleaning
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
- Official
Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
- Official
Python Pypi Package Builder
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Questions about Signal Write
What does Signal Write do?
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signal Write is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership.
How do I install Signal Write in Claude Code?
Run `npx skills add github/awesome-copilot --skill signal-write -a claude-code`. Or copy the skill folder (skills/signal-write in github/awesome-copilot) into .claude/skills/signal-write in your project. Claude Code loads it when a task matches its description.
How do I install Signal Write in Codex?
Run `npx skills add github/awesome-copilot --skill signal-write -a codex`. Or copy the skill folder (skills/signal-write in github/awesome-copilot) into .agents/skills/signal-write in your project. Codex loads it when a task matches its description.
Can I use Signal Write in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill signal-write -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/signal-write, .gemini/skills/signal-write, .github/skills/signal-write and .opencode/skills/signal-write in your project.
What does Signal Write need to run?
SKILL.md names no scripts, command-line tools or credentials: Signal Write is instructions for the agent only.
Does Signal Write access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Signal Write safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Signal Write use?
Signal Write is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Signal Write use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Signal Write?
Skills that share tags, products or a category with Signal Write: Trader Signal (ruvnet/ruflo, 74k stars), Render Blocking (thedaviddias/Front-End-Checklist, 74k stars), Blocking IO Guard (bytedance/deer-flow, 83k stars) and Color Blocking (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signal Write?
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.