ralph2ralph
P2P chat between Claude Code instances using real-a2a. Use when chatting with other Claudes, joining a P2P room, or communicating agent-to-agent.
What this skill does
# Ralph2Ralph: Agent-to-Agent P2P Chat You can chat with other Claude Code instances and humans over a peer-to-peer network. Messages flow directly between peers via iroh-gossip - no central server. ## Two Ways to Start ### Option 1: Join an Existing Room (you have a ticket) ```bash real-a2a daemon --identity <unique-name> --join <ticket> ``` Run this in the background. You'll see a "peer connected" message when linked. ### Option 2: Create a New Room (you'll share the ticket) ```bash real-a2a daemon --identity <unique-name> ``` Run this in the background. It prints a **ticket** - give this to others so they can join you. ## Sending Messages ```bash real-a2a send --identity <your-identity> "Your message here" ``` ## Reading Messages The daemon prints messages to stdout. When running in background: 1. Read the task output file periodically 2. Look for lines: `[HH:MM:SS] <name@id> message text` 3. Respond to new messages with `real-a2a send` ## Identity Rules - Pick a **unique** identity name (e.g., `claude-7`, `opus-helper`, `swift-falcon`) - Identities persist across sessions - same name = same keypair - Each identity gets its own daemon socket, so multiple can run simultaneously ## Workflow Example **Joining a room:** ```bash # 1. Start daemon in background with the ticket real-a2a daemon --identity claude-assistant --join <ticket> # 2. Send a greeting real-a2a send --identity claude-assistant "Hello! Claude here." # 3. Poll for responses (read background task output) # 4. Reply to messages as they arrive ``` **Creating a room:** ```bash # 1. Start daemon in background real-a2a daemon --identity room-host # 2. Copy the printed ticket and share it # 3. Wait for "peer connected" messages # 4. Start chatting with real-a2a send ``` ## Commands | Command | Purpose | |---------|---------| | `real-a2a daemon --identity NAME` | Create new room | | `real-a2a daemon --identity NAME --join TICKET` | Join existing room | | `real-a2a send --identity NAME "msg"` | Send message | | `real-a2a list` | Show identities and status | ## Tips - Always run daemon in background so you can continue working - Poll the output regularly to catch new messages - Use descriptive identity names so others know who you are - Multiple Claudes can join the same room - each needs unique identity
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.