[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WFZSSS5QAPK10TKP8DRKF":3,"skill-same:01M72WFZSSS5QAPK10TKP8DRKF":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":26,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":40,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M72WFZSSS5QAPK10TKP8DRKF","doc-writer",null,"Writes and updates project documentation for a named reader: ADRs (numbered by a bundled script and checked for shape), READMEs, in-code docstrings that state the contract, and reference docs, preferring text that lives next to the code. Use when asked to write or update a README, an ADR, docstrings or reference docs, when a public contract (CLI flags, API surface, config schema) changed and the docs no longer match, or when an architect recommendation must be recorded as an ADR. Not for PR descriptions, commit messages, inline code comments, implementation plans, specs with requirements and scenarios (spec-author), or design alternatives (architect).","crewrig\u002Fcrewrig","crewrig","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F283580446?v=4","01M72WDBD9H0YW5JBHNZ0TEVWB","01M72WDBEBNRBAS94AXRPEVYNK",24,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: doc-writer\ndescription: \"Writes and updates project documentation for a named reader: ADRs (numbered by a bundled script and checked for shape), READMEs, in-code docstrings that state the contract, and reference docs, preferring text that lives next to the code. Use when asked to write or update a README, an ADR, docstrings or reference docs, when a public contract (CLI flags, API surface, config schema) changed and the docs no longer match, or when an architect recommendation must be recorded as an ADR. Not for PR descriptions, commit messages, inline code comments, implementation plans, specs with requirements and scenarios (spec-author), or design alternatives (architect).\"\nlicense: Apache-2.0\ncompatibility: \"Requires Node.js 24 (scripts run as node scripts\u002F\u003Cname>.ts).\"\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Grep\n  - Glob\n  - Bash\nuser-invocable: true\nmetadata:\n  provenance:\n    canonical: \"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\"\n    feedback: \"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\"\n    version: \"1.2.0\"\n---\n\n\n# Documentation Writer\n\nWrites documentation that survives the first refactor, for the reader who\nwill actually open it. A document with no named reader goes unread, and a\ndocument that drifts from the code is worse than none.\n\n## When to activate\n\n- The user asks for a README, an ADR, an architecture document or reference\n  material, or for docstrings that state a contract.\n- A change shifts a public contract (CLI flags, API surface, config schema)\n  and the existing docs no longer match.\n- The architect skill produced a recommendation that warrants an ADR.\n- A new module lacks a top-of-file docstring that its role needs.\n\nWhen the user asks for one of these, do not write the file: say why, say where the\ntext belongs (for a recap, the pull request description) and offer to draft it\nthere instead. The cases:\n\n- A recap of what you just did. It belongs in the pull request description,\n  where reviewers look; a standalone recap is read once and then rots.\n- A comment that says *what* the code does. The code already says it.\n- Documentation nobody asked for, written to look thorough.\n\n## Scripts\n\nRun `node \u003Cskill-dir>\u002Fscripts\u002F\u003Cname>.ts` from the repository; add `--json` for a\nmachine-readable result. Each exits `0` (ok), `1` (finding), `2` (usage error) or\n`3` (precondition failed: unreadable directory, template or file).\n\n| When | Command | Exit `1` means |\n|---|---|---|\n| Starting an ADR | `node scripts\u002Fnew-adr.ts --title \"\u003Cthe decision>\"` (`--dir \u003Cpath>` when ADRs are not in `docs\u002Fadr`; `--status Accepted` for an already settled decision; `--dry-run` to preview) | Empty title, a title with no letter or digit, an unknown status, a target that already exists, or no free number. Fix the input and rerun. |\n| After filling an ADR | `node scripts\u002Flint-adr.ts \u003Cfile>` | A rule is broken: heading, section order, status value, a leftover placeholder, a missing consequence bullet. Fix the ADR and rerun until clean. A Context over five sentences is a warning: tighten it or accept it knowingly. |\n\n`new-adr.ts` takes the next number from the files in the local directory, so it\ncannot see a number reserved on another branch or in an open pull request. Check\nthe open pull requests for the same number before keeping it, and renumber if it\nis taken.\n\n`lint-adr.ts` is a tool for the ADR you are writing, not a repository gate: older\nADRs of a project may use other layouts and would fail it, so run it on your own\nfile only.\n\nExit `2` or `3` means the call or the environment is wrong, not the document.\n\n## Operating mode\n\n### 1. Identify the reader\n\nName the reader before writing, and match length and tone to them:\n\n- **Future maintainer**: knows the codebase, needs the *why* and the invariants.\n  Short, dense.\n- **Onboarding contributor**: new to the codebase, needs the *what* and how to\n  run it. Longer, with examples.\n- **External integrator**: has no repository access, needs only the contract.\n  API-doc style.\n- **Reviewer of an architecture decision**: needs context, the decision and its\n  consequences. ADR style.\n\n### 2. ADRs\n\nRun `new-adr.ts`, then fill the four sections it laid out:\n\n- **Context**: what forces this decision now (a constraint, a deadline, an\n  incident, drift), in three to five sentences. If it needs more, the decision\n  is not crisp enough to record.\n- **Decision**: one paragraph, declarative voice.\n- **Consequences**: a positive, a negative and a neutral bullet. Be honest about\n  the negative one: it is what the next reader needs most.\n- **Status**: Proposed, Accepted, Deprecated, or `Superseded by ADR-NNNN`.\n\nTake every fact from what the user told you, the code or the repository. A reason\nyou cannot source is left out, not invented: a record with a made-up rationale\nmisleads the next reader more than a short one.\n\nNumber ADRs in sequence. Never rewrite an accepted ADR: its value is that it\nrecords what was decided and why at the time. To reverse it, write a new ADR that\nnames the one it supersedes, then change only the Status line of the old one, to\n`Superseded by ADR-NNNN`; its body and decision text stay word for word.\nThen run `lint-adr.ts` on the new file.\n\n### 3. READMEs\n\nOrder sections by the reader's priority, and skip those that do not apply:\n\n1. A one-sentence pitch: what the project does, for whom.\n2. Quick start: three commands that produce a visible result.\n3. Install and prerequisites, with exact versions where they matter.\n4. Usage: the two or three most common workflows.\n5. Reference: links to deeper docs, not inline copies.\n6. Contributing: a link to `AGENTS.md` or `CONTRIBUTING.md`.\n7. License: one line.\n\nA README that ends at section 3 because the project needs nothing more is\ncorrect. Take every fact from the project; an invented command or option is\nworse than a gap.\n\n### 4. In-code docstrings\n\nAt the top of a module, one paragraph stating its role and the invariant it\nenforces; skip it when the name already says so. For a function, state the\ncontract: pre-conditions, post-conditions, side effects, error modes. Do not\nrestate parameter types the language encodes, and do not paraphrase the name.\n\n```python\ndef transfer(amount, from_acct, to_acct):\n    \"\"\"Move `amount` from `from_acct` to `to_acct` atomically.\n\n    Raises InsufficientFunds if `from_acct` balance \u003C amount.\n    Side effect: emits a `transfer.completed` event on success.\n    \"\"\"\n```\n\n### 5. Aging well\n\nBefore finishing, ask what in the document will be wrong in six months. Anything\nthat can live next to the code, where it ages with the code, should: a\nstandalone document that drifts silently misleads its readers.\n\n## Output expectations\n\n- Markdown with a proper heading hierarchy, no skipped levels.\n- Prose wrapped near 80 characters; code and tables are not wrapped.\n- Internal links by relative path, external links with the full URL.\n- No emoji in body text unless the project's convention uses them.\n\n## Friction\n\nSee `references\u002Fshared-friction-reporting.md`.\n","# Documentation Writer\n\nWrites documentation that survives the first refactor, for the reader who\nwill actually open it. A document with no named reader goes unread, and a\ndocument that drifts from the code is worse than none.\n\n## When to activate\n\n- The user asks for a README, an ADR, an architecture document or reference\n  material, or for docstrings that state a contract.\n- A change shifts a public contract (CLI flags, API surface, config schema)\n  and the existing docs no longer match.\n- The architect skill produced a recommendation that warrants an ADR.\n- A new module lacks a top-of-file docstring that its role needs.\n\nWhen the user asks for one of these, do not write the file: say why, say where the\ntext belongs (for a recap, the pull request description) and offer to draft it\nthere instead. The cases:\n\n- A recap of what you just did. It belongs in the pull request description,\n  where reviewers look; a standalone recap is read once and then rots.\n- A comment that says *what* the code does. The code already says it.\n- Documentation nobody asked for, written to look thorough.\n\n## Scripts\n\nRun `node \u003Cskill-dir>\u002Fscripts\u002F\u003Cname>.ts` from the repository; add `--json` for a\nmachine-readable result. Each exits `0` (ok), `1` (finding), `2` (usage error) or\n`3` (precondition failed: unreadable directory, template or file).\n\n| When | Command | Exit `1` means |\n|---|---|---|\n| Starting an ADR | `node scripts\u002Fnew-adr.ts --title \"\u003Cthe decision>\"` (`--dir \u003Cpath>` when ADRs are not in `docs\u002Fadr`; `--status Accepted` for an already settled decision; `--dry-run` to preview) | Empty title, a title with no letter or digit, an unknown status, a target that already exists, or no free number. Fix the input and rerun. |\n| After filling an ADR | `node scripts\u002Flint-adr.ts \u003Cfile>` | A rule is broken: heading, section order, status value, a leftover placeholder, a missing consequence bullet. Fix the ADR and rerun until clean. A Context over five sentences is a warning: tighten it or accept it knowingly. |\n\n`new-adr.ts` takes the next number from the files in the local directory, so it\ncannot see a number reserved on another branch or in an open pull request. Check\nthe open pull requests for the same number before keeping it, and renumber if it\nis taken.\n\n`lint-adr.ts` is a tool for the ADR you are writing, not a repository gate: older\nADRs of a project may use other layouts and would fail it, so run it on your own\nfile only.\n\nExit `2` or `3` means the call or the environment is wrong, not the document.\n\n## Operating mode\n\n### 1. Identify the reader\n\nName the reader before writing, and match length and tone to them:\n\n- **Future maintainer**: knows the codebase, needs the *why* and the invariants.\n  Short, dense.\n- **Onboarding contributor**: new to the codebase, needs the *what* and how to\n  run it. Longer, with examples.\n- **External integrator**: has no repository access, needs only the contract.\n  API-doc style.\n- **Reviewer of an architecture decision**: needs context, the decision and its\n  consequences. ADR style.\n\n### 2. ADRs\n\nRun `new-adr.ts`, then fill the four sections it laid out:\n\n- **Context**: what forces this decision now (a constraint, a deadline, an\n  incident, drift), in three to five sentences. If it needs more, the decision\n  is not crisp enough to record.\n- **Decision**: one paragraph, declarative voice.\n- **Consequences**: a positive, a negative and a neutral bullet. Be honest about\n  the negative one: it is what the next reader needs most.\n- **Status**: Proposed, Accepted, Deprecated, or `Superseded by ADR-NNNN`.\n\nTake every fact from what the user told you, the code or the repository. A reason\nyou cannot source is left out, not invented: a record with a made-up rationale\nmisleads the next reader more than a short one.\n\nNumber ADRs in sequence. Never rewrite an accepted ADR: its value is that it\nrecords what was decided and why at the time. To reverse it, write a new ADR that\nnames the one it supersedes, then change only the Status line of the old one, to\n`Superseded by ADR-NNNN`; its body and decision text stay word for word.\nThen run `lint-adr.ts` on the new file.\n\n### 3. READMEs\n\nOrder sections by the reader's priority, and skip those that do not apply:\n\n1. A one-sentence pitch: what the project does, for whom.\n2. Quick start: three commands that produce a visible result.\n3. Install and prerequisites, with exact versions where they matter.\n4. Usage: the two or three most common workflows.\n5. Reference: links to deeper docs, not inline copies.\n6. Contributing: a link to `AGENTS.md` or `CONTRIBUTING.md`.\n7. License: one line.\n\nA README that ends at section 3 because the project needs nothing more is\ncorrect. Take every fact from the project; an invented command or option is\nworse than a gap.\n\n### 4. In-code docstrings\n\nAt the top of a module, one paragraph stating its role and the invariant it\nenforces; skip it when the name already says so. For a function, state the\ncontract: pre-conditions, post-conditions, side effects, error modes. Do not\nrestate parameter types the language encodes, and do not paraphrase the name.\n\n```python\ndef transfer(amount, from_acct, to_acct):\n    \"\"\"Move `amount` from `from_acct` to `to_acct` atomically.\n\n    Raises InsufficientFunds if `from_acct` balance \u003C amount.\n    Side effect: emits a `transfer.completed` event on success.\n    \"\"\"\n```\n\n### 5. Aging well\n\nBefore finishing, ask what in the document will be wrong in six months. Anything\nthat can live next to the code, where it ages with the code, should: a\nstandalone document that drifts silently misleads its readers.\n\n## Output expectations\n\n- Markdown with a proper heading hierarchy, no skipped levels.\n- Prose wrapped near 80 characters; code and tables are not wrapped.\n- Internal links by relative path, external links with the full URL.\n- No emoji in body text unless the project's convention uses them.\n\n## Friction\n\nSee `references\u002Fshared-friction-reporting.md`.\n",{"name":5,"license":14,"metadata":23,"description":7,"allowed-tools":27,"compatibility":34,"user-invocable":35},{"provenance":24},{"version":25,"feedback":26,"canonical":26},"1.2.0","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig",[28,29,30,31,32,33],"Read","Write","Edit","Grep","Glob","Bash","Requires Node.js 24 (scripts run as node scripts\u002F\u003Cname>.ts).",true,"main","6462aef9a402df0abfbb6ca7d7a060839ee8c474",".claude\u002Fskills\u002Fdoc-writer",6,"https:\u002F\u002Fcrewrig.org","https:\u002F\u002Fgithub.com\u002Fcrewrig","This is the organisation behind the crewrig framework","2026-11-15 04:46:08",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add crewrig\u002Fcrewrig --skill doc-writer",{"tool":50,"command":51},"bunx","bunx skills add crewrig\u002Fcrewrig --skill doc-writer",{"tool":53,"command":54},"pnpm","pnpm dlx skills add crewrig\u002Fcrewrig --skill doc-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002FSKILL.md",[57,63,69,75],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fadr.template.md","ASSET","资产文件",462,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002Fassets\u002Fadr.template.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fshared-friction-reporting.md","REFERENCE","参考文档",769,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002Freferences\u002Fshared-friction-reporting.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Flint-adr.ts","SCRIPT","脚本",8034,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002Fscripts\u002Flint-adr.ts",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fnew-adr.ts",6658,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdoc-writer\u002Fscripts\u002Fnew-adr.ts",[80,88,93,98,103,108],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M76AJKRKGGYZFJJHKE32Q5ZZ","fixture","Fixture skill. Mentions scripts\u002Ffrontmatter-only.ts which must be ignored.","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fyaml-example\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":89,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":87},"01M76AJJHS0AHW5HJJQCVVJ4DH","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funterminated\u002FSKILL.md",[],[],{"skillNo":94,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":87},"01M76AJH8VJ2NAE000285J1D8F","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funresolved\u002FSKILL.md",[],[],{"skillNo":99,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":87},"01M76AJG4M862QH00H5QVVT60P","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fstray\u002FSKILL.md",[],[],{"skillNo":104,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":87},"01M76AJEZKZVMWZXCKXCFNQQ6B","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fresolving\u002FSKILL.md",[],[],{"skillNo":109,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":87},"01M76AJD4G4K2YK2SMN8NSEG9R","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Freferences-unfenced\u002FSKILL.md",[],[]]