[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CD3KJ2GNJWCZD89GCEBWK2":3,"skill-same:01M6CD3KJ2GNJWCZD89GCEBWK2":122},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":32,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":73,"install":74,"resources":87},"01M6CD3KJ2GNJWCZD89GCEBWK2","technical-writing",null,"Writes and reviews project copy, READMEs, developer documentation, tutorials, API and CLI references, UI text, errors, and agent instructions. Use whenever creating or revising project-facing prose; grounds claims in current behavior and preserves meaning while improving clarity.","cercova-studios\u002F10x-swe","cercova-studios","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217108198?v=4","01M6CCYGHXTH80N3BXRW6KESTE","Cercova Studios","01M6CCYGPADH5MJDR0VNNR775C",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[19,24,29],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":30,"categoryName":31,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000036","内容创作者",[33,34,35,36,37,38,39,40,41,42,43,5,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"technical writing","technical","writing","instructions","agent instructions","SWE","claims","meaning","developer documentation","errors","reviews","project","references","use","behavior","10x","text","clarity","api","developer","ui","plugin","brainstorming","documentation","cli","2026-11-10 10:12:30",false,"---\nname: technical-writing\ndescription: Writes and reviews project copy, READMEs, developer documentation, tutorials,\n  API and CLI references, UI text, errors, and agent instructions. Use whenever creating\n  or revising project-facing prose; grounds claims in current behavior and preserves\n  meaning while improving clarity.\nmetadata:\n  skill-graph-id: plugin\u002F10x-swe\u002Ftechnical-writing\n  skill-graph-uses: ''\n  skill-graph-used-by: plugin\u002F10x-swe\u002Fbrainstorming\n---\n\n\u003Cobjective>\nHelp a reader understand a product, choose an action, and complete it correctly.\nWrite concise, accurate prose for humans and agents. Follow project terminology,\nvoice and documentation policy before general style preferences.\n\u003C\u002Fobjective>\n\n\u003Cquick_start>\nIdentify the reader, their goal, the artifact and the first useful outcome.\nInspect the current capability contract before drafting. For a small edit, revise\nand check the affected sentence; for a substantial rewrite, follow the process.\nRead [README guidance](references\u002Freadmes.md) for landing pages,\n[developer documentation](references\u002Fdeveloper-docs.md) for procedures\u002Freferences,\nand [language and fidelity](references\u002Fstyle.md) for wording and copy reviews.\n\u003C\u002Fquick_start>\n\n\u003Cprinciples>\n- Lead with purpose, usefulness or the reader's next action. Define unfamiliar concepts with a concrete example.\n- Use familiar words, active verbs and consistent names. State the actor when responsibility matters. Keep one topic per paragraph.\n- Preserve facts, conditions, scope, uncertainty, negation and requirement strength. Keep code, flags, identifiers, paths, units, quotations and URLs exact.\n- Use a fact brief as evidence, not copy to paste. Express verified scope positively instead of filling product copy with absence lists or repeated disclaimers.\n- Describe implemented behavior precisely. Skills prescribe work; they do not guarantee agent outcomes. Scope local\u002Foffline, safety and performance claims to the verified capability.\n- Use stricter sentence discipline for procedures, errors and agent instructions. Keep README explanations natural; preserve approved product voice in UI and marketing copy.\n- Keep current capabilities, setup, contracts and operations in repo docs. Put plans, TODOs, experiments and detailed validation history in the project wiki\u002Farchive. Retain essential requirements and recovery steps with the code.\n\u003C\u002Fprinciples>\n\n\u003Cprocess>\n1. **Ground.** Read the project instructions and relevant architecture. Build a compact fact brief: audience, task, current capabilities, prerequisites, exact examples and important effects. Verify uncertain commands with source\u002Fhelp. Keep research notes separate from the published copy.\n2. **Structure.** Give the artifact one job: README orientation\u002Ffirst success; how-to task completion; reference exact contracts; architecture current boundaries; UI copy the user's decision or next step. Load only the relevant reference.\n3. **Draft.** Write the shortest complete explanation for that reader. Put prerequisites before actions. Show a concrete useful task and its expected result where applicable. Link deeper detail instead of repeating it.\n4. **Challenge.** Compare every consequential claim and example with the fact brief. Check modality, actors, conditions, errors, defaults, privacy, data ownership and approval. Check what each condition modifies; preserve unconditional constraints across all actions. Fix misleading implications as well as literal errors.\n5. **Edit.** Remove repetition, vague promises, jargon, filler and development narration. Preserve necessary detail even when a sentence must be longer. Apply [language and fidelity](references\u002Fstyle.md).\n6. **Verify.** Check links, anchors, formatting and example syntax. Run the safe representative task when authorized; syntax checks alone do not establish that a workflow works. Review changed UI copy in its actual context when practical. Report check limits outside the document.\n\u003C\u002Fprocess>\n\n\u003Ccollaboration>\nUse one agent for routine edits. For substantial rewrites, an investigator can\nsupply verified facts, a writer draft independently, and a different reviewer\nchallenge the claims before an editor combines the best parts. A fresh reader\ncan attempt the first task. See [review and agent roles](references\u002Freview.md).\nChoose models by task needs and observed results, not fixed brand rankings.\nDelegation, external model calls and publication require existing authorization;\nthis skill grants none of them. Share only material allowed for that destination.\n\u003C\u002Fcollaboration>\n\n\u003Csuccess_criteria>\nThe intended reader can explain the purpose and find the next useful action.\nConsequential claims match current behavior; requirements and examples agree.\nRewrites preserve meaning and operational safeguards. Links\u002Fexamples have the\nappropriate checks. Deliver the requested artifact without editorial narration;\nput rationale, evidence and unresolved questions in a separate review when useful.\nSource attribution and adaptation details are in [sources](references\u002Fsources.md).\n\u003C\u002Fsuccess_criteria>\n","\u003Cobjective>\nHelp a reader understand a product, choose an action, and complete it correctly.\nWrite concise, accurate prose for humans and agents. Follow project terminology,\nvoice and documentation policy before general style preferences.\n\u003C\u002Fobjective>\n\n\u003Cquick_start>\nIdentify the reader, their goal, the artifact and the first useful outcome.\nInspect the current capability contract before drafting. For a small edit, revise\nand check the affected sentence; for a substantial rewrite, follow the process.\nRead [README guidance](references\u002Freadmes.md) for landing pages,\n[developer documentation](references\u002Fdeveloper-docs.md) for procedures\u002Freferences,\nand [language and fidelity](references\u002Fstyle.md) for wording and copy reviews.\n\u003C\u002Fquick_start>\n\n\u003Cprinciples>\n- Lead with purpose, usefulness or the reader's next action. Define unfamiliar concepts with a concrete example.\n- Use familiar words, active verbs and consistent names. State the actor when responsibility matters. Keep one topic per paragraph.\n- Preserve facts, conditions, scope, uncertainty, negation and requirement strength. Keep code, flags, identifiers, paths, units, quotations and URLs exact.\n- Use a fact brief as evidence, not copy to paste. Express verified scope positively instead of filling product copy with absence lists or repeated disclaimers.\n- Describe implemented behavior precisely. Skills prescribe work; they do not guarantee agent outcomes. Scope local\u002Foffline, safety and performance claims to the verified capability.\n- Use stricter sentence discipline for procedures, errors and agent instructions. Keep README explanations natural; preserve approved product voice in UI and marketing copy.\n- Keep current capabilities, setup, contracts and operations in repo docs. Put plans, TODOs, experiments and detailed validation history in the project wiki\u002Farchive. Retain essential requirements and recovery steps with the code.\n\u003C\u002Fprinciples>\n\n\u003Cprocess>\n1. **Ground.** Read the project instructions and relevant architecture. Build a compact fact brief: audience, task, current capabilities, prerequisites, exact examples and important effects. Verify uncertain commands with source\u002Fhelp. Keep research notes separate from the published copy.\n2. **Structure.** Give the artifact one job: README orientation\u002Ffirst success; how-to task completion; reference exact contracts; architecture current boundaries; UI copy the user's decision or next step. Load only the relevant reference.\n3. **Draft.** Write the shortest complete explanation for that reader. Put prerequisites before actions. Show a concrete useful task and its expected result where applicable. Link deeper detail instead of repeating it.\n4. **Challenge.** Compare every consequential claim and example with the fact brief. Check modality, actors, conditions, errors, defaults, privacy, data ownership and approval. Check what each condition modifies; preserve unconditional constraints across all actions. Fix misleading implications as well as literal errors.\n5. **Edit.** Remove repetition, vague promises, jargon, filler and development narration. Preserve necessary detail even when a sentence must be longer. Apply [language and fidelity](references\u002Fstyle.md).\n6. **Verify.** Check links, anchors, formatting and example syntax. Run the safe representative task when authorized; syntax checks alone do not establish that a workflow works. Review changed UI copy in its actual context when practical. Report check limits outside the document.\n\u003C\u002Fprocess>\n\n\u003Ccollaboration>\nUse one agent for routine edits. For substantial rewrites, an investigator can\nsupply verified facts, a writer draft independently, and a different reviewer\nchallenge the claims before an editor combines the best parts. A fresh reader\ncan attempt the first task. See [review and agent roles](references\u002Freview.md).\nChoose models by task needs and observed results, not fixed brand rankings.\nDelegation, external model calls and publication require existing authorization;\nthis skill grants none of them. Share only material allowed for that destination.\n\u003C\u002Fcollaboration>\n\n\u003Csuccess_criteria>\nThe intended reader can explain the purpose and find the next useful action.\nConsequential claims match current behavior; requirements and examples agree.\nRewrites preserve meaning and operational safeguards. Links\u002Fexamples have the\nappropriate checks. Deliver the requested artifact without editorial narration;\nput rationale, evidence and unresolved questions in a separate review when useful.\nSource attribution and adaptation details are in [sources](references\u002Fsources.md).\n\u003C\u002Fsuccess_criteria>\n",{"name":5,"metadata":63,"description":7},{"skill-graph-id":64,"skill-graph-uses":65,"skill-graph-used-by":66},"plugin\u002F10x-swe\u002Ftechnical-writing","","plugin\u002F10x-swe\u002Fbrainstorming","main","12441d84a8a292fcc94f47bc98877cbefd9b52e2","plugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing",0,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe","https:\u002F\u002Fgithub.com\u002Fcercova-studios","2026-11-12 00:33:06",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add cercova-studios\u002F10x-swe --skill technical-writing",{"tool":80,"command":81},"bunx","bunx skills add cercova-studios\u002F10x-swe --skill technical-writing",{"tool":83,"command":84},"pnpm","pnpm dlx skills add cercova-studios\u002F10x-swe --skill technical-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",true,[88,92,98,102,106,110,114,118],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fdeveloper-docs.md","REFERENCE","参考文档",1921,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Fdeveloper-docs.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Freadme-template.md",2134,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Freadme-template.md",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Freadmes.md",2490,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Freadmes.md",{"path":107,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Freview.md",2075,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Freview.md",{"path":111,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fsources.md",2131,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Fsources.md",{"path":115,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fstyle.md",2373,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Fstyle.md",{"path":119,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fupstream-asd-ste100-LICENSE.txt",1075,"https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ftechnical-writing\u002Freferences\u002Fupstream-asd-ste100-LICENSE.txt",[123,158,193,213,231,243],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":58},"01M6CD3T6EQ9N5KPNXCM6ABHVA","turnstile-spin","Set up Cloudflare Turnstile end-to-end in a project. Scan the codebase, create the widget via the Cloudflare API, embed it where user requests need bot verification (form submissions, SPA actions, API endpoints, download links, comment or vote submissions, etc.), wire canonical server-side siteverify in the customer's existing backend, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form or endpoint from bots, or fix a Turnstile integration. Uses Cloudflare's documented Turnstile contract.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Fturnstile-spin\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Fturnstile-spin\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000010","后端与接口",[135,136,137,138,139,140,141,142,51,143,144,145,146,147,54,148,149,150,151,152,153,154,155,44,156,38,157],"turnstile spin","SET","nextjs","actions","up","fix","cloudflare","bot","permissions","create","astro","server","verification","endpoints","customer","backend","sveltekit","integration","app","bots","spa","end","when",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":174,"publishedAt":58},"01M6CD0BJYRNV610HYYPX933RE","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002F10x-swe\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[165,168,171],{"categoryNo":166,"categoryName":167,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":169,"categoryName":170,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":172,"categoryName":173,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000032","设计师",[175,176,177,144,178,179,180,181,182,183,46,184,185,186,187,188,189,157,190,191,192],"frontend design","frontend","design","web","quality","applications","creative","web components","Production","code","components","user","generic","aesthetics","pages","with","high","build",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":58},"01M6CD4QX8C4DST98AY21HEYCM","source-insights","Prepare inspected source evidence, preserve exact citations, and publish reviewed insights into an explicit local library.","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge\u002Fskills\u002Fsource-insights\u002FSKILL.md",[],[200,201,202,203,204,205,206,207,208,209,210,211,212],"source insights","insights","source","publish","Citations","evidence","library","workflows","prepare","session","global","local","preserve",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":222,"publishedAt":58},"01M6CD4N1HVNC1EXPEBZT7YS31","skill-graph","Discover skills and workflows through independent lexical search, relationship paths and a terminal graph.","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge\u002Fskills\u002Fskill-graph\u002FSKILL.md",[219],{"categoryNo":220,"categoryName":221,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",[223,224,54,207,225,48,226,210,227,228,229,38,230],"graph","skill graph","terminal","search","discover skills","discover","paths","relationship",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":237,"publishedAt":58},"01M6CD4HQKXNZ57YEGD8QVK6Z6","session-search","Recall public session turns with exact provenance, bounded excerpts and independent piped exports.","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge\u002Fskills\u002Fsession-search\u002FSKILL.md",[],[226,209,238,239,207,240,241,210,190,201,202,242],"session search","public","provenance","recall","bounded",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":255,"publishedAt":58},"01M6CD4ET7DVNBYPDAMAYMSK2T","newsletter","Produce a private local AI newsletter from bounded public research, with cited deep dives, HTML\u002FMarkdown output, Dagu scheduling and seven-day retention.","https:\u002F\u002Fgithub.com\u002Fcercova-studios\u002F10x-swe\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge\u002Fskills\u002Fnewsletter\u002FSKILL.md",[249,252],{"categoryNo":250,"categoryName":251,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":253,"categoryName":254,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究",[245,256,257,258,259,239,207,260,261,262,263,210,190,264,265,211,242,266],"local ai","dagu","produce","research","markdown","scheduling","html","daily","deep","retention","output"]