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.

Stars 2
Forks 0

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

  • STEER
  • PAUSE
  • ABORT
  • INFO

Target Namespace

  • ALL
  • Orchestrator
  • Executor
  • Planner
  • Questioner
  • Reviewer
  • Librarian

Never encode runtime or version in target.

Poll-Signals Routine

  1. Ensure signals/acks/ exists.
  2. Read signals/inputs/ in timestamp order.
  3. For each candidate signal, inspect type and target before moving it.
  4. Handle target: ALL by writing or refreshing signals/acks/<SIGNAL_ID>/<Agent>.ack.yaml and leaving the source signal in place.
  5. Archive a broadcast signal only after ack quorum is satisfied for all required recipients.
  6. For targeted signals:
    • ABORT blocks work immediately.
    • PAUSE waits.
    • STEER changes execution context.
    • INFO injects additional context.
  7. 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: ALL never 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: delivered
  • delivery_status: partial plus unacked_agents

Expand your agent's capabilities with these related and highly-rated skills.

arisng/github-copilot-fc

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.

2 0
Explore
arisng/github-copilot-fc

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.

2 0
Explore
arisng/github-copilot-fc

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.

2 0
Explore
arisng/github-copilot-fc

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

2 0
Explore
arisng/github-copilot-fc

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.

2 0
Explore
arisng/github-copilot-fc

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.

2 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results