[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754Q37TKPNN5BFCZ7K1MXP5":3,"skill-same:01M754Q37TKPNN5BFCZ7K1MXP5":84},{"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},"01M754Q37TKPNN5BFCZ7K1MXP5","codex-document-writer",null,"Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.","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-document-writer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: codex-document-writer\ndescription: Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.\nload_priority: on-demand\n---\n\n## TL;DR\nLoad before writing or revising any document, report, proposal, memo, guide, academic paper, or long-form explanation. The goal is reader clarity: correct context, full meaning, professional structure, reliable tone, compact wording, proper diagrams, and polished formatting — without making the reader infer missing intent.\n\n## Activation\n\n1. Activate when the task involves drafting, rewriting, summarizing, formatting, or improving documents, reports, memos, proposals, guides, handoffs, emails, academic papers, or formal text.\n2. Activate on `$doc`, `$report`, `$write`, `$diagram`, `$báo-cáo`, \"soạn tài liệu\", \"viết báo cáo\", \"làm văn bản chuyên nghiệp\", \"viết rõ ràng hơn\", \"vẽ sơ đồ\".\n3. Auto-load with `codex-reasoning-rigor` when the document is decision-heavy, high-stakes, or evidence-based.\n4. Auto-load with `codex-doc-renderer` when the deliverable is `.docx`.\n\n## Hard Rules\n\n- Always identify purpose, audience, context, and expected use before choosing wording.\n- Start with the document outcome, not background narration.\n- Use complete sentences with explicit actor, action, object, and outcome.\n- Keep each paragraph focused on one message; do not make the reader infer the point.\n- Be detailed where meaning depends on detail, but remove filler, repeated framing, and synonym stacking.\n- Use humble, reliable wording: state what is verified, what is inferred, and what remains uncertain.\n- Do not overclaim. Avoid \"clearly\", \"obviously\", \"guaranteed\", \"always\", and \"never\" unless evidence supports them.\n- For Vietnamese, use natural UTF-8 Vietnamese, correct context labels, and professional but readable wording.\n- Every diagram must answer a specific question. No decorative diagrams.\n- Every report section must earn its place. No empty sections or placeholder text.\n\n## Document Flow\n\nBefore drafting:\n\n1. Determine document type and reader.\n2. Pick the matching structure:\n   - For reports → `references\u002Freport-structures.md`\n   - For general documents → `references\u002Fdocument-types.md`\n   - For academic\u002Funiversity work → `references\u002Facademic-report-patterns.md`\n3. Add diagrams where visual explanation is needed → `references\u002Fdiagram-patterns.md`\n4. Apply content writing patterns → `references\u002Fcontent-writing-patterns.md`\n5. Apply sentence rules from `references\u002Fsentence-quality.md`.\n6. Apply reliability rules from `references\u002Ftone-reliability.md`.\n7. Apply Vietnamese wording rules from `references\u002Fvietnamese-style.md` when writing Vietnamese.\n8. Apply formatting rules from `references\u002Fformatting.md`.\n\n## Diagram Integration Protocol\n\nWhen the document needs visual explanation:\n\n1. Check `references\u002Fdiagram-patterns.md` → Diagram Selection Decision Table\n2. Choose the simplest diagram type that answers the reader's question\n3. Use Mermaid syntax for rendered documents, ASCII for plain text\n4. Add a caption\u002Ftitle before every diagram\n5. Limit: max 15 nodes per diagram, split if larger\n6. Verify render before delivering\n\n### Quick Diagram Dispatch\n\n| Need | Diagram Type | Mermaid Keyword |\n|---|---|---|\n| System architecture | Flowchart with subgraphs | `flowchart TB` |\n| API interaction flow | Sequence diagram | `sequenceDiagram` |\n| Database schema | ER diagram | `erDiagram` |\n| Status\u002Fworkflow transitions | State diagram | `stateDiagram-v2` |\n| Project timeline | Gantt chart | `gantt` |\n| Branch strategy | Git graph | `gitGraph` |\n| Feature breakdown | Mind map | `mindmap` |\n| Distribution\u002Fproportion | Pie chart | `pie` |\n| Milestone overview | Timeline | `timeline` |\n\n## Report Type Router\n\n| Signal in User Request | Load Reference |\n|---|---|\n| \"báo cáo tiến độ\", \"progress report\" | `references\u002Freport-structures.md` → Progress Report |\n| \"phân tích\", \"analysis\", \"analytical\" | `references\u002Freport-structures.md` → Analytical Report |\n| \"đề xuất\", \"proposal\" | `references\u002Freport-structures.md` → Proposal |\n| \"sprint report\", \"release notes\" | `references\u002Freport-structures.md` → Sprint Report |\n| \"incident\", \"postmortem\", \"sự cố\" | `references\u002Freport-structures.md` → Incident Report |\n| \"đồ án\", \"assignment\", \"bài tập lớn\", \"luận văn\" | `references\u002Facademic-report-patterns.md` |\n| \"memo\", \"update\", \"thông báo\" | `references\u002Fdocument-types.md` → Business Memo |\n| \"hướng dẫn\", \"guide\", \"tutorial\" | `references\u002Fdocument-types.md` → User Guide |\n| \"handoff\", \"bàn giao\" | `references\u002Fdocument-types.md` → Session Handoff |\n| \"README\", \"documentation\" | `references\u002Fcontent-writing-patterns.md` → README Template |\n\n## Quality Gate (Before Delivery)\n\nBefore delivering any document:\n\n- [ ] First section answers the reader's primary question\n- [ ] Every claim backed by evidence\n- [ ] Tables used for comparisons, not narratives\n- [ ] Every diagram has a caption and answers a specific question\n- [ ] Metrics shown with target vs actual\n- [ ] Clear \"Next Steps\" or \"Required Decision\" section\n- [ ] Risks listed with severity AND mitigation\n- [ ] For Vietnamese: proper section headings and figure\u002Ftable numbering\n- [ ] Scannable: headings + tables alone convey the gist\n- [ ] No wall-of-text paragraphs (max 5-6 lines per paragraph)\n- [ ] No \"empty calories\" phrases (\"it is important to note that...\", \"in order to...\")\n\n## Reference Files\n\n- `references\u002Fdocument-types.md`: templates for reports, memos, proposals, guides, handoffs, summaries, and executive updates.\n- `references\u002Freport-structures.md`: 8 report types — progress, analytical, proposal, comparison, sprint, incident, research, and Vietnamese academic.\n- `references\u002Fdiagram-patterns.md`: complete Mermaid diagram reference — flowchart, sequence, ER, state, Gantt, C4, journey, mindmap, pie, gitGraph, timeline + ASCII alternatives + quality rules.\n- `references\u002Fcontent-writing-patterns.md`: PREP framework, heading hierarchy, active voice, \"So What?\" test, Vietnamese content patterns, anti-patterns, and README template.\n- `references\u002Facademic-report-patterns.md`: Vietnamese university report template — 6 chapters, cover page, TOC, figure\u002Ftable lists, formatting standards, citation guide, and common academic phrases.\n- `references\u002Fsentence-quality.md`: sentence patterns that keep meaning complete, compact, and easy to read.\n- `references\u002Ftone-reliability.md`: humility, evidence wording, uncertainty, and confidence calibration.\n- `references\u002Fvietnamese-style.md`: Vietnamese document labels, wording patterns, and anti-filler rules.\n- `references\u002Fformatting.md`: professional headings, tables, bullets, spacing, and scan-friendly layout rules.\n","## TL;DR\nLoad before writing or revising any document, report, proposal, memo, guide, academic paper, or long-form explanation. The goal is reader clarity: correct context, full meaning, professional structure, reliable tone, compact wording, proper diagrams, and polished formatting — without making the reader infer missing intent.\n\n## Activation\n\n1. Activate when the task involves drafting, rewriting, summarizing, formatting, or improving documents, reports, memos, proposals, guides, handoffs, emails, academic papers, or formal text.\n2. Activate on `$doc`, `$report`, `$write`, `$diagram`, `$báo-cáo`, \"soạn tài liệu\", \"viết báo cáo\", \"làm văn bản chuyên nghiệp\", \"viết rõ ràng hơn\", \"vẽ sơ đồ\".\n3. Auto-load with `codex-reasoning-rigor` when the document is decision-heavy, high-stakes, or evidence-based.\n4. Auto-load with `codex-doc-renderer` when the deliverable is `.docx`.\n\n## Hard Rules\n\n- Always identify purpose, audience, context, and expected use before choosing wording.\n- Start with the document outcome, not background narration.\n- Use complete sentences with explicit actor, action, object, and outcome.\n- Keep each paragraph focused on one message; do not make the reader infer the point.\n- Be detailed where meaning depends on detail, but remove filler, repeated framing, and synonym stacking.\n- Use humble, reliable wording: state what is verified, what is inferred, and what remains uncertain.\n- Do not overclaim. Avoid \"clearly\", \"obviously\", \"guaranteed\", \"always\", and \"never\" unless evidence supports them.\n- For Vietnamese, use natural UTF-8 Vietnamese, correct context labels, and professional but readable wording.\n- Every diagram must answer a specific question. No decorative diagrams.\n- Every report section must earn its place. No empty sections or placeholder text.\n\n## Document Flow\n\nBefore drafting:\n\n1. Determine document type and reader.\n2. Pick the matching structure:\n   - For reports → `references\u002Freport-structures.md`\n   - For general documents → `references\u002Fdocument-types.md`\n   - For academic\u002Funiversity work → `references\u002Facademic-report-patterns.md`\n3. Add diagrams where visual explanation is needed → `references\u002Fdiagram-patterns.md`\n4. Apply content writing patterns → `references\u002Fcontent-writing-patterns.md`\n5. Apply sentence rules from `references\u002Fsentence-quality.md`.\n6. Apply reliability rules from `references\u002Ftone-reliability.md`.\n7. Apply Vietnamese wording rules from `references\u002Fvietnamese-style.md` when writing Vietnamese.\n8. Apply formatting rules from `references\u002Fformatting.md`.\n\n## Diagram Integration Protocol\n\nWhen the document needs visual explanation:\n\n1. Check `references\u002Fdiagram-patterns.md` → Diagram Selection Decision Table\n2. Choose the simplest diagram type that answers the reader's question\n3. Use Mermaid syntax for rendered documents, ASCII for plain text\n4. Add a caption\u002Ftitle before every diagram\n5. Limit: max 15 nodes per diagram, split if larger\n6. Verify render before delivering\n\n### Quick Diagram Dispatch\n\n| Need | Diagram Type | Mermaid Keyword |\n|---|---|---|\n| System architecture | Flowchart with subgraphs | `flowchart TB` |\n| API interaction flow | Sequence diagram | `sequenceDiagram` |\n| Database schema | ER diagram | `erDiagram` |\n| Status\u002Fworkflow transitions | State diagram | `stateDiagram-v2` |\n| Project timeline | Gantt chart | `gantt` |\n| Branch strategy | Git graph | `gitGraph` |\n| Feature breakdown | Mind map | `mindmap` |\n| Distribution\u002Fproportion | Pie chart | `pie` |\n| Milestone overview | Timeline | `timeline` |\n\n## Report Type Router\n\n| Signal in User Request | Load Reference |\n|---|---|\n| \"báo cáo tiến độ\", \"progress report\" | `references\u002Freport-structures.md` → Progress Report |\n| \"phân tích\", \"analysis\", \"analytical\" | `references\u002Freport-structures.md` → Analytical Report |\n| \"đề xuất\", \"proposal\" | `references\u002Freport-structures.md` → Proposal |\n| \"sprint report\", \"release notes\" | `references\u002Freport-structures.md` → Sprint Report |\n| \"incident\", \"postmortem\", \"sự cố\" | `references\u002Freport-structures.md` → Incident Report |\n| \"đồ án\", \"assignment\", \"bài tập lớn\", \"luận văn\" | `references\u002Facademic-report-patterns.md` |\n| \"memo\", \"update\", \"thông báo\" | `references\u002Fdocument-types.md` → Business Memo |\n| \"hướng dẫn\", \"guide\", \"tutorial\" | `references\u002Fdocument-types.md` → User Guide |\n| \"handoff\", \"bàn giao\" | `references\u002Fdocument-types.md` → Session Handoff |\n| \"README\", \"documentation\" | `references\u002Fcontent-writing-patterns.md` → README Template |\n\n## Quality Gate (Before Delivery)\n\nBefore delivering any document:\n\n- [ ] First section answers the reader's primary question\n- [ ] Every claim backed by evidence\n- [ ] Tables used for comparisons, not narratives\n- [ ] Every diagram has a caption and answers a specific question\n- [ ] Metrics shown with target vs actual\n- [ ] Clear \"Next Steps\" or \"Required Decision\" section\n- [ ] Risks listed with severity AND mitigation\n- [ ] For Vietnamese: proper section headings and figure\u002Ftable numbering\n- [ ] Scannable: headings + tables alone convey the gist\n- [ ] No wall-of-text paragraphs (max 5-6 lines per paragraph)\n- [ ] No \"empty calories\" phrases (\"it is important to note that...\", \"in order to...\")\n\n## Reference Files\n\n- `references\u002Fdocument-types.md`: templates for reports, memos, proposals, guides, handoffs, summaries, and executive updates.\n- `references\u002Freport-structures.md`: 8 report types — progress, analytical, proposal, comparison, sprint, incident, research, and Vietnamese academic.\n- `references\u002Fdiagram-patterns.md`: complete Mermaid diagram reference — flowchart, sequence, ER, state, Gantt, C4, journey, mindmap, pie, gitGraph, timeline + ASCII alternatives + quality rules.\n- `references\u002Fcontent-writing-patterns.md`: PREP framework, heading hierarchy, active voice, \"So What?\" test, Vietnamese content patterns, anti-patterns, and README template.\n- `references\u002Facademic-report-patterns.md`: Vietnamese university report template — 6 chapters, cover page, TOC, figure\u002Ftable lists, formatting standards, citation guide, and common academic phrases.\n- `references\u002Fsentence-quality.md`: sentence patterns that keep meaning complete, compact, and easy to read.\n- `references\u002Ftone-reliability.md`: humility, evidence wording, uncertainty, and confidence calibration.\n- `references\u002Fvietnamese-style.md`: Vietnamese document labels, wording patterns, and anti-filler rules.\n- `references\u002Fformatting.md`: professional headings, tables, bullets, spacing, and scan-friendly layout rules.\n",{"name":5,"description":7,"load_priority":23},"on-demand","main","19b976c6b4f182f06d2d2e6b030549f2f8a69cc0","packages\u002Fcli\u002Fskills\u002Fcodex-document-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-document-writer",{"tool":38,"command":39},"bunx","bunx skills add Bang-isme\u002FAgencyCLI --skill codex-document-writer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Bang-isme\u002FAgencyCLI --skill codex-document-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Facademic-report-patterns.md","REFERENCE","参考文档",8708,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Facademic-report-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcontent-writing-patterns.md",6751,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fcontent-writing-patterns.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdiagram-patterns.md",9768,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fdiagram-patterns.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdocument-types.md",3212,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fdocument-types.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fformatting.md",1584,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fformatting.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Freport-structures.md",8348,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Freport-structures.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fsentence-quality.md",2261,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fsentence-quality.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ftone-reliability.md",2011,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Ftone-reliability.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fvietnamese-style.md",2803,"https:\u002F\u002Fgithub.com\u002FBang-isme\u002FAgencyCLI\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcodex-document-writer\u002Freferences\u002Fvietnamese-style.md",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M754T1HG4JRTJVZC2PBFTXDT","codex-plan-writer","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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]