القائمة
Send messages to other Claude Code or Codex sessions via tmux. Hand off complex debugging context, get second opinions, share detailed technical findings across sessions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Screenshot every view/screen of an app for marketing, product sites, and documentation. Use when asked to "screenshot the app", "capture all views", "get marketing screenshots", "screenshot every screen", or "product shots". Works with macOS native apps (screencapture), web apps (Puppeteer/Playwright), and Electron apps.
Recover working context from a prior Claude Code session by reading its JSONL conversation log and turning it into a clean handoff for Codex or another agent. Use when the user wants Codex to continue where Claude left off in the same repo, asks you to get up to speed on previous work, wants to resume a Claude thread after an interruption or outage, or needs help finding and summarizing the relevant file in ~/.claude/projects/.
Deep dive on any topic. Decomposes into subtopics, researches each in parallel with thorough source gathering, then synthesizes into a comprehensive report (4,000-10,000+ words, 40-100+ sources). Scales depth dynamically based on topic complexity. Use when asked for a deep dive, deep research, comprehensive analysis, or thorough investigation of a topic.
Branch the current Claude Code or Codex session into a new tmux session. Creates a parallel conversation that can diverge independently. Use when you want to explore an alternative approach without losing your current context.
Spawn a new Claude Code or Codex session in a project directory with context handoff. This skill should be used when discussion shifts to a different project/repo and the user wants to work on it in a dedicated session. Creates a handoff document with relevant context from the current conversation, then launches a new tmux session ready to continue.
Refactor bloated skill.md files using progressive disclosure pattern. Moves detailed content to references/ while keeping skill.md focused and discoverable. Use when a skill is approaching 500 lines or needs better organization.
| name | agent-comms |
| description | Send messages to other Claude Code or Codex sessions via tmux. Hand off complex debugging context, get second opinions, share detailed technical findings across sessions. |
Send messages to and read output from other tmux sessions running Claude Code or Codex. Built for coordination between parallel agent sessions.
Works identically on both platforms -- the underlying mechanism is tmux, not the AI agent. Sessions can communicate across platforms (a Claude Code session can message a Codex session and vice versa).
Make the script executable (one-time):
chmod +x ~/.claude/skills/agent-comms/scripts/agent-msg
Always prefix messages with a header so the receiving session knows it's agent-to-agent:
[AGENT-MSG] From: <your-session-name>
<your actual message here>
Get your session name:
tmux display-message -p '#S'
SCRIPT=~/.claude/skills/agent-comms/scripts/agent-msg
# List available sessions
$SCRIPT list
# Send message (types into their terminal + Enter)
$SCRIPT send <session> "<message>"
# Read their terminal output
$SCRIPT read <session> --lines 50
# Get their working directory
$SCRIPT info <session>
Get your session name for identification:
tmux display-message -p '#S'
List sessions to find the target:
~/.claude/skills/agent-comms/scripts/agent-msg list
Read their context before sending:
~/.claude/skills/agent-comms/scripts/agent-msg read worker-1 --lines 50
Send your message with identification:
~/.claude/skills/agent-comms/scripts/agent-msg send worker-1 "[AGENT-MSG] From: main-session
Hit a wall on the websocket reconnection logic. Here's where I'm stuck: [detailed context...]"
Read their response:
~/.claude/skills/agent-comms/scripts/agent-msg read worker-1 --lines 30
You've been debugging a native module issue for 20 minutes. It's a multi-layered problem involving Node versions, native rebuilds, and cross-project dependencies. You want another agent to take a look with full context:
# Check what sessions are running
~/.claude/skills/agent-comms/scripts/agent-msg list
# SESSION WINDOWS ATTACHED
# worker-debug 1 no
# main-session 1 yes
# Send the full technical context
~/.claude/skills/agent-comms/scripts/agent-msg send worker-debug "[AGENT-MSG] From: main-session
Need a second opinion on a native module conflict. Here's what I've traced:
THE ISSUE:
- electron-builder fails with 'better-sqlite3 was compiled against a different Node.js version'
- This started after I ran nvm use 22 in another terminal for a different project
WHAT I'VE FOUND:
1. Main project expects Node 20.x for native modules
2. better-sqlite3 got rebuilt against Node 22 when I ran npm install in the other project
3. They share a global .node-gyp cache at ~/.node-gyp
4. The rebuild pulled in headers for 22.x, now electron can't load the module
WHAT I'VE TRIED:
- npm rebuild better-sqlite3 (still uses cached 22.x headers)
- Deleted node_modules, fresh install (same issue)
- electron-rebuild --force (fails with same ABI mismatch)
QUESTION:
Do I need to clear the global .node-gyp cache? Or is there a way to force better-sqlite3 to rebuild with electron's Node headers specifically? Wondering if I'm missing something obvious."
# Wait for them to analyze, then check response
~/.claude/skills/agent-comms/scripts/agent-msg read worker-debug --lines 50
The receiving session sees your message as user input. Without the [AGENT-MSG] header, it might think a human is typing. The header tells it:
terminal-HHMMSS or custom names you assign[AGENT-MSG] prefix