[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M759VSS6V73Y3AAXPFFXDXS9":3,"skill-same:01M759VSS6V73Y3AAXPFFXDXS9":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M759VSS6V73Y3AAXPFFXDXS9","paper-writer",null,"Gated agentic paper-writing workflow — outline-first, section-by-section, content-provenance. Use when the user asks to write, format, or edit sections of a research paper.","harmoniqs\u002Famicode","harmoniqs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F199011497?v=4","01M759PQCJ9Y093EC5HC3344DW","Harmoniqs","01M759PQD5S85W68FZKV3XD1X0",7,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Fskills\u002Fpaper-writer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: paper-writer\ndescription: Gated agentic paper-writing workflow — outline-first, section-by-section, content-provenance. Use when the user asks to write, format, or edit sections of a research paper.\nagents: []\nsurface: public\n---\n\n# Paper Writer\n\nA gated workflow for formatting research papers from a user-authored outline.\nThe researcher owns the intellectual content; the agent is a typesetter, not a\nco-author.\n\n## Gate model\n\nThis skill enforces two classes of gate:\n\n- **Hard gates** — code-enforced by checking files and frontmatter before\n  acting. The agent reads `paper\u002Foutline.md`, inspects its YAML frontmatter,\n  and refuses to proceed if the gate conditions are not met. These are\n  deterministic.\n- **Soft gates** — LLM instructions that guide behavior probabilistically.\n  They work as well as the model's instruction-following allows. This skill\n  is honest about the distinction.\n\n## Hard gates\n\n### 1. Outline-first gate\n\n**Before writing any content in `paper\u002Fmain.tex`**, check that\n`paper\u002Foutline.md` exists AND its YAML frontmatter has `status: final` (not\n`draft`).\n\nIf the outline is missing or still `status: draft`, **refuse** with:\n\n> \"I need a finalized outline before writing the paper. Your outline is\n> currently [missing \u002F draft]. Please review `paper\u002Foutline.md`, mark each\n> section as ready, and set `status: final` in the frontmatter.\"\n\nThe user controls when the outline is final. The agent never changes the\noutline's `status` field.\n\n### 2. Section-by-section approval\n\nFormat **one section at a time** in this order:\n\n1. Read the section's outline bullets from `paper\u002Foutline.md`\n2. Expand the bullets into LaTeX prose in `paper\u002Fmain.tex`\n3. Present the formatted section to the user for review\n4. Wait for explicit approval before proceeding to the next section\n\nAfter user approval, add the section name to the `sections_approved[]` array\nin `paper\u002Foutline.md` frontmatter. Never format a section already in the\napproved list unless the user explicitly asks for a revision.\n\n### 3. Abstract prohibition\n\nThe abstract is **always** user-authored. Never generate an abstract. If the\nuser asks the agent to write the abstract, respond:\n\n> \"The abstract is your synthesis of the work — I can proofread or format it,\n> but I shouldn't write it. Draft your abstract in the outline and I'll\n> typeset it.\"\n\n## Soft gates (LLM instructions)\n\nThese are behavioral rules, not code-enforceable constraints. They guide the\nagent's output quality but are probabilistic.\n\n### Content provenance\n\nEvery paragraph in `paper\u002Fmain.tex` must trace back to a specific bullet in\n`paper\u002Foutline.md`. When expanding a bullet into prose, cite the outline\nbullet in a LaTeX comment:\n\n```latex\n% outline: Results > bullet 3\nThe optimized pulse achieves $F = 0.9995$ in 42~ns...\n```\n\n### Forbidden actions\n\nThe agent MUST NOT:\n\n1. **Generate novel conclusions** — only format what the outline says\n2. **Interpret results** — report numbers; do not explain their significance\n   beyond what the outline states\n3. **Generate the abstract** — always user-authored (hard gate above)\n4. **Select emphasis** — do not add \"importantly,\" \"notably,\" \"remarkably\" or\n   similar editorial emphasis not present in the outline\n5. **Invent methodology details** — only include methods described in the\n   outline or referenced in `scripts\u002Fexperiment\u002F` (optimization solves) and\n   `scripts\u002Ftestbed\u002F` (system environment)\n6. **Hallucinate citations** — only cite references that exist in\n   `paper\u002Freferences.bib`\n\n### Data grounding\n\nQuantitative claims (fidelities, gate times, error rates, etc.) must cite\ntheir source file in `data\u002F`. When expanding an outline bullet that contains a\nnumber, verify the number appears in a referenced data file. If the number\ncannot be traced to `data\u002F`, flag it:\n\n```latex\n% WARNING: F = 0.9995 not found in data\u002F — verify before submission\n```\n\n## Capabilities\n\nThe paper-writer skill supports seven operations:\n\n1. **Sentence expansion from outline** — expand outline bullets into\n   well-formed LaTeX paragraphs, one section at a time\n2. **Data citation with inline results** — embed quantitative results from\n   `data\u002F` files inline, with provenance comments\n3. **Figure placement and captioning** — insert `\\includegraphics` for files\n   in `paper\u002Ffigures\u002F`, draft captions from outline descriptions\n4. **Bibliography management** — add BibTeX entries to `paper\u002Freferences.bib`,\n   insert `\\cite{}` references where the outline indicates citations\n5. **Outline gap detection** — identify outline sections that are too thin to\n   expand into a full section and suggest what's missing\n6. **Proofreading** — fix grammar, punctuation, and LaTeX formatting in\n   already-approved sections (does not change technical content)\n7. **Equation formatting** — convert inline math descriptions in the outline\n   to properly formatted LaTeX equations\n\n## Venue-aware outline templates\n\nWhen scaffolding `paper\u002Foutline.md` for a new project, use the template\nmatching the project's venue. These templates define the section structure the\npaper-writer expects.\n\n### PRL (Physical Review Letters) — compressed format\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline (PRL compressed format)\n\n### Abstract\n- [ ] [User-authored summary — max 600 words]\n\n### Introduction\n- [ ] Context and motivation (1-2 paragraphs)\n- [ ] State of the art and gap\n- [ ] Our contribution (one sentence)\n\n### Results\n- [ ] Main result with key figure\n- [ ] Supporting measurements\n- [ ] Comparison with prior work\n\n### Discussion\n- [ ] Interpretation of results\n- [ ] Limitations\n- [ ] Outlook\n\n### Methods\n- [ ] Experimental\u002Fcomputational setup\n- [ ] Key parameters and their justification\n\n### Supplementary\n- [ ] Extended data tables\n- [ ] Additional figures\n- [ ] Detailed derivations\n```\n\n### PRX Quantum — full format\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline (PRX Quantum full format)\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] Broad context (1 paragraph)\n- [ ] Specific problem and prior work (2-3 paragraphs)\n- [ ] Gap in existing approaches\n- [ ] Our approach and key results (1 paragraph)\n- [ ] Paper organization\n\n### Background\n- [ ] Notation and conventions\n- [ ] Review of relevant theory\n- [ ] System model\n\n### Methods\n- [ ] Problem formulation\n- [ ] Optimization approach\n- [ ] Computational details\n\n### Results\n- [ ] Main result\n- [ ] Systematic study \u002F parameter sweep\n- [ ] Robustness analysis\n- [ ] Comparison with baselines\n\n### Discussion\n- [ ] Interpretation\n- [ ] Connections to related work\n- [ ] Limitations and assumptions\n- [ ] Future directions\n\n### Conclusion\n- [ ] Summary of contributions\n- [ ] Open questions\n\n### Acknowledgments\n- [ ] Funding, collaborators\n```\n\n### arXiv general\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] Motivation and context\n- [ ] Prior work\n- [ ] Our contribution\n\n### Methods\n- [ ] Approach description\n- [ ] Implementation details\n\n### Results\n- [ ] Key findings\n- [ ] Supporting evidence\n\n### Discussion\n- [ ] Implications\n- [ ] Limitations\n\n### Conclusion\n- [ ] Summary and outlook\n```\n\n### Minimal (no venue)\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] TODO\n\n### Methods\n- [ ] TODO\n\n### Results\n- [ ] TODO\n\n### Discussion\n- [ ] TODO\n\n### Conclusion\n- [ ] TODO\n```\n\n## Overriding per-project\n\nA Research Project can override this skill by placing a custom\n`skills\u002Fpaper-writer\u002FSKILL.md` in its project directory. The project version\nshadows the shipped version (project > custom > workspace > shipped in the\nskill merge chain). This lets a team enforce lab-specific writing conventions\nor venue requirements.\n","# Paper Writer\n\nA gated workflow for formatting research papers from a user-authored outline.\nThe researcher owns the intellectual content; the agent is a typesetter, not a\nco-author.\n\n## Gate model\n\nThis skill enforces two classes of gate:\n\n- **Hard gates** — code-enforced by checking files and frontmatter before\n  acting. The agent reads `paper\u002Foutline.md`, inspects its YAML frontmatter,\n  and refuses to proceed if the gate conditions are not met. These are\n  deterministic.\n- **Soft gates** — LLM instructions that guide behavior probabilistically.\n  They work as well as the model's instruction-following allows. This skill\n  is honest about the distinction.\n\n## Hard gates\n\n### 1. Outline-first gate\n\n**Before writing any content in `paper\u002Fmain.tex`**, check that\n`paper\u002Foutline.md` exists AND its YAML frontmatter has `status: final` (not\n`draft`).\n\nIf the outline is missing or still `status: draft`, **refuse** with:\n\n> \"I need a finalized outline before writing the paper. Your outline is\n> currently [missing \u002F draft]. Please review `paper\u002Foutline.md`, mark each\n> section as ready, and set `status: final` in the frontmatter.\"\n\nThe user controls when the outline is final. The agent never changes the\noutline's `status` field.\n\n### 2. Section-by-section approval\n\nFormat **one section at a time** in this order:\n\n1. Read the section's outline bullets from `paper\u002Foutline.md`\n2. Expand the bullets into LaTeX prose in `paper\u002Fmain.tex`\n3. Present the formatted section to the user for review\n4. Wait for explicit approval before proceeding to the next section\n\nAfter user approval, add the section name to the `sections_approved[]` array\nin `paper\u002Foutline.md` frontmatter. Never format a section already in the\napproved list unless the user explicitly asks for a revision.\n\n### 3. Abstract prohibition\n\nThe abstract is **always** user-authored. Never generate an abstract. If the\nuser asks the agent to write the abstract, respond:\n\n> \"The abstract is your synthesis of the work — I can proofread or format it,\n> but I shouldn't write it. Draft your abstract in the outline and I'll\n> typeset it.\"\n\n## Soft gates (LLM instructions)\n\nThese are behavioral rules, not code-enforceable constraints. They guide the\nagent's output quality but are probabilistic.\n\n### Content provenance\n\nEvery paragraph in `paper\u002Fmain.tex` must trace back to a specific bullet in\n`paper\u002Foutline.md`. When expanding a bullet into prose, cite the outline\nbullet in a LaTeX comment:\n\n```latex\n% outline: Results > bullet 3\nThe optimized pulse achieves $F = 0.9995$ in 42~ns...\n```\n\n### Forbidden actions\n\nThe agent MUST NOT:\n\n1. **Generate novel conclusions** — only format what the outline says\n2. **Interpret results** — report numbers; do not explain their significance\n   beyond what the outline states\n3. **Generate the abstract** — always user-authored (hard gate above)\n4. **Select emphasis** — do not add \"importantly,\" \"notably,\" \"remarkably\" or\n   similar editorial emphasis not present in the outline\n5. **Invent methodology details** — only include methods described in the\n   outline or referenced in `scripts\u002Fexperiment\u002F` (optimization solves) and\n   `scripts\u002Ftestbed\u002F` (system environment)\n6. **Hallucinate citations** — only cite references that exist in\n   `paper\u002Freferences.bib`\n\n### Data grounding\n\nQuantitative claims (fidelities, gate times, error rates, etc.) must cite\ntheir source file in `data\u002F`. When expanding an outline bullet that contains a\nnumber, verify the number appears in a referenced data file. If the number\ncannot be traced to `data\u002F`, flag it:\n\n```latex\n% WARNING: F = 0.9995 not found in data\u002F — verify before submission\n```\n\n## Capabilities\n\nThe paper-writer skill supports seven operations:\n\n1. **Sentence expansion from outline** — expand outline bullets into\n   well-formed LaTeX paragraphs, one section at a time\n2. **Data citation with inline results** — embed quantitative results from\n   `data\u002F` files inline, with provenance comments\n3. **Figure placement and captioning** — insert `\\includegraphics` for files\n   in `paper\u002Ffigures\u002F`, draft captions from outline descriptions\n4. **Bibliography management** — add BibTeX entries to `paper\u002Freferences.bib`,\n   insert `\\cite{}` references where the outline indicates citations\n5. **Outline gap detection** — identify outline sections that are too thin to\n   expand into a full section and suggest what's missing\n6. **Proofreading** — fix grammar, punctuation, and LaTeX formatting in\n   already-approved sections (does not change technical content)\n7. **Equation formatting** — convert inline math descriptions in the outline\n   to properly formatted LaTeX equations\n\n## Venue-aware outline templates\n\nWhen scaffolding `paper\u002Foutline.md` for a new project, use the template\nmatching the project's venue. These templates define the section structure the\npaper-writer expects.\n\n### PRL (Physical Review Letters) — compressed format\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline (PRL compressed format)\n\n### Abstract\n- [ ] [User-authored summary — max 600 words]\n\n### Introduction\n- [ ] Context and motivation (1-2 paragraphs)\n- [ ] State of the art and gap\n- [ ] Our contribution (one sentence)\n\n### Results\n- [ ] Main result with key figure\n- [ ] Supporting measurements\n- [ ] Comparison with prior work\n\n### Discussion\n- [ ] Interpretation of results\n- [ ] Limitations\n- [ ] Outlook\n\n### Methods\n- [ ] Experimental\u002Fcomputational setup\n- [ ] Key parameters and their justification\n\n### Supplementary\n- [ ] Extended data tables\n- [ ] Additional figures\n- [ ] Detailed derivations\n```\n\n### PRX Quantum — full format\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline (PRX Quantum full format)\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] Broad context (1 paragraph)\n- [ ] Specific problem and prior work (2-3 paragraphs)\n- [ ] Gap in existing approaches\n- [ ] Our approach and key results (1 paragraph)\n- [ ] Paper organization\n\n### Background\n- [ ] Notation and conventions\n- [ ] Review of relevant theory\n- [ ] System model\n\n### Methods\n- [ ] Problem formulation\n- [ ] Optimization approach\n- [ ] Computational details\n\n### Results\n- [ ] Main result\n- [ ] Systematic study \u002F parameter sweep\n- [ ] Robustness analysis\n- [ ] Comparison with baselines\n\n### Discussion\n- [ ] Interpretation\n- [ ] Connections to related work\n- [ ] Limitations and assumptions\n- [ ] Future directions\n\n### Conclusion\n- [ ] Summary of contributions\n- [ ] Open questions\n\n### Acknowledgments\n- [ ] Funding, collaborators\n```\n\n### arXiv general\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] Motivation and context\n- [ ] Prior work\n- [ ] Our contribution\n\n### Methods\n- [ ] Approach description\n- [ ] Implementation details\n\n### Results\n- [ ] Key findings\n- [ ] Supporting evidence\n\n### Discussion\n- [ ] Implications\n- [ ] Limitations\n\n### Conclusion\n- [ ] Summary and outlook\n```\n\n### Minimal (no venue)\n\n```markdown\n---\nstatus: draft\nlast_reviewed:\nsections_approved: []\n---\n\n# [Title]\n\n**Research question:** [question]\n\n## Outline\n\n### Abstract\n- [ ] [User-authored summary]\n\n### Introduction\n- [ ] TODO\n\n### Methods\n- [ ] TODO\n\n### Results\n- [ ] TODO\n\n### Discussion\n- [ ] TODO\n\n### Conclusion\n- [ ] TODO\n```\n\n## Overriding per-project\n\nA Research Project can override this skill by placing a custom\n`skills\u002Fpaper-writer\u002FSKILL.md` in its project directory. The project version\nshadows the shipped version (project > custom > workspace > shipped in the\nskill merge chain). This lets a team enforce lab-specific writing conventions\nor venue requirements.\n",{"name":5,"agents":24,"surface":25,"description":7},[],"public","main","bf84fdd4c1494800695bd5881702b3118dbf98be","packages\u002Fextension\u002Fskills\u002Fpaper-writer",2,"https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode","https:\u002F\u002Fgithub.com\u002Fharmoniqs","harmoniqs.ai","research tools, for researchers, by reseachers","2026-11-12 14:46:24",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add harmoniqs\u002Famicode --skill paper-writer",{"tool":41,"command":42},"bunx","bunx skills add harmoniqs\u002Famicode --skill paper-writer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add harmoniqs\u002Famicode --skill paper-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Fskills\u002Fpaper-writer\u002FSKILL.md",true,[],[50,57,64,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M759XGHEQRJ1GWZTPRFF9Z1W","malformed","Frontmatter that parses as YAML but is missing the required name field.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fmalformed\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M759XDVQ1PYPMT876X8J21TQ","duplicated","Second skill carrying the duplicated frontmatter name.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fdup-two\u002FSKILL.md",[],[],{"skillNo":65,"name":59,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M759XBZYBHF38JDWSRHAC6E1","First skill carrying the duplicated frontmatter name.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fdup-one\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M759XAQBSP29BKTTXR1WF2D7","drifted","A skill whose API claims have drifted from the fixture packages.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fdrifted\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M759X8CNBPVK98C6M45D0QMB","clean","A clean skill whose every extracted claim resolves against the fixture packages.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fclean\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M759X73H6N2G0VDH8CJ5TF11","broken-paths","A skill with a broken relative link and a broken cited package path.","https:\u002F\u002Fgithub.com\u002Fharmoniqs\u002Famicode\u002Fblob\u002Fmain\u002Fpackages\u002Fextension\u002Ftest\u002Ffixtures\u002Fskill-drift\u002Fskills\u002Fbroken-paths\u002FSKILL.md",[],[]]