[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P6DN9P4BQPQAQ618MAT1H":3,"skill-same:01M71P6DN9P4BQPQAQ618MAT1H":74},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":51,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M71P6DN9P4BQPQAQ618MAT1H","technical-writer",null,"Org role guidance for a technical writer: turn engineering concepts into clear developer docs such as READMEs, API references, tutorials and conceptual guides. Covers tested code samples, the Divio doc types, outcome-first framing and consistent voice.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ftechnical-writer\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"technical","technical writer","writer","voice","clear","guidance","https","outcome","github","monomind","first","references","documentation","guides","api","code","writing","for","types","as","2026-11-10 13:02:02",false,"---\nname: technical-writer\ndescription: \"Org role guidance for a technical writer: turn engineering concepts into clear developer docs such as READMEs, API references, tutorials and conceptual guides. Covers tested code samples, the Divio doc types, outcome-first framing and consistent voice.\"\ntags: [\"writing\",\"marketing\",\"documentation\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Technical Writer — Best Practices\n\n## Focus\nTransforms complex engineering concepts into clear, accurate developer documentation — READMEs, API references, tutorials, and conceptual guides that developers actually read and use.\n\n## Best practices\n- Run every code example in a clean environment before shipping it — untested snippets are bugs.\n- Lead with outcomes, not features: \"After this guide, you'll have a working webhook\" beats \"This guide covers webhooks.\"\n- Apply the Divio system: keep tutorials (learning), how-to guides (task), reference (information), and explanation (understanding) as separate document types — never blend them.\n- Write in second person, present tense, active voice, consistently across all docs.\n- Interview the engineer who built the feature before writing: \"What's hard to understand? Where do users get stuck?\"\n- Version documentation alongside software releases; deprecate old docs instead of deleting them.\n- Ship every breaking change with a migration guide before release, not after.\n- One concept per section — never combine installation, configuration, and usage into one wall of text.\n\n## Common pitfalls\n- Assuming reader context instead of stating prerequisites explicitly or linking to them.\n- Writing docs from the API surface instead of the user's task — reference-driven docs that skip the \"why.\"\n- Letting docs drift from the shipped version because they weren't updated in the same PR as the code change.\n- Padding with corporate throat-clearing (\"In this document we will discuss...\") instead of getting to the point.\n\n## Tools & techniques\n- Divio documentation system for information architecture (tutorial\u002Fhow-to\u002Freference\u002Fexplanation).\n- Docs-as-code pipelines (Docusaurus, MkDocs, Sphinx, VitePress) with CI builds that fail on broken links or stale examples.\n- Auto-generate API references from OpenAPI\u002FSwagger, JSDoc, or docstrings rather than hand-maintaining them.\n- The \"5-second test\" for READMEs: what is this, why should I care, how do I start.\n- Docs linting (Vale, markdownlint) enforced in CI for house style.\n","# Technical Writer — Best Practices\n\n## Focus\nTransforms complex engineering concepts into clear, accurate developer documentation — READMEs, API references, tutorials, and conceptual guides that developers actually read and use.\n\n## Best practices\n- Run every code example in a clean environment before shipping it — untested snippets are bugs.\n- Lead with outcomes, not features: \"After this guide, you'll have a working webhook\" beats \"This guide covers webhooks.\"\n- Apply the Divio system: keep tutorials (learning), how-to guides (task), reference (information), and explanation (understanding) as separate document types — never blend them.\n- Write in second person, present tense, active voice, consistently across all docs.\n- Interview the engineer who built the feature before writing: \"What's hard to understand? Where do users get stuck?\"\n- Version documentation alongside software releases; deprecate old docs instead of deleting them.\n- Ship every breaking change with a migration guide before release, not after.\n- One concept per section — never combine installation, configuration, and usage into one wall of text.\n\n## Common pitfalls\n- Assuming reader context instead of stating prerequisites explicitly or linking to them.\n- Writing docs from the API surface instead of the user's task — reference-driven docs that skip the \"why.\"\n- Letting docs drift from the shipped version because they weren't updated in the same PR as the code change.\n- Padding with corporate throat-clearing (\"In this document we will discuss...\") instead of getting to the point.\n\n## Tools & techniques\n- Divio documentation system for information architecture (tutorial\u002Fhow-to\u002Freference\u002Fexplanation).\n- Docs-as-code pipelines (Docusaurus, MkDocs, Sphinx, VitePress) with CI builds that fail on broken links or stale examples.\n- Auto-generate API references from OpenAPI\u002FSwagger, JSDoc, or docstrings rather than hand-maintaining them.\n- The \"5-second test\" for READMEs: what is this, why should I care, how do I start.\n- Docs linting (Vale, markdownlint) enforced in CI for house style.\n",{"name":5,"tags":48,"tools":50,"source":51,"license":14,"description":7},[39,49,35],"marketing",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ftechnical-writer",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add monoes\u002Fmonomind --skill technical-writer",{"tool":66,"command":67},"bunx","bunx skills add monoes\u002Fmonomind --skill technical-writer",{"tool":69,"command":70},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill technical-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ftechnical-writer\u002FSKILL.md",true,[],[75,101,134,161,183,210],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":43},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,91,92,93,32,94,95,96,97,98,99,100],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":117,"publishedAt":43},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[109,114],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[39,118,119,86,120,121,122,123,91,38,124,125,126,127,128,129,130,131,132,133],"writing plans","plans","superpowers","implementation plan","when","you","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":43},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[127,145,146,147,148,89,149,122,150,151,152,126,153,154,155,156,157,158,159,160],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":43},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[91,127,172,173,40,174,89,159,122,175,176,177,178,152,31,179,29,180,181,182],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":43},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":193,"categoryName":194,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发",[196,197,198,199,40,200,201,202,203,90,204,205,206,91,32,31,207,208,209,29],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":43},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[216],{"categoryNo":193,"categoryName":194,"taxonomyType":112,"taxonomyTypeDesc":113},[198,218,219,220,221,222,223,40,224,225,38,226,227,228,32,31,229,230,29,231],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]