Agent skill
ralph-signal-mailbox-protocol
Ralph-v2 live signal mailbox protocol for polling, ack handling, broadcast quorum, and signal routing. Use when a Ralph agent needs to process `signals/inputs`, write ack files, route target-specific signals, or finalize broadcast signals safely.
Install this agent skill to your Project
npx add-skill https://github.com/arisng/github-copilot-fc/tree/main/skills/ralph-signal-mailbox-protocol
SKILL.md
Ralph Signal Mailbox Protocol
This skill contains the authoritative live-signal mailbox rules for Ralph-v2 agents.
Signal Artifacts
- Inputs:
.ralph-sessions/<SESSION_ID>/signals/inputs/ - Acks:
.ralph-sessions/<SESSION_ID>/signals/acks/ - Processed:
.ralph-sessions/<SESSION_ID>/signals/processed/
Recognized Signal Types
STEERPAUSEABORTINFO
Target Namespace
ALLOrchestratorExecutorPlannerQuestionerReviewerLibrarian
Never encode runtime or version in target.
Poll-Signals Routine
- Ensure
signals/acks/exists. - Read
signals/inputs/in timestamp order. - For each candidate signal, inspect
typeandtargetbefore moving it. - Handle
target: ALLby writing or refreshingsignals/acks/<SIGNAL_ID>/<Agent>.ack.yamland leaving the source signal in place. - Archive a broadcast signal only after ack quorum is satisfied for all required recipients.
- For targeted signals:
ABORTblocks work immediately.PAUSEwaits.STEERchanges execution context.INFOinjects additional context.
- Route target-specific signals to the named subagent by buffering context and moving the original file to
signals/processed/.
Broadcast Invariant
- The first agent that reads
target: ALLnever archives it. - Every recipient writes exactly one ack file per signal ID.
- Only the Orchestrator archives the broadcast signal after quorum is met.
Completion Hygiene
Before a session ends, the Orchestrator should sweep remaining target: ALL signals and archive them with either:
delivery_status: delivereddelivery_status: partialplusunacked_agents
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
fleet
Multi-iteration parallel subagent orchestrator for Kimi Code CLI with streamlined observability, automated documentation, and atomic commits. Use when orchestrating complex work across multiple subagents, enabling parallel execution, or when explicitly requesting fleet mode with '/flow:fleet'. Integrates diataxis documentation and git-atomic-commit workflow.
github-pages-deploy
Deploy a static HTML file or static site directory to GitHub Pages. Use when the user wants a durable GitHub-hosted URL for a static page, diagram, report, or generated site, and can provide GitHub authentication via GITHUB_TOKEN or GH_TOKEN.
Didn't find tool you were looking for?