[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72Y40X98TXPASM6HTNPYSYR":3,"skill-same:01M72Y40X98TXPASM6HTNPYSYR":83},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M72Y40X98TXPASM6HTNPYSYR","writing",null,"Write, review, or clean up prose that engineers and agents read. Use for docs, a README, an RFC, an ADR, a guide, commit messages, PR descriptions, a SKILL.md, AGENTS.md or CLAUDE.md, or to unslop, de-AI, or line-edit supplied text. Skip product and marketing copy (copy), verify and driver skills (verification), and media prompts (prompt).","h00mankind\u002Fworkflow","h00mankind","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F105175148?v=4","01M72XXA2JP2H3BBK5GP9AP4P6","h00man","01M72XXA3824K52XFYWJDBFJ06",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: writing\ndescription: Write, review, or clean up prose that engineers and agents read. Use for docs, a README, an RFC, an ADR, a guide, commit messages, PR descriptions, a SKILL.md, AGENTS.md or CLAUDE.md, or to unslop, de-AI, or line-edit supplied text. Skip product and marketing copy (copy), verify and driver skills (verification), and media prompts (prompt).\n---\n\n# Writing\n\nWrite so the reader understands on the first read. Pick the job first, read the reference for that job, then run one cleanup pass.\n\n## Scope\n\n- Docs, READMEs, RFCs, ADRs, guides, and reference pages.\n- Commit messages and PR descriptions. The `ship` skill commits and opens the PR. This skill writes the text.\n- Documents an agent reads: a skill, `AGENTS.md`, `CLAUDE.md`, or a doc behind a pointer.\n- Cleanup of prose that the user supplies.\n\nSend other work away:\n\n- Landing pages, headlines, UI labels, errors, and empty states go to the `copy` skill.\n- A one-off prompt for another agent or a later run goes to the `\u002Fambitious` command.\n- Image, video, and audio prompts go to the `prompt` skill.\n\n## Order of work\n\n1. **Find the terms.** Read the repo's `CONTEXT.md` or glossary if it has one. Use its terms for each concept. Do not invent a synonym.\n2. **Pick the job.** Use the table in the next section. Read the reference that the job names before you write.\n3. **Write the draft.** Use the real file, flag, command, and symbol names from the code.\n4. **Clean it.** Run the cleanup pass for the job (see \"Cleanup\").\n5. **Check it.** Make each count, path, and command in the text true at the commit that ships it. Run the command if you can.\n\n## Jobs and references\n\n**Human docs (README, RFC, ADR, guide, reference).** Read `references\u002Fpstack-technical-writing.md` in full. Take the mode choice (tutorial, how-to, reference, explanation), the sentence rules, and the rules against two readings. Pick one mode per document.\n\n- Save an ADR in `docs\u002Fadr\u002F` as one Markdown file. Record the choice, the context, and the options you rejected.\n- Save a plan or PRD through the `\u002Fplan` command, not this skill.\n\n**Commit messages and PR descriptions.** Read the \"Voice and repo specifics\" part of `references\u002Fpstack-technical-writing.md`. Write the PR body as a short briefing. Open it with the goal of the change. Link long logs and do not paste them.\n\n**Agent-facing docs (skills, AGENTS.md, CLAUDE.md).** Read `references\u002Fwriting-for-agents\u002FSKILL.ref.md`. Take its terms: context pointer, the two loads, the information hierarchy, completion criteria, leading words, and pruning. For a skill, also read `references\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md` for the frontmatter and the choice between model and user invocation.\n\n- Front-load the trigger words a user types in the `description`.\n- Keep each rule in one place. Point to a reference file and do not copy it.\n- Write in the second person, imperative mood, and active voice.\n\n**Cleanup of supplied prose.** Read `references\u002Funslop\u002FSKILL.ref.md` for its contract. Keep the author's facts, claims, and certainty. Return the edited text first.\n\n## Cleanup\n\n`references\u002Fpstack-unslop.md` is the one pattern catalog for all text. Its rule numbers are stable, so cite a rule by number in a review or when you explain an edit.\n\n- **Text you write** (docs, commits, PRs, agent docs, replies): apply every rule.\n- **Text the user wrote**: apply every rule too, an em dash included. The contract in `references\u002Funslop\u002FSKILL.ref.md` limits the edit. Change no fact, claim, or level of certainty, and keep the source's formality and point of view. Use the pattern list in that file only for a pattern that the catalog does not name.\n\nRemove AI patterns as you draft, because a later pass misses some.\n\n## Upstream names in the references\n\nThe references name skills that this plugin does not install. Use these files in their place:\n\n- \"the **unslop** skill\" or \"`unslop`\" in `references\u002Fpstack-technical-writing.md` means `references\u002Fpstack-unslop.md`. Its \"abstract-metaphor rule\" is rule 26 there. Propose a new word for rule 26 in your reply. Do not edit the file.\n- \"`writing-for-agents`\" and \"`SKILL.md`\" in `references\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md` mean `references\u002Fwriting-for-agents\u002FSKILL.ref.md`.\n- `\u002Ftechnical-writing` means this skill.\n- \"your product's copy guidelines\" means the `copy` skill.\n\n## Done\n\n- The document has one mode, and each heading states its point.\n- Each term matches the repo glossary.\n- No pattern from `references\u002Fpstack-unslop.md` remains.\n- Each path, count, and command is true.\n\nEach upstream `SKILL.md` in `references\u002F` is named `SKILL.ref.md`, so that no harness loads it as a skill. When a reference links to a `SKILL.md`, read the `SKILL.ref.md` in that folder.\n\n## Sources\n\n- **pstack** by Lauren Tan (poteto), Claude Code port at https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fpstack, MIT. Takes `technical-writing` (the four layers for docs, commits, and PRs) and `unslop` (the numbered catalog of AI patterns for all text).\n- **matt** by Matt Pocock, https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills, MIT. Takes `writing-for-agents` (context pointers, the two loads, the information hierarchy, and skill mechanics).\n- **h00man:unslop** by the user, https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow, MIT, derived from Lauren Tan's unslop. Takes the line-edit contract for supplied prose, which protects the author's facts and certainty.\n","# Writing\n\nWrite so the reader understands on the first read. Pick the job first, read the reference for that job, then run one cleanup pass.\n\n## Scope\n\n- Docs, READMEs, RFCs, ADRs, guides, and reference pages.\n- Commit messages and PR descriptions. The `ship` skill commits and opens the PR. This skill writes the text.\n- Documents an agent reads: a skill, `AGENTS.md`, `CLAUDE.md`, or a doc behind a pointer.\n- Cleanup of prose that the user supplies.\n\nSend other work away:\n\n- Landing pages, headlines, UI labels, errors, and empty states go to the `copy` skill.\n- A one-off prompt for another agent or a later run goes to the `\u002Fambitious` command.\n- Image, video, and audio prompts go to the `prompt` skill.\n\n## Order of work\n\n1. **Find the terms.** Read the repo's `CONTEXT.md` or glossary if it has one. Use its terms for each concept. Do not invent a synonym.\n2. **Pick the job.** Use the table in the next section. Read the reference that the job names before you write.\n3. **Write the draft.** Use the real file, flag, command, and symbol names from the code.\n4. **Clean it.** Run the cleanup pass for the job (see \"Cleanup\").\n5. **Check it.** Make each count, path, and command in the text true at the commit that ships it. Run the command if you can.\n\n## Jobs and references\n\n**Human docs (README, RFC, ADR, guide, reference).** Read `references\u002Fpstack-technical-writing.md` in full. Take the mode choice (tutorial, how-to, reference, explanation), the sentence rules, and the rules against two readings. Pick one mode per document.\n\n- Save an ADR in `docs\u002Fadr\u002F` as one Markdown file. Record the choice, the context, and the options you rejected.\n- Save a plan or PRD through the `\u002Fplan` command, not this skill.\n\n**Commit messages and PR descriptions.** Read the \"Voice and repo specifics\" part of `references\u002Fpstack-technical-writing.md`. Write the PR body as a short briefing. Open it with the goal of the change. Link long logs and do not paste them.\n\n**Agent-facing docs (skills, AGENTS.md, CLAUDE.md).** Read `references\u002Fwriting-for-agents\u002FSKILL.ref.md`. Take its terms: context pointer, the two loads, the information hierarchy, completion criteria, leading words, and pruning. For a skill, also read `references\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md` for the frontmatter and the choice between model and user invocation.\n\n- Front-load the trigger words a user types in the `description`.\n- Keep each rule in one place. Point to a reference file and do not copy it.\n- Write in the second person, imperative mood, and active voice.\n\n**Cleanup of supplied prose.** Read `references\u002Funslop\u002FSKILL.ref.md` for its contract. Keep the author's facts, claims, and certainty. Return the edited text first.\n\n## Cleanup\n\n`references\u002Fpstack-unslop.md` is the one pattern catalog for all text. Its rule numbers are stable, so cite a rule by number in a review or when you explain an edit.\n\n- **Text you write** (docs, commits, PRs, agent docs, replies): apply every rule.\n- **Text the user wrote**: apply every rule too, an em dash included. The contract in `references\u002Funslop\u002FSKILL.ref.md` limits the edit. Change no fact, claim, or level of certainty, and keep the source's formality and point of view. Use the pattern list in that file only for a pattern that the catalog does not name.\n\nRemove AI patterns as you draft, because a later pass misses some.\n\n## Upstream names in the references\n\nThe references name skills that this plugin does not install. Use these files in their place:\n\n- \"the **unslop** skill\" or \"`unslop`\" in `references\u002Fpstack-technical-writing.md` means `references\u002Fpstack-unslop.md`. Its \"abstract-metaphor rule\" is rule 26 there. Propose a new word for rule 26 in your reply. Do not edit the file.\n- \"`writing-for-agents`\" and \"`SKILL.md`\" in `references\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md` mean `references\u002Fwriting-for-agents\u002FSKILL.ref.md`.\n- `\u002Ftechnical-writing` means this skill.\n- \"your product's copy guidelines\" means the `copy` skill.\n\n## Done\n\n- The document has one mode, and each heading states its point.\n- Each term matches the repo glossary.\n- No pattern from `references\u002Fpstack-unslop.md` remains.\n- Each path, count, and command is true.\n\nEach upstream `SKILL.md` in `references\u002F` is named `SKILL.ref.md`, so that no harness loads it as a skill. When a reference links to a `SKILL.md`, read the `SKILL.ref.md` in that folder.\n\n## Sources\n\n- **pstack** by Lauren Tan (poteto), Claude Code port at https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fpstack, MIT. Takes `technical-writing` (the four layers for docs, commits, and PRs) and `unslop` (the numbered catalog of AI patterns for all text).\n- **matt** by Matt Pocock, https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills, MIT. Takes `writing-for-agents` (context pointers, the two loads, the information hierarchy, and skill mechanics).\n- **h00man:unslop** by the user, https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow, MIT, derived from Lauren Tan's unslop. Takes the line-edit contract for supplied prose, which protects the author's facts and certainty.\n",{"name":5,"description":7},"main","2b813251957e3e80c45cc5f55bf9c228d818d05b","plugins\u002Fh00man\u002Fskills\u002Fwriting","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow","https:\u002F\u002Fgithub.com\u002Fh00mankind","an ordinary mortal h00man","2026-11-13 01:29:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add h00mankind\u002Fworkflow --skill writing",{"tool":37,"command":38},"bunx","bunx skills add h00mankind\u002Fworkflow --skill writing",{"tool":40,"command":41},"pnpm","pnpm dlx skills add h00mankind\u002Fworkflow --skill writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002FSKILL.md",true,[45,51,57,61,67,71,75,79],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"includes.toml","OTHER","其他",503,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Fincludes.toml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fpstack-technical-writing.md","REFERENCE","参考文档",9062,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Fpstack-technical-writing.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fpstack-unslop.md",5796,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Fpstack-unslop.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Funslop\u002FLICENSE","LICENSE","许可证",1067,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Funslop\u002FLICENSE",{"path":68,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Funslop\u002FSKILL.ref.md",4995,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Funslop\u002FSKILL.ref.md",{"path":72,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fwriting-for-agents\u002Fagents\u002Fopenai.yaml",102,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Fwriting-for-agents\u002Fagents\u002Fopenai.yaml",{"path":76,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md",2629,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md",{"path":80,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fwriting-for-agents\u002FSKILL.ref.md",10886,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fwriting\u002Freferences\u002Fwriting-for-agents\u002FSKILL.ref.md",[84,92,99,107,114,121],{"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":91},"01M78R7TT830V3BYFNDX1EHF0V","teach","Teach the user a subject, in explain mode (one plain account of code, a change, or a concept, in chat) or course mode (a learning workspace with a mission, lessons, and records over many sessions). Runs only when the user types \u002Fteach.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fteach\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":91},"01M78R7RSGFF5TFE0JBGY3WKEJ","council","Get a review or a second opinion on existing work from several strong models of different providers. Runs only when the user types \u002Fcouncil.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fcouncil\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":106},"01M74AAVCZZREXPZEE5HRN5WF5","variant","Builds multiple variants of a component you're working on and helps you iterate and pick one.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fvariant\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":106},"01M74AAR3M07M86YX2CXPD79EX","teardown","Creates technical illustrations of physical objects and of how things work, such as display pixels or interface layers, with coherent views, fine linework and part fills.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fteardown\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":106},"01M74AAMKJ8MKP9M99K37A82ZM","state-machine","Renders every state of a component you choose on a throwaway page, with mock data and a switcher, so you can work on each state.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fstate-machine\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":106},"01M74AAHF2A498F7F2E74696KF","interface-review","Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color and UI.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Finterface-review\u002FSKILL.md",[],[]]