[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75WJ0BASHT3WXZP7RR1KJG2":3,"skill-same:01M75WJ0BASHT3WXZP7RR1KJG2":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75WJ0BASHT3WXZP7RR1KJG2","tmux-monitor",null,"Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.","stevengonsalvez\u002Fainb-toolkit","stevengonsalvez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9320602?v=4","01M75W59QRYZYANWY3XG8CJB1P","Steven Gonsalvez","01M75W59RD5YW1RT67BDV0EAZF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftmux-monitor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: tmux-monitor\ndescription: Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.\nversion: 1.0.0\n---\n\n# tmux-monitor Skill\n\n## Purpose\n\nProvide comprehensive visibility into all active tmux sessions, running processes, and spawned agents. This skill enables checking what's running where without needing to manually inspect each session.\n\n## Capabilities\n\n1. **Session Discovery**: Find and categorize all tmux sessions\n2. **Process Inspection**: Identify running servers, dev environments, agents\n3. **Port Mapping**: Show which ports are in use and by what\n4. **Status Reporting**: Generate detailed reports with recommendations\n5. **tmuxwatch Integration**: Use tmuxwatch for enhanced real-time monitoring\n6. **Metadata Extraction**: Read session metadata from .tmux-dev-session.json and agent JSON files\n\n## When to Use\n\n- User asks \"what's running?\"\n- Before starting new dev environments (check port conflicts)\n- After spawning agents (verify they started correctly)\n- When debugging server\u002Fprocess issues\n- Before session cleanup\n- When context switching between projects\n\n## Implementation\n\n### Step 1: Check tmux Availability\n\n```bash\nif ! command -v tmux &> \u002Fdev\u002Fnull; then\n    echo \"❌ tmux is not installed\"\n    exit 1\nfi\n\nif ! tmux list-sessions 2>\u002Fdev\u002Fnull; then\n    echo \"✅ No tmux sessions currently running\"\n    exit 0\nfi\n```\n\n### Step 2: Discover All Sessions\n\n```bash\n# Get all sessions with metadata\nSESSIONS=$(tmux list-sessions -F '#{session_name}|#{session_windows}|#{session_created}|#{session_attached}')\n\n# Count sessions\nTOTAL_SESSIONS=$(echo \"$SESSIONS\" | wc -l | tr -d ' ')\n```\n\n### Step 3: Categorize Sessions\n\nGroup by prefix pattern:\n\n- `dev-*` → Development environments\n- `agent-*` → Spawned agents\n- `claude-*` → Claude Code sessions\n- `monitor-*` → Monitoring sessions\n- Others → Miscellaneous\n\n```bash\nDEV_SESSIONS=$(echo \"$SESSIONS\" | grep \"^dev-\" || true)\nAGENT_SESSIONS=$(echo \"$SESSIONS\" | grep \"^agent-\" || true)\nCLAUDE_SESSIONS=$(echo \"$SESSIONS\" | grep \"^claude-\" || true)\n```\n\n### Step 4: Extract Details for Each Session\n\nFor each session, gather:\n\n**Window Information**:\n```bash\ntmux list-windows -t \"$SESSION\" -F '#{window_index}:#{window_name}:#{window_panes}'\n```\n\n**Running Processes** (from first pane of each window):\n```bash\ntmux capture-pane -t \"$SESSION:0.0\" -p -S -10 -E 0\n```\n\n**Port Detection** (check for listening ports):\n```bash\n# Extract ports from session metadata\nif [ -f \".tmux-dev-session.json\" ]; then\n    BACKEND_PORT=$(jq -r '.backend.port \u002F\u002F empty' .tmux-dev-session.json)\n    FRONTEND_PORT=$(jq -r '.frontend.port \u002F\u002F empty' .tmux-dev-session.json)\nfi\n\n# Or detect from process list\nlsof -nP -iTCP -sTCP:LISTEN | grep -E \"node|python|uv|npm\"\n```\n\n### Step 5: Load Session Metadata\n\n**Dev Environment Metadata** (`.tmux-dev-session.json`):\n```bash\nif [ -f \".tmux-dev-session.json\" ]; then\n    PROJECT=$(jq -r '.project' .tmux-dev-session.json)\n    TYPE=$(jq -r '.type' .tmux-dev-session.json)\n    BACKEND_PORT=$(jq -r '.backend.port \u002F\u002F \"N\u002FA\"' .tmux-dev-session.json)\n    FRONTEND_PORT=$(jq -r '.frontend.port \u002F\u002F \"N\u002FA\"' .tmux-dev-session.json)\n    CREATED=$(jq -r '.created' .tmux-dev-session.json)\nfi\n```\n\n**Agent Metadata** (`{{HOME_TOOL_DIR}}\u002Fagents\u002F*.json`):\n```bash\nif [ -f \"\u002F.claude\u002Fagents\u002F${SESSION}.json\" ]; then\n    AGENT_TYPE=$(jq -r '.agent_type' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    TASK=$(jq -r '.task' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    STATUS=$(jq -r '.status' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    DIRECTORY=$(jq -r '.directory' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    CREATED=$(jq -r '.created' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\nfi\n```\n\n### Step 6: tmuxwatch Integration\n\nIf tmuxwatch is available, offer enhanced view:\n\n```bash\nif command -v tmuxwatch &> \u002Fdev\u002Fnull; then\n    echo \"\"\n    echo \"📊 Enhanced Monitoring Available:\"\n    echo \"   Real-time TUI: tmuxwatch\"\n    echo \"   JSON export:   tmuxwatch --dump | jq\"\n    echo \"\"\n\n    # Optional: Use tmuxwatch for structured data\n    TMUXWATCH_DATA=$(tmuxwatch --dump 2>\u002Fdev\u002Fnull || echo \"{}\")\nfi\n```\n\n### Step 7: Generate Comprehensive Report\n\n```markdown\n# tmux Sessions Overview\n\n**Total Active Sessions**: {count}\n**Total Windows**: {window_count}\n**Total Panes**: {pane_count}\n\n---\n\n## Development Environments ({dev_count})\n\n### 1. dev-myapp-1705161234\n- **Type**: fullstack\n- **Project**: myapp\n- **Status**: ⚡ Active (attached)\n- **Windows**: 4 (servers, logs, claude-work, git)\n- **Panes**: 8\n- **Backend**: Port 8432 → http:\u002F\u002Flocalhost:8432\n- **Frontend**: Port 3891 → http:\u002F\u002Flocalhost:3891\n- **Created**: 2025-01-13 14:30:00 (2h ago)\n- **Attach**: `tmux attach -t dev-myapp-1705161234`\n\n---\n\n## Spawned Agents ({agent_count})\n\n### 2. agent-1705160000\n- **Agent Type**: codex\n- **Task**: Refactor authentication module\n- **Status**: ⚙️  Running (15 minutes)\n- **Working Directory**: \u002Fworkspace\u002Fmyapp\n- **Git Worktree**: worktrees\u002Fagent-1705160000\n- **Windows**: 1 (work)\n- **Panes**: 2 (agent | monitoring)\n- **Last Output**: \"Analyzing auth.py dependencies...\"\n- **Attach**: `tmux attach -t agent-1705160000`\n- **Metadata**: `{{HOME_TOOL_DIR}}\u002Fagents\u002Fagent-1705160000.json`\n\n### 3. agent-1705161000\n- **Agent Type**: aider\n- **Task**: Generate API documentation\n- **Status**: ✅ Completed (5 minutes ago)\n- **Output**: Documentation written to docs\u002Fapi\u002F\n- **Attach**: `tmux attach -t agent-1705161000` (review)\n- **Cleanup**: `tmux kill-session -t agent-1705161000`\n\n---\n\n## Running Processes Summary\n\n| Port | Service      | Session                  | Status  |\n|------|--------------|--------------------------|---------|\n| 8432 | Backend API  | dev-myapp-1705161234     | Running |\n| 3891 | Frontend Dev | dev-myapp-1705161234     | Running |\n| 5160 | Supabase     | dev-shotclubhouse-xxx    | Running |\n\n---\n\n## Quick Actions\n\n**Attach to session**:\n```bash\ntmux attach -t \u003Csession-name>\n```\n\n**Kill session**:\n```bash\ntmux kill-session -t \u003Csession-name>\n```\n\n**List all sessions**:\n```bash\ntmux ls\n```\n\n**Kill all completed agents**:\n```bash\nfor session in $(tmux ls | grep \"^agent-\" | cut -d: -f1); do\n    STATUS=$(jq -r '.status' \"{{HOME_TOOL_DIR}}\u002Fagents\u002F${session}.json\" 2>\u002Fdev\u002Fnull)\n    if [ \"$STATUS\" = \"completed\" ]; then\n        tmux kill-session -t \"$session\"\n    fi\ndone\n```\n\n---\n\n## Recommendations\n\n{generated based on findings}\n```\n\n### Step 8: Provide Contextual Recommendations\n\n**If completed agents found**:\n```\n⚠️  Found 1 completed agent session:\n   - agent-1705161000: Task completed 5 minutes ago\n\nRecommendation: Review results and clean up:\n  tmux attach -t agent-1705161000  # Review\n  tmux kill-session -t agent-1705161000  # Cleanup\n```\n\n**If long-running detached sessions**:\n```\n💡 Found detached session running for 2h 40m:\n   - dev-api-service-1705159000\n\nRecommendation: Check if still needed:\n  tmux attach -t dev-api-service-1705159000\n```\n\n**If port conflicts detected**:\n```\n⚠️  Port conflict detected:\n   - Port 3000 in use by dev-oldproject-xxx\n   - New session will use random port instead\n\nRecommendation: Clean up old session if no longer needed\n```\n\n## Output Formats\n\n### Compact (Default)\n\n```\n5 active sessions:\n- dev-myapp-1705161234 (fullstack, 4 windows, active)\n- dev-api-service-1705159000 (backend-only, 4 windows, detached)\n- agent-1705160000 (codex, running 15m)\n- agent-1705161000 (aider, completed ✓)\n- claude-work (main session, current)\n\n3 running servers:\n- Port 8432: Backend API (dev-myapp)\n- Port 3891: Frontend Dev (dev-myapp)\n- Port 5160: Supabase (dev-shotclubhouse)\n```\n\n### Detailed (Verbose)\n\nFull report with all metadata, sample output, recommendations.\n\n### JSON (Programmatic)\n\n```json\n{\n  \"sessions\": [\n    {\n      \"name\": \"dev-myapp-1705161234\",\n      \"type\": \"dev-environment\",\n      \"category\": \"fullstack\",\n      \"windows\": 4,\n      \"panes\": 8,\n      \"status\": \"attached\",\n      \"created\": \"2025-01-13T14:30:00Z\",\n      \"ports\": {\n        \"backend\": 8432,\n        \"frontend\": 3891\n      },\n      \"metadata_file\": \".tmux-dev-session.json\"\n    },\n    {\n      \"name\": \"agent-1705160000\",\n      \"type\": \"spawned-agent\",\n      \"agent_type\": \"codex\",\n      \"task\": \"Refactor authentication module\",\n      \"status\": \"running\",\n      \"runtime\": \"15m\",\n      \"directory\": \"\u002Fworkspace\u002Fmyapp\",\n      \"worktree\": \"worktrees\u002Fagent-1705160000\",\n      \"metadata_file\": \"{{HOME_TOOL_DIR}}\u002Fagents\u002Fagent-1705160000.json\"\n    }\n  ],\n  \"summary\": {\n    \"total_sessions\": 5,\n    \"total_windows\": 12,\n    \"total_panes\": 28,\n    \"running_servers\": 3,\n    \"active_agents\": 1,\n    \"completed_agents\": 1\n  },\n  \"ports\": [\n    {\"port\": 8432, \"service\": \"Backend API\", \"session\": \"dev-myapp-1705161234\"},\n    {\"port\": 3891, \"service\": \"Frontend Dev\", \"session\": \"dev-myapp-1705161234\"},\n    {\"port\": 5160, \"service\": \"Supabase\", \"session\": \"dev-shotclubhouse-xxx\"}\n  ]\n}\n```\n\n## Integration with Commands\n\nThis skill is used by:\n- `\u002Ftmux-status` command (user-facing command)\n- Automatically before starting new dev environments (conflict detection)\n- By spawned agents to check session status\n\n## Dependencies\n\n- `tmux` (required)\n- `jq` (required for JSON parsing)\n- `lsof` (optional, for port detection)\n- `tmuxwatch` (optional, for enhanced monitoring)\n\n## File Structure\n\n```\n{{HOME_TOOL_DIR}}\u002Fagents\u002F\n  agent-{timestamp}.json           # Agent metadata\n\n.tmux-dev-session.json             # Dev environment metadata (per project)\n\n\u002Ftmp\u002Ftmux-monitor-cache.json       # Optional cache for performance\n```\n\n## Related Commands\n\n- `\u002Ftmux-status` - User-facing wrapper around this skill\n- `\u002Fspawn-agent` - Creates sessions that this skill monitors\n- `\u002Fstart-local`, `\u002Fstart-ios`, `\u002Fstart-android` - Create dev environments\n\n---\n\n## Steering Protocol\n\nBeyond monitoring, use these patterns to actively manage coding sessions.\n\n### Session Naming Convention\n\nUse consistent names so sessions are self-documenting and parseable:\n\n```\n{tool}-{scope}-{id}[-{desc}]\n```\n\n| Segment | Values | Example |\n|---------|--------|---------|\n| `tool` | `cc` (Claude Code), `codex`, `pi` | `cc` |\n| `scope` | `issue`, `fix`, `pr`, `feature`, `task` | `issue` |\n| `id` | Issue number, PR number, or short identifier | `174` |\n| `desc` | Optional short slug | `auth-refactor` |\n\n**Examples:** `cc-issue-174-auth-refactor`, `codex-fix-1520`, `cc-pr-186`\n\n### Monitoring Signals\n\nWhen monitoring a coding session, look for these signals:\n\n| Signal | Action |\n|--------|--------|\n| Model is generating code | Let it work |\n| \"I'll now...\" planning text | Verify approach is correct |\n| Error\u002Fstack trace repeating | Intervene (steer) |\n| Idle \u002F waiting for input | Check if stuck or done |\n| \"I've completed...\" summary | Move to verify phase |\n| Session has exited | Check output \u002F PR status |\n\n### Steering (when intervention is needed)\n\n```bash\n# Correct course\ntmux send-keys -t \"${SESSION}\" \\\n  \"STOP. You're going the wrong direction. \u003Cspecific correction>\" Enter\n\n# Unstick\ntmux send-keys -t \"${SESSION}\" \\\n  \"You seem stuck. Try: \u003Cspecific suggestion>\" Enter\n\n# Add context\ntmux send-keys -t \"${SESSION}\" \\\n  \"Additional context: \u003Cfile path, pattern, constraint>\" Enter\n\n# Abort\ntmux send-keys -t \"${SESSION}\" \"\u002Fexit\" Enter\n```\n\n### Steering Rules\n1. **Be specific.** \"Fix the types\" is bad. \"Change `costTotal` to `v.optional(v.float64())`\" is good.\n2. **Don't over-steer.** Interruptions reset context. If on track, let it work.\n3. **One correction at a time.** Multiple simultaneous corrections confuse the model.\n4. **Stuck 3+ times on same issue?** Kill session, rethink approach, respawn with better prompt.\n\n### Completion Detection\n\nDetect session state from `capture-pane` output:\n\n```bash\nOUTPUT=$(tmux capture-pane -t \"$SESSION\" -p | tail -30)\n\n# Completion signals\necho \"$OUTPUT\" | grep -qE \"I've completed|changes have been|PR.*created|committed.*pushed\" && echo \"DONE\"\n\n# Error signals\necho \"$OUTPUT\" | grep -qE \"Error:|FATAL|panic|OOM|killed|context.*exhausted\" && echo \"ERROR\"\n\n# Stuck signals (same error repeating 3+ times)\necho \"$OUTPUT\" | grep -iE \"error|fail|fatal|panic\" | sort | uniq -c | sort -rn | head -1 | awk '$1 >= 3 {print \"STUCK\"}'\n```\n\n### Session Health Check\n\nPeriodically check for stale sessions:\n\n```bash\ntmux list-sessions -F '#{session_name}' 2>\u002Fdev\u002Fnull | while IFS= read -r s; do\n  [ -z \"$s\" ] && continue\n  LAST_ACTIVITY=$(tmux display -t \"$s\" -p '#{session_activity}')\n  IDLE_SECS=$(( $(date +%s) - LAST_ACTIVITY ))\n  if [ $IDLE_SECS -gt 3600 ]; then\n    echo \"⚠️ $s idle for ${IDLE_SECS}s — consider cleanup\"\n  fi\ndone\n```\n\n---\n\n## Notes\n\n- This skill is read-only (monitoring\u002Fdiscovery), never modifies sessions\n- Steering commands above are for manual intervention when needed\n- Safe to run anytime without side effects\n- Provides snapshot of current state\n- Can be cached for performance (TTL: 10 seconds)\n- Should be run before potentially conflicting operations\n","# tmux-monitor Skill\n\n## Purpose\n\nProvide comprehensive visibility into all active tmux sessions, running processes, and spawned agents. This skill enables checking what's running where without needing to manually inspect each session.\n\n## Capabilities\n\n1. **Session Discovery**: Find and categorize all tmux sessions\n2. **Process Inspection**: Identify running servers, dev environments, agents\n3. **Port Mapping**: Show which ports are in use and by what\n4. **Status Reporting**: Generate detailed reports with recommendations\n5. **tmuxwatch Integration**: Use tmuxwatch for enhanced real-time monitoring\n6. **Metadata Extraction**: Read session metadata from .tmux-dev-session.json and agent JSON files\n\n## When to Use\n\n- User asks \"what's running?\"\n- Before starting new dev environments (check port conflicts)\n- After spawning agents (verify they started correctly)\n- When debugging server\u002Fprocess issues\n- Before session cleanup\n- When context switching between projects\n\n## Implementation\n\n### Step 1: Check tmux Availability\n\n```bash\nif ! command -v tmux &> \u002Fdev\u002Fnull; then\n    echo \"❌ tmux is not installed\"\n    exit 1\nfi\n\nif ! tmux list-sessions 2>\u002Fdev\u002Fnull; then\n    echo \"✅ No tmux sessions currently running\"\n    exit 0\nfi\n```\n\n### Step 2: Discover All Sessions\n\n```bash\n# Get all sessions with metadata\nSESSIONS=$(tmux list-sessions -F '#{session_name}|#{session_windows}|#{session_created}|#{session_attached}')\n\n# Count sessions\nTOTAL_SESSIONS=$(echo \"$SESSIONS\" | wc -l | tr -d ' ')\n```\n\n### Step 3: Categorize Sessions\n\nGroup by prefix pattern:\n\n- `dev-*` → Development environments\n- `agent-*` → Spawned agents\n- `claude-*` → Claude Code sessions\n- `monitor-*` → Monitoring sessions\n- Others → Miscellaneous\n\n```bash\nDEV_SESSIONS=$(echo \"$SESSIONS\" | grep \"^dev-\" || true)\nAGENT_SESSIONS=$(echo \"$SESSIONS\" | grep \"^agent-\" || true)\nCLAUDE_SESSIONS=$(echo \"$SESSIONS\" | grep \"^claude-\" || true)\n```\n\n### Step 4: Extract Details for Each Session\n\nFor each session, gather:\n\n**Window Information**:\n```bash\ntmux list-windows -t \"$SESSION\" -F '#{window_index}:#{window_name}:#{window_panes}'\n```\n\n**Running Processes** (from first pane of each window):\n```bash\ntmux capture-pane -t \"$SESSION:0.0\" -p -S -10 -E 0\n```\n\n**Port Detection** (check for listening ports):\n```bash\n# Extract ports from session metadata\nif [ -f \".tmux-dev-session.json\" ]; then\n    BACKEND_PORT=$(jq -r '.backend.port \u002F\u002F empty' .tmux-dev-session.json)\n    FRONTEND_PORT=$(jq -r '.frontend.port \u002F\u002F empty' .tmux-dev-session.json)\nfi\n\n# Or detect from process list\nlsof -nP -iTCP -sTCP:LISTEN | grep -E \"node|python|uv|npm\"\n```\n\n### Step 5: Load Session Metadata\n\n**Dev Environment Metadata** (`.tmux-dev-session.json`):\n```bash\nif [ -f \".tmux-dev-session.json\" ]; then\n    PROJECT=$(jq -r '.project' .tmux-dev-session.json)\n    TYPE=$(jq -r '.type' .tmux-dev-session.json)\n    BACKEND_PORT=$(jq -r '.backend.port \u002F\u002F \"N\u002FA\"' .tmux-dev-session.json)\n    FRONTEND_PORT=$(jq -r '.frontend.port \u002F\u002F \"N\u002FA\"' .tmux-dev-session.json)\n    CREATED=$(jq -r '.created' .tmux-dev-session.json)\nfi\n```\n\n**Agent Metadata** (`{{HOME_TOOL_DIR}}\u002Fagents\u002F*.json`):\n```bash\nif [ -f \"\u002F.claude\u002Fagents\u002F${SESSION}.json\" ]; then\n    AGENT_TYPE=$(jq -r '.agent_type' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    TASK=$(jq -r '.task' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    STATUS=$(jq -r '.status' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    DIRECTORY=$(jq -r '.directory' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\n    CREATED=$(jq -r '.created' \"\u002F.claude\u002Fagents\u002F${SESSION}.json\")\nfi\n```\n\n### Step 6: tmuxwatch Integration\n\nIf tmuxwatch is available, offer enhanced view:\n\n```bash\nif command -v tmuxwatch &> \u002Fdev\u002Fnull; then\n    echo \"\"\n    echo \"📊 Enhanced Monitoring Available:\"\n    echo \"   Real-time TUI: tmuxwatch\"\n    echo \"   JSON export:   tmuxwatch --dump | jq\"\n    echo \"\"\n\n    # Optional: Use tmuxwatch for structured data\n    TMUXWATCH_DATA=$(tmuxwatch --dump 2>\u002Fdev\u002Fnull || echo \"{}\")\nfi\n```\n\n### Step 7: Generate Comprehensive Report\n\n```markdown\n# tmux Sessions Overview\n\n**Total Active Sessions**: {count}\n**Total Windows**: {window_count}\n**Total Panes**: {pane_count}\n\n---\n\n## Development Environments ({dev_count})\n\n### 1. dev-myapp-1705161234\n- **Type**: fullstack\n- **Project**: myapp\n- **Status**: ⚡ Active (attached)\n- **Windows**: 4 (servers, logs, claude-work, git)\n- **Panes**: 8\n- **Backend**: Port 8432 → http:\u002F\u002Flocalhost:8432\n- **Frontend**: Port 3891 → http:\u002F\u002Flocalhost:3891\n- **Created**: 2025-01-13 14:30:00 (2h ago)\n- **Attach**: `tmux attach -t dev-myapp-1705161234`\n\n---\n\n## Spawned Agents ({agent_count})\n\n### 2. agent-1705160000\n- **Agent Type**: codex\n- **Task**: Refactor authentication module\n- **Status**: ⚙️  Running (15 minutes)\n- **Working Directory**: \u002Fworkspace\u002Fmyapp\n- **Git Worktree**: worktrees\u002Fagent-1705160000\n- **Windows**: 1 (work)\n- **Panes**: 2 (agent | monitoring)\n- **Last Output**: \"Analyzing auth.py dependencies...\"\n- **Attach**: `tmux attach -t agent-1705160000`\n- **Metadata**: `{{HOME_TOOL_DIR}}\u002Fagents\u002Fagent-1705160000.json`\n\n### 3. agent-1705161000\n- **Agent Type**: aider\n- **Task**: Generate API documentation\n- **Status**: ✅ Completed (5 minutes ago)\n- **Output**: Documentation written to docs\u002Fapi\u002F\n- **Attach**: `tmux attach -t agent-1705161000` (review)\n- **Cleanup**: `tmux kill-session -t agent-1705161000`\n\n---\n\n## Running Processes Summary\n\n| Port | Service      | Session                  | Status  |\n|------|--------------|--------------------------|---------|\n| 8432 | Backend API  | dev-myapp-1705161234     | Running |\n| 3891 | Frontend Dev | dev-myapp-1705161234     | Running |\n| 5160 | Supabase     | dev-shotclubhouse-xxx    | Running |\n\n---\n\n## Quick Actions\n\n**Attach to session**:\n```bash\ntmux attach -t \u003Csession-name>\n```\n\n**Kill session**:\n```bash\ntmux kill-session -t \u003Csession-name>\n```\n\n**List all sessions**:\n```bash\ntmux ls\n```\n\n**Kill all completed agents**:\n```bash\nfor session in $(tmux ls | grep \"^agent-\" | cut -d: -f1); do\n    STATUS=$(jq -r '.status' \"{{HOME_TOOL_DIR}}\u002Fagents\u002F${session}.json\" 2>\u002Fdev\u002Fnull)\n    if [ \"$STATUS\" = \"completed\" ]; then\n        tmux kill-session -t \"$session\"\n    fi\ndone\n```\n\n---\n\n## Recommendations\n\n{generated based on findings}\n```\n\n### Step 8: Provide Contextual Recommendations\n\n**If completed agents found**:\n```\n⚠️  Found 1 completed agent session:\n   - agent-1705161000: Task completed 5 minutes ago\n\nRecommendation: Review results and clean up:\n  tmux attach -t agent-1705161000  # Review\n  tmux kill-session -t agent-1705161000  # Cleanup\n```\n\n**If long-running detached sessions**:\n```\n💡 Found detached session running for 2h 40m:\n   - dev-api-service-1705159000\n\nRecommendation: Check if still needed:\n  tmux attach -t dev-api-service-1705159000\n```\n\n**If port conflicts detected**:\n```\n⚠️  Port conflict detected:\n   - Port 3000 in use by dev-oldproject-xxx\n   - New session will use random port instead\n\nRecommendation: Clean up old session if no longer needed\n```\n\n## Output Formats\n\n### Compact (Default)\n\n```\n5 active sessions:\n- dev-myapp-1705161234 (fullstack, 4 windows, active)\n- dev-api-service-1705159000 (backend-only, 4 windows, detached)\n- agent-1705160000 (codex, running 15m)\n- agent-1705161000 (aider, completed ✓)\n- claude-work (main session, current)\n\n3 running servers:\n- Port 8432: Backend API (dev-myapp)\n- Port 3891: Frontend Dev (dev-myapp)\n- Port 5160: Supabase (dev-shotclubhouse)\n```\n\n### Detailed (Verbose)\n\nFull report with all metadata, sample output, recommendations.\n\n### JSON (Programmatic)\n\n```json\n{\n  \"sessions\": [\n    {\n      \"name\": \"dev-myapp-1705161234\",\n      \"type\": \"dev-environment\",\n      \"category\": \"fullstack\",\n      \"windows\": 4,\n      \"panes\": 8,\n      \"status\": \"attached\",\n      \"created\": \"2025-01-13T14:30:00Z\",\n      \"ports\": {\n        \"backend\": 8432,\n        \"frontend\": 3891\n      },\n      \"metadata_file\": \".tmux-dev-session.json\"\n    },\n    {\n      \"name\": \"agent-1705160000\",\n      \"type\": \"spawned-agent\",\n      \"agent_type\": \"codex\",\n      \"task\": \"Refactor authentication module\",\n      \"status\": \"running\",\n      \"runtime\": \"15m\",\n      \"directory\": \"\u002Fworkspace\u002Fmyapp\",\n      \"worktree\": \"worktrees\u002Fagent-1705160000\",\n      \"metadata_file\": \"{{HOME_TOOL_DIR}}\u002Fagents\u002Fagent-1705160000.json\"\n    }\n  ],\n  \"summary\": {\n    \"total_sessions\": 5,\n    \"total_windows\": 12,\n    \"total_panes\": 28,\n    \"running_servers\": 3,\n    \"active_agents\": 1,\n    \"completed_agents\": 1\n  },\n  \"ports\": [\n    {\"port\": 8432, \"service\": \"Backend API\", \"session\": \"dev-myapp-1705161234\"},\n    {\"port\": 3891, \"service\": \"Frontend Dev\", \"session\": \"dev-myapp-1705161234\"},\n    {\"port\": 5160, \"service\": \"Supabase\", \"session\": \"dev-shotclubhouse-xxx\"}\n  ]\n}\n```\n\n## Integration with Commands\n\nThis skill is used by:\n- `\u002Ftmux-status` command (user-facing command)\n- Automatically before starting new dev environments (conflict detection)\n- By spawned agents to check session status\n\n## Dependencies\n\n- `tmux` (required)\n- `jq` (required for JSON parsing)\n- `lsof` (optional, for port detection)\n- `tmuxwatch` (optional, for enhanced monitoring)\n\n## File Structure\n\n```\n{{HOME_TOOL_DIR}}\u002Fagents\u002F\n  agent-{timestamp}.json           # Agent metadata\n\n.tmux-dev-session.json             # Dev environment metadata (per project)\n\n\u002Ftmp\u002Ftmux-monitor-cache.json       # Optional cache for performance\n```\n\n## Related Commands\n\n- `\u002Ftmux-status` - User-facing wrapper around this skill\n- `\u002Fspawn-agent` - Creates sessions that this skill monitors\n- `\u002Fstart-local`, `\u002Fstart-ios`, `\u002Fstart-android` - Create dev environments\n\n---\n\n## Steering Protocol\n\nBeyond monitoring, use these patterns to actively manage coding sessions.\n\n### Session Naming Convention\n\nUse consistent names so sessions are self-documenting and parseable:\n\n```\n{tool}-{scope}-{id}[-{desc}]\n```\n\n| Segment | Values | Example |\n|---------|--------|---------|\n| `tool` | `cc` (Claude Code), `codex`, `pi` | `cc` |\n| `scope` | `issue`, `fix`, `pr`, `feature`, `task` | `issue` |\n| `id` | Issue number, PR number, or short identifier | `174` |\n| `desc` | Optional short slug | `auth-refactor` |\n\n**Examples:** `cc-issue-174-auth-refactor`, `codex-fix-1520`, `cc-pr-186`\n\n### Monitoring Signals\n\nWhen monitoring a coding session, look for these signals:\n\n| Signal | Action |\n|--------|--------|\n| Model is generating code | Let it work |\n| \"I'll now...\" planning text | Verify approach is correct |\n| Error\u002Fstack trace repeating | Intervene (steer) |\n| Idle \u002F waiting for input | Check if stuck or done |\n| \"I've completed...\" summary | Move to verify phase |\n| Session has exited | Check output \u002F PR status |\n\n### Steering (when intervention is needed)\n\n```bash\n# Correct course\ntmux send-keys -t \"${SESSION}\" \\\n  \"STOP. You're going the wrong direction. \u003Cspecific correction>\" Enter\n\n# Unstick\ntmux send-keys -t \"${SESSION}\" \\\n  \"You seem stuck. Try: \u003Cspecific suggestion>\" Enter\n\n# Add context\ntmux send-keys -t \"${SESSION}\" \\\n  \"Additional context: \u003Cfile path, pattern, constraint>\" Enter\n\n# Abort\ntmux send-keys -t \"${SESSION}\" \"\u002Fexit\" Enter\n```\n\n### Steering Rules\n1. **Be specific.** \"Fix the types\" is bad. \"Change `costTotal` to `v.optional(v.float64())`\" is good.\n2. **Don't over-steer.** Interruptions reset context. If on track, let it work.\n3. **One correction at a time.** Multiple simultaneous corrections confuse the model.\n4. **Stuck 3+ times on same issue?** Kill session, rethink approach, respawn with better prompt.\n\n### Completion Detection\n\nDetect session state from `capture-pane` output:\n\n```bash\nOUTPUT=$(tmux capture-pane -t \"$SESSION\" -p | tail -30)\n\n# Completion signals\necho \"$OUTPUT\" | grep -qE \"I've completed|changes have been|PR.*created|committed.*pushed\" && echo \"DONE\"\n\n# Error signals\necho \"$OUTPUT\" | grep -qE \"Error:|FATAL|panic|OOM|killed|context.*exhausted\" && echo \"ERROR\"\n\n# Stuck signals (same error repeating 3+ times)\necho \"$OUTPUT\" | grep -iE \"error|fail|fatal|panic\" | sort | uniq -c | sort -rn | head -1 | awk '$1 >= 3 {print \"STUCK\"}'\n```\n\n### Session Health Check\n\nPeriodically check for stale sessions:\n\n```bash\ntmux list-sessions -F '#{session_name}' 2>\u002Fdev\u002Fnull | while IFS= read -r s; do\n  [ -z \"$s\" ] && continue\n  LAST_ACTIVITY=$(tmux display -t \"$s\" -p '#{session_activity}')\n  IDLE_SECS=$(( $(date +%s) - LAST_ACTIVITY ))\n  if [ $IDLE_SECS -gt 3600 ]; then\n    echo \"⚠️ $s idle for ${IDLE_SECS}s — consider cleanup\"\n  fi\ndone\n```\n\n---\n\n## Notes\n\n- This skill is read-only (monitoring\u002Fdiscovery), never modifies sessions\n- Steering commands above are for manual intervention when needed\n- Safe to run anytime without side effects\n- Provides snapshot of current state\n- Can be cached for performance (TTL: 10 seconds)\n- Should be run before potentially conflicting operations\n",{"name":5,"version":24,"description":7},"1.0.0","main","9cf32d1e636db09530158af14ba301bfa5d401e9","skills\u002Ftmux-monitor","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez","stevengonsalvez.com","2026-11-12 00:50:59",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-monitor",{"tool":38,"command":39},"bunx","bunx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-monitor",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-monitor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftmux-monitor\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"scripts\u002Fmonitor.sh","SCRIPT","脚本",16294,"https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftmux-monitor\u002Fscripts\u002Fmonitor.sh",[53,60,67,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75WK9B8DKVJBJJ4CX2QMJMX","well-formed","Fixture skill that satisfies every mechanical rule, used to prove the conformance check passes a clean tree instead of failing everything.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fclean\u002Fwell-formed\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75WK6ZGDXJJN8879K49QEYG","underscore-tools","Fixture skill that spells the tool allowlist key with an underscore instead of the hyphen the spec requires.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Funderscore-tools\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75WK524MVT2H9E27ZCEA3HR","no-frontmatter","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fno-frontmatter\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75WJWZBMKR8R60PG3T3MCCC","long-description","Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Flong-description\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75WJVRH3J22WKED7E5D01S8","some-other-name","Fixture skill whose frontmatter name does not match its parent directory name.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fdir-mismatch\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75WJTC7H5FRP6S129VBSMZC","bad_Name","Fixture skill whose name uses an underscore and a capital letter, so it violates the agentskills.io name pattern.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fbad_Name\u002FSKILL.md",[],[]]