[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754R77HE0S157B625MAN2W0":3,"skill-same:01M754R77HE0S157B625MAN2W0":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M754R77HE0S157B625MAN2W0","codex-plan-writer",null,"Use for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.","Bang-isme\u002FAgencyCLI","Bang-isme","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F179383529?v=4","01M754NDM8K05SAX2V31R63WEE","01M754NDMV48ECFT4HY6X2CKQ0",2,"MIT","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-plan-writer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: codex-plan-writer\ndescription: Use for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.\nload_priority: on-demand\n---\n\n## TL;DR\nCreate `{task-slug}.md` plan file for complex requests. Map file structure first. Required sections: Overview, Success Criteria, Tech Stack, File Structure, Task Breakdown (TDD steps, dependencies, verify), Phase X Checklist. No placeholders. Self-review before presenting. Offer execution handoff. Wait for user approval.\n\n# Plan Writer\n\n## Activation\n\n1. Activate during workflow planning phases.\n2. Activate on explicit `$codex-plan-writer` or `$plan`.\n3. Mandatory for complex requests with scope `medium` or `large`.\n\n**Announce at start:** \"I'm using codex-plan-writer to create the implementation plan.\"\n\n## Output File Naming\n\n- Derive a short kebab-case slug from the task intent (2-3 keywords).\n- Maximum 30 characters.\n- Examples: `ecommerce-cart.md`, `login-fix.md`, `dark-mode.md`.\n\n## Output Location\n\nWrite plan file to project root: `.\u002F{task-slug}.md`\n\n## Scope Check\n\nIf the spec covers multiple independent subsystems, it should have been broken into sub-project specs during the design phase. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** Use `$sdd` (codex-subagent-execution) or execute inline.\n> Follow `$tdd` (RED-GREEN-REFACTOR) for each implementation step.\n> to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Required Plan Structure\n\n### 1. Overview\n\n- what is being built or changed\n- why it matters\n\n### 2. Success Criteria\n\n- measurable \"done\" conditions\n\n### 3. Tech Stack (if relevant)\n\n- selected technologies and rationale\n\n### 4. File Structure\n\n**Before defining tasks, map out which files will be created or modified and what each one is responsible for.** This is where decomposition decisions get locked in.\n\n- Design units with clear boundaries and well-defined interfaces\n- Each file should have one clear responsibility\n- Prefer smaller, focused files over large ones\n- Files that change together should live together\n- Split by responsibility, not by technical layer\n- In existing codebases, follow established patterns\n\nThis structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.\n\n### 5. Task Breakdown\n\nFor each task include:\n\n- task name and id\n- domain (`frontend | backend | mobile | debug`)\n- priority (`P0 | P1 | P2 | P3`)\n- dependencies\n- input\n- output\n- verify method\n- rollback strategy\n\n### 5.5 Evidence & Monitoring\n\nFor medium or high-risk tasks, also include:\n\n- what evidence is required before claiming success\n- what signal should be monitored after the change\n- what drift or failure would look like\n- what fallback path exists if the signal goes red\n\n### 6. Phase X Verification Checklist\n\n- lint passes\n- tests pass\n- security scan reviewed\n- all tasks completed\n- `$gate` passes\n\n## Plan Granularity: Bite-Sized Tasks\n\nEach task in an implementation plan should be **completable in 2-5 minutes**. Break down as follows:\n1. \"Write the failing test\" - one step\n2. \"Run it to verify it fails\" - one step\n3. \"Implement minimal code to pass\" - one step\n4. \"Run tests to verify they pass\" - one step\n5. \"Commit\" - one step\n\n### Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n- [ ] **Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n- [ ] **Step 2: Run test to verify it fails**\n\nRun: `python -m pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n- [ ] **Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n- [ ] **Step 4: Run test to verify it passes**\n\nRun: `python -m pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n- [ ] **Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\nEach task MUST include:\n- **Files:** Exact paths to create\u002Fmodify\u002Ftest\n- **Code:** Complete code (not \"add validation here\")\n- **Commands:** Exact commands with expected output\n- **Verification:** How to confirm this task is done\n- **Evidence:** What makes the step specific and believable\n\n## No Placeholders\n\nEvery step must contain the actual content an engineer needs. These are **plan failures** — never write them:\n- \"TBD\", \"TODO\", \"implement later\", \"fill in details\"\n- \"Add appropriate error handling\" \u002F \"add validation\" \u002F \"handle edge cases\"\n- \"Write tests for the above\" (without actual test code)\n- \"Similar to Task N\" (repeat the code — the engineer may be reading tasks out of order)\n- Steps that describe what to do without showing how (code blocks required for code steps)\n- References to types, functions, or methods not defined in any task\n\n## Rules\n\n- Do not use vague placeholders in implementation tasks.\n- Keep tasks small and verifiable.\n- Explain why each task exists, not only what to do.\n- Exact file paths always.\n- Complete code in every step — if a step changes code, show the code.\n- Exact commands with expected output.\n- DRY, YAGNI, TDD, frequent commits.\n\n## Self-Review\n\nAfter writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.\n\n**1. Spec coverage:** Skim each section\u002Frequirement in the spec. Can you point to a task that implements it? List any gaps.\n\n**2. Placeholder scan:** Search your plan for red flags — any of the patterns from the \"No Placeholders\" section above. Fix them.\n\n**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.\n\nIf you find issues, fix them inline. If you find a spec requirement with no task, add the task.\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `.\u002F{task-slug}.md`. Two execution options:**\n\n**1. Subagent-Driven (`$sdd`)** — I dispatch a fresh subagent per task, review between tasks, fast iteration\n\n**2. Inline Execution** — Execute tasks in this session, batch execution with checkpoints\n\n**Which approach?\"**\n\n**If Subagent-Driven chosen:**\n- Use `codex-subagent-execution` skill\n- Fresh subagent per task + two-stage review\n\n**If Inline Execution chosen:**\n- Execute tasks sequentially in current session\n- Run `$gate` after each batch of 3 tasks\n\n## Script Invocation Discipline\n\n1. When plan execution calls scripts from other skills, run `--help` first.\n2. Treat scripts as black-box helpers and execute by contract.\n3. Read script source only when customization or bug fixing is required.\n\n## Exit Gate\n\nPlan writing is complete only when:\n\n1. plan file exists at `.\u002F{task-slug}.md`\n2. all required sections exist (including File Structure and No Placeholders)\n3. self-review completed (spec coverage, placeholder scan, type consistency)\n4. the plan can survive strict deliverable validation via `run_gate.py --output-file \u003Cplan.md>` without falling back to generic filler\n5. user has reviewed and approved the plan\n\n## Reference Files\n\n- `references\u002Fplan-document-reviewer-prompt.md`: subagent dispatch template for automated plan quality verification.\n\n## Related Skills\n\n| Skill | Integration |\n| --- | --- |\n| `codex-subagent-execution` | Executes the plan this skill produces |\n| `codex-test-driven-development` | Each task follows TDD cycle |\n| `codex-verification-discipline` | Verify before claiming plan is complete |\n| `codex-branch-finisher` | After all plan tasks complete, use `$finish` |\n","## TL;DR\nCreate `{task-slug}.md` plan file for complex requests. Map file structure first. Required sections: Overview, Success Criteria, Tech Stack, File Structure, Task Breakdown (TDD steps, dependencies, verify), Phase X Checklist. No placeholders. Self-review before presenting. Offer execution handoff. Wait for user approval.\n\n# Plan Writer\n\n## Activation\n\n1. Activate during workflow planning phases.\n2. Activate on explicit `$codex-plan-writer` or `$plan`.\n3. Mandatory for complex requests with scope `medium` or `large`.\n\n**Announce at start:** \"I'm using codex-plan-writer to create the implementation plan.\"\n\n## Output File Naming\n\n- Derive a short kebab-case slug from the task intent (2-3 keywords).\n- Maximum 30 characters.\n- Examples: `ecommerce-cart.md`, `login-fix.md`, `dark-mode.md`.\n\n## Output Location\n\nWrite plan file to project root: `.\u002F{task-slug}.md`\n\n## Scope Check\n\nIf the spec covers multiple independent subsystems, it should have been broken into sub-project specs during the design phase. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** Use `$sdd` (codex-subagent-execution) or execute inline.\n> Follow `$tdd` (RED-GREEN-REFACTOR) for each implementation step.\n> to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Required Plan Structure\n\n### 1. Overview\n\n- what is being built or changed\n- why it matters\n\n### 2. Success Criteria\n\n- measurable \"done\" conditions\n\n### 3. Tech Stack (if relevant)\n\n- selected technologies and rationale\n\n### 4. File Structure\n\n**Before defining tasks, map out which files will be created or modified and what each one is responsible for.** This is where decomposition decisions get locked in.\n\n- Design units with clear boundaries and well-defined interfaces\n- Each file should have one clear responsibility\n- Prefer smaller, focused files over large ones\n- Files that change together should live together\n- Split by responsibility, not by technical layer\n- In existing codebases, follow established patterns\n\nThis structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.\n\n### 5. Task Breakdown\n\nFor each task include:\n\n- task name and id\n- domain (`frontend | backend | mobile | debug`)\n- priority (`P0 | P1 | P2 | P3`)\n- dependencies\n- input\n- output\n- verify method\n- rollback strategy\n\n### 5.5 Evidence & Monitoring\n\nFor medium or high-risk tasks, also include:\n\n- what evidence is required before claiming success\n- what signal should be monitored after the change\n- what drift or failure would look like\n- what fallback path exists if the signal goes red\n\n### 6. Phase X Verification Checklist\n\n- lint passes\n- tests pass\n- security scan reviewed\n- all tasks completed\n- `$gate` passes\n\n## Plan Granularity: Bite-Sized Tasks\n\nEach task in an implementation plan should be **completable in 2-5 minutes**. Break down as follows:\n1. \"Write the failing test\" - one step\n2. \"Run it to verify it fails\" - one step\n3. \"Implement minimal code to pass\" - one step\n4. \"Run tests to verify they pass\" - one step\n5. \"Commit\" - one step\n\n### Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n- [ ] **Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n- [ ] **Step 2: Run test to verify it fails**\n\nRun: `python -m pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n- [ ] **Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n- [ ] **Step 4: Run test to verify it passes**\n\nRun: `python -m pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n- [ ] **Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\nEach task MUST include:\n- **Files:** Exact paths to create\u002Fmodify\u002Ftest\n- **Code:** Complete code (not \"add validation here\")\n- **Commands:** Exact commands with expected output\n- **Verification:** How to confirm this task is done\n- **Evidence:** What makes the step specific and believable\n\n## No Placeholders\n\nEvery step must contain the actual content an engineer needs. These are **plan failures** — never write them:\n- \"TBD\", \"TODO\", \"implement later\", \"fill in details\"\n- \"Add appropriate error handling\" \u002F \"add validation\" \u002F \"handle edge cases\"\n- \"Write tests for the above\" (without actual test code)\n- \"Similar to Task N\" (repeat the code — the engineer may be reading tasks out of order)\n- Steps that describe what to do without showing how (code blocks required for code steps)\n- References to types, functions, or methods not defined in any task\n\n## Rules\n\n- Do not use vague placeholders in implementation tasks.\n- Keep tasks small and verifiable.\n- Explain why each task exists, not only what to do.\n- Exact file paths always.\n- Complete code in every step — if a step changes code, show the code.\n- Exact commands with expected output.\n- DRY, YAGNI, TDD, frequent commits.\n\n## Self-Review\n\nAfter writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.\n\n**1. Spec coverage:** Skim each section\u002Frequirement in the spec. Can you point to a task that implements it? List any gaps.\n\n**2. Placeholder scan:** Search your plan for red flags — any of the patterns from the \"No Placeholders\" section above. Fix them.\n\n**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.\n\nIf you find issues, fix them inline. If you find a spec requirement with no task, add the task.\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `.\u002F{task-slug}.md`. Two execution options:**\n\n**1. Subagent-Driven (`$sdd`)** — I dispatch a fresh subagent per task, review between tasks, fast iteration\n\n**2. Inline Execution** — Execute tasks in this session, batch execution with checkpoints\n\n**Which approach?\"**\n\n**If Subagent-Driven chosen:**\n- Use `codex-subagent-execution` skill\n- Fresh subagent per task + two-stage review\n\n**If Inline Execution chosen:**\n- Execute tasks sequentially in current session\n- Run `$gate` after each batch of 3 tasks\n\n## Script Invocation Discipline\n\n1. When plan execution calls scripts from other skills, run `--help` first.\n2. Treat scripts as black-box helpers and execute by contract.\n3. Read script source only when customization or bug fixing is required.\n\n## Exit Gate\n\nPlan writing is complete only when:\n\n1. plan file exists at `.\u002F{task-slug}.md`\n2. all required sections exist (including File Structure and No Placeholders)\n3. self-review completed (spec coverage, placeholder scan, type consistency)\n4. the plan can survive strict deliverable validation via `run_gate.py --output-file \u003Cplan.md>` without falling back to generic filler\n5. user has reviewed and approved the plan\n\n## Reference Files\n\n- `references\u002Fplan-document-reviewer-prompt.md`: subagent dispatch template for automated plan quality verification.\n\n## Related Skills\n\n| Skill | Integration |\n| --- | --- |\n| `codex-subagent-execution` | Executes the plan this skill produces |\n| `codex-test-driven-development` | Each task follows TDD cycle |\n| `codex-verification-discipline` | Verify before claiming plan is complete |\n| `codex-branch-finisher` | After all plan tasks complete, use `$finish` |\n",{"name":5,"description":7,"load_priority":23},"on-demand","main","19b976c6b4f182f06d2d2e6b030549f2f8a69cc0","packages\u002Fcli\u002Fskills\u002Fcodex-plan-writer",0,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI","https:\u002F\u002Fgithub.com\u002FBang-isme","Hi my name is jeff","2026-07-15 19:58:17",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Bang-isme\u002FAgencyCLI --skill codex-plan-writer",{"tool":38,"command":39},"bunx","bunx skills add Bang-isme\u002FAgencyCLI --skill codex-plan-writer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Bang-isme\u002FAgencyCLI --skill codex-plan-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-plan-writer\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",225,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-plan-writer\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fplan-document-reviewer-prompt.md",1916,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-plan-writer\u002Freferences\u002Fplan-document-reviewer-prompt.md",[57,64,71,78,84,91],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M754T5CB6WCXB2AV8N0M50AC","codex-test-driven-development","Fixture stub for TDD skill.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-test-driven-development\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M754T41J59TG0MJYC52TES58","codex-subagent-execution","Fixture stub for subagent execution skill.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-subagent-execution\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M754T2JDSPA3YF83FK6BMNV6","codex-runtime-hook","Fixture stub for runtime hook skill.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-runtime-hook\u002FSKILL.md",[],[],{"skillNo":79,"name":5,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M754T1HG4JRTJVZC2PBFTXDT","Fixture stub for plan writer skill.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-plan-writer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M754SZJVZKGQR5PSA6YFFY09","codex-execution-quality-gate","Fixture stub for quality gate skill.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-execution-quality-gate\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M754SXBJ1DE0JR6TK0XJ4SAK","codex-demo","Minimal fixture skill for Agency CLI skill-md parser tests.","https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-skills\u002Fcodex-demo\u002FSKILL.md",[],[]]