[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75WHVZESDD2SCK0C3YER96K":3,"skill-same:01M75WHVZESDD2SCK0C3YER96K":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M75WHVZESDD2SCK0C3YER96K","tmux-message",null,"Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — \"claude-peers fallback\", \"tmux send-keys\", \"send to peer via tmux\", \"inject directive\", \"deliver to nanoclaw\u002Fhermes peer\", \"peer message\". Tmux-only — won't reach peers running outside tmux.","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-message\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: tmux-message\ndescription: Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — \"claude-peers fallback\", \"tmux send-keys\", \"send to peer via tmux\", \"inject directive\", \"deliver to nanoclaw\u002Fhermes peer\", \"peer message\". Tmux-only — won't reach peers running outside tmux.\n---\n\n# tmux-message\n\nDeliver a message to another Claude Code TUI session running in tmux. Use the bundled `scripts\u002Fsend.sh` — it handles session resolution, pre-flight safety checks, paste-buffer delivery, and post-flight verification.\n\n## When to use\n\n- claude-peers MCP `send_message` returned success but the receiver never acted on the message (silent failure mode observed in this fleet).\n- Sending a directive\u002Fhandoff to a peer Claude Code session whose tmux session name is known (full or fuzzy).\n- Need to inject a multi-line message into another Claude Code TUI prompt and submit it as if the user typed it.\n\nDo NOT use for — peers outside tmux, shell-only sessions (no Claude Code TUI), or one-shot commands you would just paste yourself.\n\n## Usage\n\n```bash\n# Send file content\n~\u002F.claude\u002Fskills\u002Ftmux-message\u002Fscripts\u002Fsend.sh \u003Csession-or-hint> \u003Cmessage-file>\n\n# Send via stdin\necho \"ping from hermes peer\" | ~\u002F.claude\u002Fskills\u002Ftmux-message\u002Fscripts\u002Fsend.sh nanoclaw -\n```\n\n`\u003Csession-or-hint>` accepts either an exact tmux session name OR a unique substring. `tmux ls` is grepped — if zero or multiple matches, the script aborts and lists them.\n\n## Workflow\n\n1. **Compose the message in a file**. Always prefix with an origin marker so the receiver knows where it came from:\n\n   ```\n   [from \u003Cmy-peer-id-or-cwd>]\n\n   \u003Cdirective body>\n   ```\n\n2. **Run send.sh**. It will:\n   - Resolve the session (exact → fuzzy)\n   - `capture-pane` and check for: idle `❯ ` prompt (good), activity spinner (warn), permission prompt (abort)\n   - `load-buffer` → `paste-buffer` → `Enter`\n   - Re-capture pane and report whether an activity indicator appeared (i.e. receiver submitted)\n\n3. **Inspect** the receiver afterwards if needed:\n   ```bash\n   tmux capture-pane -t \u003Csession> -p | tail -20\n   ```\n\n## Safety gates\n\nThe script aborts in these cases (override carefully):\n\n- **Permission prompt detected** (`Do you want to allow\u002Fapprove\u002Frun`) — paste would be captured by the prompt handler instead of routed as input. Always abort. No override.\n- **Mid-tool-call activity** (`✻`, `✢`, `⚒`, `Frosting…`, etc.) with no idle prompt visible — queueing into the current input buffer is risky. Override with `TMUX_MESSAGE_FORCE=1` only when you understand the receiver state.\n\n## Edge cases\n\n- **Long messages (>5KB)** — paste-buffer may exceed tmux buffer limits on some versions. Prefer writing the body to a file the receiver can read; the message you send is then just `see \u002Ftmp\u002Fhandoff-X.md`.\n- **Receiver at shell prompt (no Claude Code)** — paste still happens; Enter runs it as a shell command. Pre-flight catches absence of `❯ ` and warns.\n- **`Remote Control active` line in status bar** — indicates `\u002Fremote-control` skill is running on the receiver. Delivery still works.\n- **Multiple panes in the session** — script targets the active pane only. For multi-pane sessions, append `:0.0` (window:pane) to the session name in the first arg.\n\n## Tradeoffs\n\n- Tmux-only.\n- Receiver sees the message as if the user typed it. Provenance only via the `[from X]` prefix you include — no read receipts.\n- Post-flight check confirms an activity indicator appeared but not that the receiver actually understood the directive. Treat as \"delivered\" not \"actioned\".\n- Message files at `\u002Ftmp\u002Ftmux-message-*.txt` are NOT auto-cleaned; that's intentional for replay\u002Fdebugging. Sweep periodically.\n","# tmux-message\n\nDeliver a message to another Claude Code TUI session running in tmux. Use the bundled `scripts\u002Fsend.sh` — it handles session resolution, pre-flight safety checks, paste-buffer delivery, and post-flight verification.\n\n## When to use\n\n- claude-peers MCP `send_message` returned success but the receiver never acted on the message (silent failure mode observed in this fleet).\n- Sending a directive\u002Fhandoff to a peer Claude Code session whose tmux session name is known (full or fuzzy).\n- Need to inject a multi-line message into another Claude Code TUI prompt and submit it as if the user typed it.\n\nDo NOT use for — peers outside tmux, shell-only sessions (no Claude Code TUI), or one-shot commands you would just paste yourself.\n\n## Usage\n\n```bash\n# Send file content\n~\u002F.claude\u002Fskills\u002Ftmux-message\u002Fscripts\u002Fsend.sh \u003Csession-or-hint> \u003Cmessage-file>\n\n# Send via stdin\necho \"ping from hermes peer\" | ~\u002F.claude\u002Fskills\u002Ftmux-message\u002Fscripts\u002Fsend.sh nanoclaw -\n```\n\n`\u003Csession-or-hint>` accepts either an exact tmux session name OR a unique substring. `tmux ls` is grepped — if zero or multiple matches, the script aborts and lists them.\n\n## Workflow\n\n1. **Compose the message in a file**. Always prefix with an origin marker so the receiver knows where it came from:\n\n   ```\n   [from \u003Cmy-peer-id-or-cwd>]\n\n   \u003Cdirective body>\n   ```\n\n2. **Run send.sh**. It will:\n   - Resolve the session (exact → fuzzy)\n   - `capture-pane` and check for: idle `❯ ` prompt (good), activity spinner (warn), permission prompt (abort)\n   - `load-buffer` → `paste-buffer` → `Enter`\n   - Re-capture pane and report whether an activity indicator appeared (i.e. receiver submitted)\n\n3. **Inspect** the receiver afterwards if needed:\n   ```bash\n   tmux capture-pane -t \u003Csession> -p | tail -20\n   ```\n\n## Safety gates\n\nThe script aborts in these cases (override carefully):\n\n- **Permission prompt detected** (`Do you want to allow\u002Fapprove\u002Frun`) — paste would be captured by the prompt handler instead of routed as input. Always abort. No override.\n- **Mid-tool-call activity** (`✻`, `✢`, `⚒`, `Frosting…`, etc.) with no idle prompt visible — queueing into the current input buffer is risky. Override with `TMUX_MESSAGE_FORCE=1` only when you understand the receiver state.\n\n## Edge cases\n\n- **Long messages (>5KB)** — paste-buffer may exceed tmux buffer limits on some versions. Prefer writing the body to a file the receiver can read; the message you send is then just `see \u002Ftmp\u002Fhandoff-X.md`.\n- **Receiver at shell prompt (no Claude Code)** — paste still happens; Enter runs it as a shell command. Pre-flight catches absence of `❯ ` and warns.\n- **`Remote Control active` line in status bar** — indicates `\u002Fremote-control` skill is running on the receiver. Delivery still works.\n- **Multiple panes in the session** — script targets the active pane only. For multi-pane sessions, append `:0.0` (window:pane) to the session name in the first arg.\n\n## Tradeoffs\n\n- Tmux-only.\n- Receiver sees the message as if the user typed it. Provenance only via the `[from X]` prefix you include — no read receipts.\n- Post-flight check confirms an activity indicator appeared but not that the receiver actually understood the directive. Treat as \"delivered\" not \"actioned\".\n- Message files at `\u002Ftmp\u002Ftmux-message-*.txt` are NOT auto-cleaned; that's intentional for replay\u002Fdebugging. Sweep periodically.\n",{"name":5,"description":7},"main","9cf32d1e636db09530158af14ba301bfa5d401e9","skills\u002Ftmux-message","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-message",{"tool":37,"command":38},"bunx","bunx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-message",{"tool":40,"command":41},"pnpm","pnpm dlx skills add stevengonsalvez\u002Fainb-toolkit --skill tmux-message","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftmux-message\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Fsend.sh","SCRIPT","脚本",3884,"https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftmux-message\u002Fscripts\u002Fsend.sh",[52,59,66,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M75WK524MVT2H9E27ZCEA3HR","no-frontmatter","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fno-frontmatter\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]