hcom-agent-messaging
SolidMulti-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom, troubleshooting delivery, or writing multi-agent scripts.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- aannoo
- Repository
- aannoo/hcom
- Created
- 1 years ago
- Last Updated
- today
- Language
- Rust
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
holix-subagents
Full Holix sub-agent lifecycle: spawn, monitor, collect results, answer ask_user questions, approve tool confirmations, and delegate to external CLIs (holix launch). Use when the user asks about subagents, /subagent-spawn, delegate_to_subagent, background workers, sub-agent questions, /subagent-reply, holix launch + coder, or running tasks without blocking the main chat. Invoke via /holix-subagents.
dispatch
Orchestrate other AI coding agents (Claude Code, Codex, Cursor, OpenCode, Pi, Gemini, or any custom agent) by driving them through `ccmux invoke`. ccmux is the cross-harness substrate; YOU are the router. Use this skill when a prompt asks you to coordinate, delegate, fan out, or pipeline work across multiple agents, e.g. "plan with claude, implement with codex, search with gemini", "run these three agents in parallel and combine the results", "delegate this long implementation to codex while I keep working", "have another agent do X and summarize it back", or any request to use `ccmux invoke` to launch and watch worker agents. The user supplies the agent-per-task policy in their prompt; this skill teaches the mechanics of firing, polling, joining, cancelling, and reading worker output, plus when to hand a job off to `ccmux spawn` (a live, human-driven pane) instead of invoking it.
agent-chat
Use when two or more agent sessions (Claude Code or other tools, same machine or peers) must coordinate through markdown files in a shared folder instead of one supervisor driving subagents — group chat, blackboard, mailbox/inbox, multi-session handoff, or an agent-chat/ directory. Triggers include peer agents, N sessions sharing a folder, waiting for another session's reply, atomic task claiming, and needing multiple separate group chats/channels.