msg — Claude Code skill: agent-to-agent messaging
This skill hands your agent a msg CLI for talking to other Claude and Claude sessions, reading incoming messages and coordinating across tmux panes.
npx skills add pchalasani/claude-code-tools --skill msg -a claude-codeWhat msg does
The agent registers once per session with msg register <your-name>; the tmux pane is detected automatically. From there it sends directly — msg send <agent-name> "text", or several names separated by commas — and answers with msg reply. Incoming mail lands in msg inbox, grouped by thread and marked as read.
Housekeeping commands cover the rest: msg list for registered agents, msg threads for open threads, msg status for system health. The CLI is the only piece involved, but pane detection depends on tmux, so check that before pulling a second agent into the loop.
Messages eat context in the receiving session, so the skill's guidelines ask for short ones. Reference code and file paths in the text instead of pasting large blocks, and give enough context in a reply that the other agent does not have to re-read the whole thread.
What it helps with
- hand a task to a parallel agent session without retyping it
- read incoming messages from another agent and clear the inbox
- coordinate two agents sitting in neighbouring tmux panes
- broadcast one message to several agents at once
- see which agents are registered and which threads are open
Example prompts for the agent
- register as reviewer and tell the builder agent the review is done
- check msg inbox and reply in the latest thread
- send agent1,agent2 the path to the file you just changed
How to install msg
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill msg -a claude-code2Manually: put the files in place
~/.claude/skills/msg/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/msg/
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill msg -a codex2Manually: put the files in place
.agents/skills/msg/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill msg -a cursor2Manually: put the files in place
.cursor/skills/msg/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pchalasani/claude-code-tools msg2Manually: put the files in place
.github/skills/msg/SKILL.md1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill msg -a gemini-cli2Platform CLI
gemini skills install https://github.com/pchalasani/claude-code-tools --path plugins/msg/skills/msgManually: put the files in place
.devin/skills/msg/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill msg -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about msg
How do I install msg in Claude?
Run npx skills add pchalasani/claude-code-tools --skill msg -a claude-code. The skill lands in ~/.claude/skills/msg/SKILL.md.
What does msg do?
It gives an agent a CLI for messaging other Claude and Claude sessions: send, reply, read the inbox, list agents and threads.
What does msg need to work?
The agent registers first with msg register <your-name>. The tmux pane is auto-detected, and registration is a one-time step per session.
Source text
SKILL.md · MIT
--- name: msg description: >- Inter-agent communication via the msg CLI. Use this when you need to send messages to other agent sessions, read incoming messages, or coordinate with other agents in tmux panes. --- # msg: Inter-Agent Communication You can communicate with other coding agent sessions (Claude Code or Codex CLI) using the `msg` CLI tool. ## Registration Before sending or receiving messages, register yourself: ```bash msg register <your-name> ``` This auto-detects your tmux pane. You only need to do this once per session. ## Sending Messages Send a message directly to another agent: ```bash msg send <agent-name> "Your message here" ``` Send to multiple agents: ```bash msg send agent1,agent2 "Message for both of you" ``` ## Replying ```bash msg reply <agent-name> "Your reply here" ``` ## Receiving Messages Check your inbox: ```bash msg inbox ``` This shows all unread messages grouped by thread and marks them as read. ## Other Commands ```bash msg list # List registered agents msg threads # List active threads msg status # Check system health ``` ## Guidelines - Keep messages concise -- they consume context in the receiving agent's session. - When replying, include enough context that the recipient understands without re-reading the full thread. - If you need to share code or file paths, reference them in the message text rather than pasting large blocks.
© pchalasani · MIT · pchalasani/claude-code-tools