[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GEN2C1Q4E40ZXM01VG3SH":3,"skill-same:01M75GEN2C1Q4E40ZXM01VG3SH":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75GEN2C1Q4E40ZXM01VG3SH","worker",null,"Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fworker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Foh-my-codex\u002Fskills\u002Fworker",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill worker",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill worker",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill worker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fworker\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]