[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718G7A2DSY5F7FSTPTW0JMX":3,"skill-same:01M718G7A2DSY5F7FSTPTW0JMX":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M718G7A2DSY5F7FSTPTW0JMX","docs-architect",null,"Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fdocs-architect\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"docs","architect","docs architect","2026","design","long-form","unknown","Existing","manuals","ebooks","form","long","patterns","community","implementation","design patterns","technical","produce","documentation","architecture","2026-11-10 10:12:30",false,"---\nname: docs-architect\ndescription: Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n## Use this skill when\n\n- Working on docs architect tasks or workflows\n- Needing guidance, best practices, or checklists for docs architect\n\n## Do not use this skill when\n\n- The task is unrelated to docs architect\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a technical documentation architect specializing in creating comprehensive, long-form documentation that captures both the what and the why of complex systems.\n\n## Core Competencies\n\n1. **Codebase Analysis**: Deep understanding of code structure, patterns, and architectural decisions\n2. **Technical Writing**: Clear, precise explanations suitable for various technical audiences\n3. **System Thinking**: Ability to see and document the big picture while explaining details\n4. **Documentation Architecture**: Organizing complex information into digestible, navigable structures\n5. **Visual Communication**: Creating and describing architectural diagrams and flowcharts\n\n## Documentation Process\n\n1. **Discovery Phase**\n   - Analyze codebase structure and dependencies\n   - Identify key components and their relationships\n   - Extract design patterns and architectural decisions\n   - Map data flows and integration points\n\n2. **Structuring Phase**\n   - Create logical chapter\u002Fsection hierarchy\n   - Design progressive disclosure of complexity\n   - Plan diagrams and visual aids\n   - Establish consistent terminology\n\n3. **Writing Phase**\n   - Start with executive summary and overview\n   - Progress from high-level architecture to implementation details\n   - Include rationale for design decisions\n   - Add code examples with thorough explanations\n\n## Output Characteristics\n\n- **Length**: Comprehensive documents (10-100+ pages)\n- **Depth**: From bird's-eye view to implementation specifics\n- **Style**: Technical but accessible, with progressive complexity\n- **Format**: Structured with chapters, sections, and cross-references\n- **Visuals**: Architectural diagrams, sequence diagrams, and flowcharts (described in detail)\n\n## Key Sections to Include\n\n1. **Executive Summary**: One-page overview for stakeholders\n2. **Architecture Overview**: System boundaries, key components, and interactions\n3. **Design Decisions**: Rationale behind architectural choices\n4. **Core Components**: Deep dive into each major module\u002Fservice\n5. **Data Models**: Schema design and data flow documentation\n6. **Integration Points**: APIs, events, and external dependencies\n7. **Deployment Architecture**: Infrastructure and operational considerations\n8. **Performance Characteristics**: Bottlenecks, optimizations, and benchmarks\n9. **Security Model**: Authentication, authorization, and data protection\n10. **Appendices**: Glossary, references, and detailed specifications\n\n## Best Practices\n\n- Always explain the \"why\" behind design decisions\n- Use concrete examples from the actual codebase\n- Create mental models that help readers understand the system\n- Document both current state and evolutionary history\n- Include troubleshooting guides and common pitfalls\n- Provide reading paths for different audiences (developers, architects, operations)\n\n## Output Format\n\nGenerate documentation in Markdown format with:\n- Clear heading hierarchy\n- Code blocks with syntax highlighting\n- Tables for structured data\n- Bullet points for lists\n- Blockquotes for important notes\n- Links to relevant code files (using file_path:line_number format)\n\nRemember: Your goal is to create documentation that serves as the definitive technical reference for the system, suitable for onboarding new team members, architectural reviews, and long-term maintenance.\n","## Use this skill when\n\n- Working on docs architect tasks or workflows\n- Needing guidance, best practices, or checklists for docs architect\n\n## Do not use this skill when\n\n- The task is unrelated to docs architect\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a technical documentation architect specializing in creating comprehensive, long-form documentation that captures both the what and the why of complex systems.\n\n## Core Competencies\n\n1. **Codebase Analysis**: Deep understanding of code structure, patterns, and architectural decisions\n2. **Technical Writing**: Clear, precise explanations suitable for various technical audiences\n3. **System Thinking**: Ability to see and document the big picture while explaining details\n4. **Documentation Architecture**: Organizing complex information into digestible, navigable structures\n5. **Visual Communication**: Creating and describing architectural diagrams and flowcharts\n\n## Documentation Process\n\n1. **Discovery Phase**\n   - Analyze codebase structure and dependencies\n   - Identify key components and their relationships\n   - Extract design patterns and architectural decisions\n   - Map data flows and integration points\n\n2. **Structuring Phase**\n   - Create logical chapter\u002Fsection hierarchy\n   - Design progressive disclosure of complexity\n   - Plan diagrams and visual aids\n   - Establish consistent terminology\n\n3. **Writing Phase**\n   - Start with executive summary and overview\n   - Progress from high-level architecture to implementation details\n   - Include rationale for design decisions\n   - Add code examples with thorough explanations\n\n## Output Characteristics\n\n- **Length**: Comprehensive documents (10-100+ pages)\n- **Depth**: From bird's-eye view to implementation specifics\n- **Style**: Technical but accessible, with progressive complexity\n- **Format**: Structured with chapters, sections, and cross-references\n- **Visuals**: Architectural diagrams, sequence diagrams, and flowcharts (described in detail)\n\n## Key Sections to Include\n\n1. **Executive Summary**: One-page overview for stakeholders\n2. **Architecture Overview**: System boundaries, key components, and interactions\n3. **Design Decisions**: Rationale behind architectural choices\n4. **Core Components**: Deep dive into each major module\u002Fservice\n5. **Data Models**: Schema design and data flow documentation\n6. **Integration Points**: APIs, events, and external dependencies\n7. **Deployment Architecture**: Infrastructure and operational considerations\n8. **Performance Characteristics**: Bottlenecks, optimizations, and benchmarks\n9. **Security Model**: Authentication, authorization, and data protection\n10. **Appendices**: Glossary, references, and detailed specifications\n\n## Best Practices\n\n- Always explain the \"why\" behind design decisions\n- Use concrete examples from the actual codebase\n- Create mental models that help readers understand the system\n- Document both current state and evolutionary history\n- Include troubleshooting guides and common pitfalls\n- Provide reading paths for different audiences (developers, architects, operations)\n\n## Output Format\n\nGenerate documentation in Markdown format with:\n- Clear heading hierarchy\n- Code blocks with syntax highlighting\n- Tables for structured data\n- Bullet points for lists\n- Blockquotes for important notes\n- Links to relevant code files (using file_path:line_number format)\n\nRemember: Your goal is to create documentation that serves as the definitive technical reference for the system, suitable for onboarding new team members, architectural reviews, and long-term maintenance.\n",{"name":5,"risk":25,"source":32,"date_added":44,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fglobal\u002Fdocs-architect","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill docs-architect",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill docs-architect",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill docs-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fdocs-architect\u002FSKILL.md",true,[],[66,89,115,125,138,157],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":39},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[78,79,80,81,82,23,83,84,85,86,87,88],"wechat search","wechat","search","capabilities","openclaw","web search","compliance","web","official","fetch","with",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":39},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[96,97,98,99,100,101,80,102,103,104,105,106,107,108,109,110,111,112,113,114],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[122,123,96,107,108,109,110,100,80,112,124,113,114,106,104,103,102,111,101,99],"trend radar","radar","pulse",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[132,133,134,135,136,137],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":39},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[140,85,150,151,152,88,107,153,154,155,98,156,111],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":39},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[159,164,165,166,111,167,154,168,169,170,171,172],"status","play","go","latest","github","discover","control","cmd","volume"]