[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDXQ1G2GNAVRXDJ78FZC7N":3,"skill-same:01M6XDXQ1G2GNAVRXDJ78FZC7N":53},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6XDXQ1G2GNAVRXDJ78FZC7N","worker",null,"Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcodex\u002Fworker\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27],"tmux","teams","protocol","lifecycle","team","task","mailbox","ack","for","2026-11-10 10:12:30",false,"---\nname: worker\ndescription: Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams\n---\n\n# Worker Skill\n\nThis skill is for a Codex session that was started as an OMX Team worker (a tmux pane spawned by `$team`).\n\n## Identity\n\nYou MUST be running with `OMX_TEAM_WORKER` set. It looks like:\n\n`\u003Cteam-name>\u002Fworker-\u003Cn>`\n\nExample: `alpha\u002Fworker-2`\n\n## Load Worker Skill Path (Claude\u002FCodex)\n\nWhen a worker inbox tells you to load this skill, resolve the first existing path:\n\n1. `${CODEX_HOME:-~\u002F.codex}\u002Fskills\u002Fworker\u002FSKILL.md`\n2. `~\u002F.codex\u002Fskills\u002Fworker\u002FSKILL.md`\n3. `\u003Cleader_cwd>\u002F.codex\u002Fskills\u002Fworker\u002FSKILL.md`\n4. `\u003Cleader_cwd>\u002Fskills\u002Fworker\u002FSKILL.md` (repo fallback)\n\n## Startup Protocol (ACK)\n\n1. Parse `OMX_TEAM_WORKER` into:\n   - `teamName` (before the `\u002F`)\n   - `workerName` (after the `\u002F`, usually `worker-\u003Cn>`)\n2. Send a startup ACK to the lead mailbox **before task work**:\n   - Recipient worker id: `leader-fixed`\n   - Body: one short deterministic line (recommended: `ACK: \u003CworkerName> initialized`).\n3. After ACK, proceed to your inbox instructions.\n\nThe lead will see your message in:\n\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fmailbox\u002Fleader-fixed.json`\n\nUse CLI interop:\n- `omx team api send-message --input \u003Cjson> --json` with `{team_name, from_worker, to_worker:\"leader-fixed\", body}`\n\nCopy\u002Fpaste template:\n\n```bash\nomx team api send-message --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"from_worker\\\":\\\"\u003CworkerName>\\\",\\\"to_worker\\\":\\\"leader-fixed\\\",\\\"body\\\":\\\"ACK: \u003CworkerName> initialized\\\"}\" --json\n```\n\n## Inbox + Tasks\n\n1. Resolve canonical team state root in this order:\n   1) `OMX_TEAM_STATE_ROOT` env\n   2) worker identity `team_state_root`\n   3) team config\u002Fmanifest `team_state_root`\n   4) local cwd fallback (`.omx\u002Fstate`)\n2. Read your inbox:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fworkers\u002F\u003CworkerName>\u002Finbox.md`\n3. Pick the first unblocked task assigned to you.\n4. Read the task file:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Ftasks\u002Ftask-\u003Cid>.json` (example: `task-1.json`)\n5. Task id format:\n   - The MCP\u002Fstate API uses the numeric id (`\"1\"`), not `\"task-1\"`.\n   - Never use legacy `tasks\u002F{id}.json` wording.\n6. Claim the task (do NOT start work without a claim) using claim-safe lifecycle CLI interop (`omx team api claim-task --json`).\n7. Do the work.\n8. Complete\u002Ffail the task via lifecycle transition CLI interop (`omx team api transition-task-status --json`) from `in_progress` to `completed` or `failed`.\n   - Do NOT directly write lifecycle fields (`status`, `owner`, `result`, `error`) in task files.\n9. Use `omx team api release-task-claim --json` only for rollback\u002Frequeue to `pending` (not for completion).\n10. Update your worker status:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fworkers\u002F\u003CworkerName>\u002Fstatus.json` with `{\"state\":\"idle\", ...}`\n\n## Mailbox\n\nCheck your mailbox for messages:\n\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fmailbox\u002F\u003CworkerName>.json`\n\nWhen notified, read messages and follow any instructions. Use short ACK replies when appropriate.\n\nNote: leader dispatch is state-first. The durable queue lives at:\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fdispatch\u002Frequests.json`\nHooks\u002Fwatchers may nudge you after mailbox\u002Finbox state is already written.\n\nUse CLI interop:\n- `omx team api mailbox-list --json` to read\n- `omx team api mailbox-mark-delivered --json` to acknowledge delivery\n\nCopy\u002Fpaste templates:\n\n```bash\nomx team api mailbox-list --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"worker\\\":\\\"\u003CworkerName>\\\"}\" --json\nomx team api mailbox-mark-delivered --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"worker\\\":\\\"\u003CworkerName>\\\",\\\"message_id\\\":\\\"\u003CMESSAGE_ID>\\\"}\" --json\n```\n\n## Dispatch Discipline (state-first)\n\nWorker sessions should treat team state + CLI interop as the source of truth.\n\n- Prefer inbox\u002Fmailbox\u002Ftask state and `omx team api ... --json` operations.\n- Do **not** rely on ad-hoc tmux keystrokes as a primary delivery channel.\n- If a manual trigger arrives (for example `tmux send-keys` nudge), treat it only as a prompt to re-check state and continue through the normal claim-safe lifecycle.\n\n## Shutdown\n\nIf the lead sends a shutdown request, follow the shutdown inbox instructions exactly, write your shutdown ack file, then exit the Codex session.\n","# Worker Skill\n\nThis skill is for a Codex session that was started as an OMX Team worker (a tmux pane spawned by `$team`).\n\n## Identity\n\nYou MUST be running with `OMX_TEAM_WORKER` set. It looks like:\n\n`\u003Cteam-name>\u002Fworker-\u003Cn>`\n\nExample: `alpha\u002Fworker-2`\n\n## Load Worker Skill Path (Claude\u002FCodex)\n\nWhen a worker inbox tells you to load this skill, resolve the first existing path:\n\n1. `${CODEX_HOME:-~\u002F.codex}\u002Fskills\u002Fworker\u002FSKILL.md`\n2. `~\u002F.codex\u002Fskills\u002Fworker\u002FSKILL.md`\n3. `\u003Cleader_cwd>\u002F.codex\u002Fskills\u002Fworker\u002FSKILL.md`\n4. `\u003Cleader_cwd>\u002Fskills\u002Fworker\u002FSKILL.md` (repo fallback)\n\n## Startup Protocol (ACK)\n\n1. Parse `OMX_TEAM_WORKER` into:\n   - `teamName` (before the `\u002F`)\n   - `workerName` (after the `\u002F`, usually `worker-\u003Cn>`)\n2. Send a startup ACK to the lead mailbox **before task work**:\n   - Recipient worker id: `leader-fixed`\n   - Body: one short deterministic line (recommended: `ACK: \u003CworkerName> initialized`).\n3. After ACK, proceed to your inbox instructions.\n\nThe lead will see your message in:\n\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fmailbox\u002Fleader-fixed.json`\n\nUse CLI interop:\n- `omx team api send-message --input \u003Cjson> --json` with `{team_name, from_worker, to_worker:\"leader-fixed\", body}`\n\nCopy\u002Fpaste template:\n\n```bash\nomx team api send-message --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"from_worker\\\":\\\"\u003CworkerName>\\\",\\\"to_worker\\\":\\\"leader-fixed\\\",\\\"body\\\":\\\"ACK: \u003CworkerName> initialized\\\"}\" --json\n```\n\n## Inbox + Tasks\n\n1. Resolve canonical team state root in this order:\n   1) `OMX_TEAM_STATE_ROOT` env\n   2) worker identity `team_state_root`\n   3) team config\u002Fmanifest `team_state_root`\n   4) local cwd fallback (`.omx\u002Fstate`)\n2. Read your inbox:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fworkers\u002F\u003CworkerName>\u002Finbox.md`\n3. Pick the first unblocked task assigned to you.\n4. Read the task file:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Ftasks\u002Ftask-\u003Cid>.json` (example: `task-1.json`)\n5. Task id format:\n   - The MCP\u002Fstate API uses the numeric id (`\"1\"`), not `\"task-1\"`.\n   - Never use legacy `tasks\u002F{id}.json` wording.\n6. Claim the task (do NOT start work without a claim) using claim-safe lifecycle CLI interop (`omx team api claim-task --json`).\n7. Do the work.\n8. Complete\u002Ffail the task via lifecycle transition CLI interop (`omx team api transition-task-status --json`) from `in_progress` to `completed` or `failed`.\n   - Do NOT directly write lifecycle fields (`status`, `owner`, `result`, `error`) in task files.\n9. Use `omx team api release-task-claim --json` only for rollback\u002Frequeue to `pending` (not for completion).\n10. Update your worker status:\n   `\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fworkers\u002F\u003CworkerName>\u002Fstatus.json` with `{\"state\":\"idle\", ...}`\n\n## Mailbox\n\nCheck your mailbox for messages:\n\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fmailbox\u002F\u003CworkerName>.json`\n\nWhen notified, read messages and follow any instructions. Use short ACK replies when appropriate.\n\nNote: leader dispatch is state-first. The durable queue lives at:\n`\u003Cteam_state_root>\u002Fteam\u002F\u003CteamName>\u002Fdispatch\u002Frequests.json`\nHooks\u002Fwatchers may nudge you after mailbox\u002Finbox state is already written.\n\nUse CLI interop:\n- `omx team api mailbox-list --json` to read\n- `omx team api mailbox-mark-delivered --json` to acknowledge delivery\n\nCopy\u002Fpaste templates:\n\n```bash\nomx team api mailbox-list --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"worker\\\":\\\"\u003CworkerName>\\\"}\" --json\nomx team api mailbox-mark-delivered --input \"{\\\"team_name\\\":\\\"\u003CteamName>\\\",\\\"worker\\\":\\\"\u003CworkerName>\\\",\\\"message_id\\\":\\\"\u003CMESSAGE_ID>\\\"}\" --json\n```\n\n## Dispatch Discipline (state-first)\n\nWorker sessions should treat team state + CLI interop as the source of truth.\n\n- Prefer inbox\u002Fmailbox\u002Ftask state and `omx team api ... --json` operations.\n- Do **not** rely on ad-hoc tmux keystrokes as a primary delivery channel.\n- If a manual trigger arrives (for example `tmux send-keys` nudge), treat it only as a prompt to re-check state and continue through the normal claim-safe lifecycle.\n\n## Shutdown\n\nIf the lead sends a shutdown request, follow the shutdown inbox instructions exactly, write your shutdown ack file, then exit the Codex session.\n",{"name":5,"description":7},"main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcodex\u002Fworker","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill worker",{"tool":45,"command":46},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill worker",{"tool":48,"command":49},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill worker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcodex\u002Fworker\u002FSKILL.md",true,[],[54,64,71,79,85,93],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M72R8PZX1ABFHJGTYPA4CAF1","webapp-testing","To test local web applications, write native Python Playwright scripts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fwebapp-testing\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"01M72QG37MMZNDY7X7GXPAK5W6","python-packaging","Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fpython-packaging\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":63},"01M72NXR0QMP9G46TW6A2DH59C","canvas-design","These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fcanvas-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fcanvas-design\u002FSKILL.md",[],[],{"skillNo":80,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":63},"01M72N55TK3EEQ4QK4AWDC2KZS","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":63},"01M72MTWC150CFAP4Y5GSNKF80","slack-gif-creator","A toolkit providing utilities and knowledge for creating animated GIFs optimized for Slack.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fslack-gif-creator\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":63},"01M72KPT3VVNSP88MNAY466TZT","frontend-design","You are a frontend designer-engineer, not a layout generator.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Ffrontend-design\u002FSKILL.md",[],[]]