[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E3GW66RTHA78CS78MRSCND":3,"skill-same:01M7E3GW66RTHA78CS78MRSCND":72},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M7E3GW66RTHA78CS78MRSCND","codex-delegate",null,"Delegate coding tasks to the OpenAI Codex CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: codex-delegate\ndescription: Delegate coding tasks to the OpenAI Codex CLI only when the user explicitly\n  requests it, while the orchestrator retains review and landing responsibility.\nrisk: critical\ncategory: agent-orchestration\nsource: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\nsource_repo: amElnagdy\u002Fdelegate-skills\nsource_type: community\ndate_added: '2026-08-26'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE\ncompatibility: Requires the `codex` CLI (OpenAI Codex) installed and authenticated,\n  Node 18+, and git. The orchestrating agent must be able to run shell commands and\n  read files. Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n# Codex Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `codex` implementer (`OpenAI Codex`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the OpenAI Codex CLI — then review what it produced and land it yourself. You write\nthe brief and own the judgment; Codex does the typing in its own sandbox; you verify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so it works the same whether you are Claude Code, OpenCode with a selected\nmodel, or any comparable agent. (It is designed for and run on Claude Code; treat other orchestrators\nas designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `codex` CLI is not installed or not authenticated (run `codex login`).\n- You want to write the code yourself, or you only need a review (use Codex's own `review` command).\n\n## Prerequisites (check once)\n\n1. `codex --version` succeeds. If not, install (`npm i -g @openai\u002Fcodex`) and `codex login`.\n2. **Confirm which `codex` is on PATH.** Multiple installs are common (e.g. a current npm\u002Fnvm copy and\n   a stale Homebrew one). `command -v codex` shows the active one and `codex --version` its version —\n   an old binary predates flags this skill relies on (`codex exec --json`, `-o`, `exec resume`). The\n   relay also records the version it ran into `result.json`, so a stale binary is visible after the fact.\n3. You are in (or will point `--cd` at) the target git repository.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nCodex sees **only** the text you send — no repo memory, no chat history, no shared context. Everything the\ntask needs goes in the brief: the goal, the current state, what to change, what to leave untouched,\nthe project's **actual** gate commands (discover them from the repo's CLAUDE.md\u002FAGENTS.md\u002FMakefile —\ndo not assume), and a report contract. Tell Codex it will **not** commit (you will). Keep one task per\nbrief. Full guidance and a template: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to Codex with the bundled helper. It wraps `codex exec`, captures the run, and writes a\nstructured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>` below is\nthis skill's installed directory — the folder containing this `SKILL.md`, i.e. the directory you loaded\nthe skill from. Claude Code prints it as \"Base directory for this skill\" when the skill loads; on other\norchestrators use that same directory — if unsure where it landed, run\n`find ~ -name relay.mjs -path '*codex-delegate*'` and substitute the directory above it.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# read-only (review\u002Fdiagnosis, no edits):   add --read-only\n# continue the exact Codex session:         add --session \u003CthreadId>  (from result.json; send only the delta brief)\n# fallback when no thread id is available:  add --resume-last\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to a write-capable (`workspace-write`) sandbox and writes its artifacts to a temp\ndir, so the repo under review stays clean. It **never commits** — see step 5. Mechanics, flags, and the\n`result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Codex finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and a stderr message and\n  writes no result file, so check the exit code too. A missing `codex` binary exits 127 but *does* write\n  a `result.json` with status `codex_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nCodex's `result.json` includes its own summary and gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did Codex do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\nBecause Codex's sandbox cannot reliably write `.git` (it varies by version, OS, and path), **the\norchestrator commits.** Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--session \u003CthreadId>` from the prior `result.json`\n  (use `--resume-last` only when no thread id is available), and review again.\n\n## Read-only second opinions\n\nThe relay doubles as a clean way to get an adversarial second opinion with no write risk: dispatch\n`--read-only` with a brief that lists the agreed points, then each contested point with both\npositions, and ask Codex to defend or concede each — deliverable in its final message, touching no\nfiles. Any delegation skill whose implementer offers a read-only mode supports the same use, but\ncheck how hard that mode's guarantee is first: Codex's sandbox enforces it, while Grok's is\nbest-effort and only flagged after the fact (`readOnlyViolation`) — for those implementers,\nverify `touchedFiles` came back empty instead of assuming no edits.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report Codex's design decisions, defensible-but-unasked turns, and\nnon-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## If you have the openai-codex plugin\n\nThe official openai-codex Claude Code plugin is excellent and **complementary** — `codex-delegate`\nbuilds on the same `codex` CLI, it doesn't replace the plugin. They point in different directions:\n\n- The plugin's `codex:codex-rescue` agent is a **forwarder**: it hands one task to Codex and returns\n  the output. It deliberately does not poll, review, or commit.\n- The plugin's review command and stop-review gate run the **inverse** direction: **Codex reviews your work**.\n- `codex-delegate` is the **orchestration loop in the other direction**: *you* drive Codex to\n  implement across one task or a queue, and *you* review and land each result. That loop — brief →\n  dispatch → poll → review → commit, with the orchestrator owning the commit — is what the plugin\n  leaves to you, and what this skill encodes.\n\nIf you have the plugin installed, its companion CLI is an optional alternative dispatch backend; the\nbundled `relay.mjs` is the default because it adds no install of its own beyond the `codex` binary\n(Node and `git`, which the relay also needs, are prerequisites for every skill here).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief Codex can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the exact-session rework cycle.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `codex` CLI, Node 18+, git.\n- Relay never commits — it only returns structured result JSON; you review and land the commit.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n","# Codex Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `codex` implementer (`OpenAI Codex`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the OpenAI Codex CLI — then review what it produced and land it yourself. You write\nthe brief and own the judgment; Codex does the typing in its own sandbox; you verify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so it works the same whether you are Claude Code, OpenCode with a selected\nmodel, or any comparable agent. (It is designed for and run on Claude Code; treat other orchestrators\nas designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `codex` CLI is not installed or not authenticated (run `codex login`).\n- You want to write the code yourself, or you only need a review (use Codex's own `review` command).\n\n## Prerequisites (check once)\n\n1. `codex --version` succeeds. If not, install (`npm i -g @openai\u002Fcodex`) and `codex login`.\n2. **Confirm which `codex` is on PATH.** Multiple installs are common (e.g. a current npm\u002Fnvm copy and\n   a stale Homebrew one). `command -v codex` shows the active one and `codex --version` its version —\n   an old binary predates flags this skill relies on (`codex exec --json`, `-o`, `exec resume`). The\n   relay also records the version it ran into `result.json`, so a stale binary is visible after the fact.\n3. You are in (or will point `--cd` at) the target git repository.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nCodex sees **only** the text you send — no repo memory, no chat history, no shared context. Everything the\ntask needs goes in the brief: the goal, the current state, what to change, what to leave untouched,\nthe project's **actual** gate commands (discover them from the repo's CLAUDE.md\u002FAGENTS.md\u002FMakefile —\ndo not assume), and a report contract. Tell Codex it will **not** commit (you will). Keep one task per\nbrief. Full guidance and a template: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to Codex with the bundled helper. It wraps `codex exec`, captures the run, and writes a\nstructured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>` below is\nthis skill's installed directory — the folder containing this `SKILL.md`, i.e. the directory you loaded\nthe skill from. Claude Code prints it as \"Base directory for this skill\" when the skill loads; on other\norchestrators use that same directory — if unsure where it landed, run\n`find ~ -name relay.mjs -path '*codex-delegate*'` and substitute the directory above it.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# read-only (review\u002Fdiagnosis, no edits):   add --read-only\n# continue the exact Codex session:         add --session \u003CthreadId>  (from result.json; send only the delta brief)\n# fallback when no thread id is available:  add --resume-last\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to a write-capable (`workspace-write`) sandbox and writes its artifacts to a temp\ndir, so the repo under review stays clean. It **never commits** — see step 5. Mechanics, flags, and the\n`result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Codex finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and a stderr message and\n  writes no result file, so check the exit code too. A missing `codex` binary exits 127 but *does* write\n  a `result.json` with status `codex_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nCodex's `result.json` includes its own summary and gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did Codex do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\nBecause Codex's sandbox cannot reliably write `.git` (it varies by version, OS, and path), **the\norchestrator commits.** Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--session \u003CthreadId>` from the prior `result.json`\n  (use `--resume-last` only when no thread id is available), and review again.\n\n## Read-only second opinions\n\nThe relay doubles as a clean way to get an adversarial second opinion with no write risk: dispatch\n`--read-only` with a brief that lists the agreed points, then each contested point with both\npositions, and ask Codex to defend or concede each — deliverable in its final message, touching no\nfiles. Any delegation skill whose implementer offers a read-only mode supports the same use, but\ncheck how hard that mode's guarantee is first: Codex's sandbox enforces it, while Grok's is\nbest-effort and only flagged after the fact (`readOnlyViolation`) — for those implementers,\nverify `touchedFiles` came back empty instead of assuming no edits.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report Codex's design decisions, defensible-but-unasked turns, and\nnon-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## If you have the openai-codex plugin\n\nThe official openai-codex Claude Code plugin is excellent and **complementary** — `codex-delegate`\nbuilds on the same `codex` CLI, it doesn't replace the plugin. They point in different directions:\n\n- The plugin's `codex:codex-rescue` agent is a **forwarder**: it hands one task to Codex and returns\n  the output. It deliberately does not poll, review, or commit.\n- The plugin's review command and stop-review gate run the **inverse** direction: **Codex reviews your work**.\n- `codex-delegate` is the **orchestration loop in the other direction**: *you* drive Codex to\n  implement across one task or a queue, and *you* review and land each result. That loop — brief →\n  dispatch → poll → review → commit, with the orchestrator owning the commit — is what the plugin\n  leaves to you, and what this skill encodes.\n\nIf you have the plugin installed, its companion CLI is an optional alternative dispatch backend; the\nbundled `relay.mjs` is the default because it adds no install of its own beyond the `codex` binary\n(Node and `git`, which the relay also needs, are prerequisites for every skill here).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief Codex can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the exact-session rework cycle.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `codex` CLI, Node 18+, git.\n- Relay never commits — it only returns structured result JSON; you review and land the commit.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n",{"name":5,"risk":24,"source":25,"license":15,"category":26,"metadata":27,"date_added":29,"description":7,"source_repo":30,"source_type":31,"compatibility":32,"license_source":33},"critical","https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills","agent-orchestration",{"version":28},"0.5.0","2026-08-26","amElnagdy\u002Fdelegate-skills","community","Requires the `codex` CLI (OpenAI Codex) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).","https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fagent-orchestration\u002Fcodex-delegate","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill codex-delegate",{"tool":46,"command":47},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill codex-delegate",{"tool":49,"command":50},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill codex-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",11493,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fmulti-task-queues.md",3741,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Freview-and-land.md",7877,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002Freferences\u002Freview-and-land.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fwriting-the-brief.md",6072,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fcodex-delegate\u002Freferences\u002Fwriting-the-brief.md",[73,81,88,95,102,109],{"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":80},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":80},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":80},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":80},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":80},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":80},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]