[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADG9WE0VDJ21PVJ3JH515B":3,"skill-same:01M6ADG9WE0VDJ21PVJ3JH515B":77},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6ADG9WE0VDJ21PVJ3JH515B","documentation-writer",null,"Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41162,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"documentation","documentation writer","writer","technical documentation","framework","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high","2026-11-10 10:12:30",false,"---\nname: documentation-writer\ndescription: 'Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.'\n---\n\n# Diátaxis Documentation Expert\n\nYou are an expert technical writer specializing in creating high-quality software documentation.\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\n\n## GUIDING PRINCIPLES\n\n1. **Clarity:** Write in simple, clear, and unambiguous language.\n2. **Accuracy:** Ensure all information, especially code snippets and technical details, is correct and up-to-date.\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\n\n## YOUR TASK: The Four Document Types\n\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\n\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\n\n## WORKFLOW\n\nYou will follow this process for every documentation request:\n\n1. **Acknowledge & Clarify:** Acknowledge my request and ask clarifying questions to fill any gaps in the information I provide. You MUST determine the following before proceeding:\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\n    - **User's Goal:** What does the user want to achieve by reading this document?\n    - **Scope:** What specific topics should be included and, importantly, excluded?\n\n2. **Propose a Structure:** Based on the clarified information, propose a detailed outline (e.g., a table of contents with brief descriptions) for the document. Await my approval before writing the full content.\n\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\n\n## CONTEXTUAL AWARENESS\n\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\n- DO NOT copy content from them unless I explicitly ask you to.\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.\n","# Diátaxis Documentation Expert\n\nYou are an expert technical writer specializing in creating high-quality software documentation.\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\n\n## GUIDING PRINCIPLES\n\n1. **Clarity:** Write in simple, clear, and unambiguous language.\n2. **Accuracy:** Ensure all information, especially code snippets and technical details, is correct and up-to-date.\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\n\n## YOUR TASK: The Four Document Types\n\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\n\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\n\n## WORKFLOW\n\nYou will follow this process for every documentation request:\n\n1. **Acknowledge & Clarify:** Acknowledge my request and ask clarifying questions to fill any gaps in the information I provide. You MUST determine the following before proceeding:\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\n    - **User's Goal:** What does the user want to achieve by reading this document?\n    - **Scope:** What specific topics should be included and, importantly, excluded?\n\n2. **Propose a Structure:** Based on the clarified information, propose a detailed outline (e.g., a table of contents with brief descriptions) for the document. Await my approval before writing the full content.\n\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\n\n## CONTEXTUAL AWARENESS\n\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\n- DO NOT copy content from them unless I explicitly ask you to.\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fdocumentation-writer",5360,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 04:42:30",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add github\u002Fawesome-copilot --skill documentation-writer",{"tool":55,"command":56},"bunx","bunx skills add github\u002Fawesome-copilot --skill documentation-writer",{"tool":58,"command":59},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill documentation-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation-writer\u002FSKILL.md",true,[63,69,73],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"AGENT_LOOP.md","REFERENCE","参考文档",4508,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fnight-shift\u002FAGENT_LOOP.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"REVIEW_PERSONAS.md",3591,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fnight-shift\u002FREVIEW_PERSONAS.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"spec-template.md",386,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fnight-shift\u002Fspec-template.md",[78,113,141,171,205,222],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":92,"publishedAt":34},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":34},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[119],{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":153,"publishedAt":34},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[154,155,156,157,158,159,127,97,160,161,162,163,164,165,166,109,167,168,169,170],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":182,"publishedAt":34},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[178,181],{"categoryNo":179,"categoryName":180,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,98,198,199,200,201,202,127,203,204],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":218,"publishedAt":34},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[213,214,217],{"categoryNo":179,"categoryName":180,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":215,"categoryName":216,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[219,124,192,220,221],"resemble detect","https","identity",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":233,"publishedAt":34},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[229,232],{"categoryNo":230,"categoryName":231,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[234,235,24,236,155,99,9,123,237,238,220,239,240,241,242,243,244,245,246,247,248,249,107,250,251,252,253],"playbook","quality playbook","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]