[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F35ZV04QC495WQBE9HM98":3,"skill-same:01M73F35ZV04QC495WQBE9HM98":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M73F35ZV04QC495WQBE9HM98","wiki-architect",null,"Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-architect\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wiki-architect\ndescription: Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Architect\n\nYou are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.\n\n## When to Activate\n\n- User asks to \"create a wiki\", \"document this repo\", \"generate docs\"\n- User wants to understand project structure or architecture\n- User asks for a table of contents or documentation plan\n- User asks for an onboarding guide or \"zero to hero\" path\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore any analysis, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Procedure\n\n1. **Resolve source repo** (see above — MUST be first)\n2. **Scan** the repository file tree and README\n3. **Detect** project type, languages, frameworks, architectural patterns, key technologies\n4. **Identify** layers: presentation, business logic, data access, infrastructure\n5. **Generate** a hierarchical JSON catalogue with:\n   - **Onboarding**: Contributor Guide, Staff Engineer Guide, Executive Guide, Product Manager Guide (in `onboarding\u002F` folder)\n   - **Getting Started**: overview, setup, usage, quick reference\n   - **Deep Dive**: architecture → subsystems → components → methods\n6. **Cite** real files in every section prompt using linked or local citation format\n\n## Onboarding Guide Architecture\n\nThe catalogue MUST include an Onboarding section (always first, uncollapsed) containing:\n\n1. **Contributor Guide** — For new contributors (assumes Python\u002FJS). Progressive depth:\n   - Part I: Language\u002Fframework\u002Ftechnology foundations with cross-language comparisons\n   - Part II: This codebase's architecture and domain model\n   - Part III: Dev setup, testing, codebase navigation, contributing\n   - Appendices: 40+ term glossary, key file reference\n\n2. **Staff Engineer Guide** — For staff\u002Fprincipal ICs. Dense, opinionated. Includes:\n   - The ONE core architectural insight with pseudocode in a different language\n   - System architecture Mermaid diagram, domain model ER diagram\n   - Design tradeoffs, decision log, dependency rationale, \"where to go deep\" reading order\n\n3. **Executive Guide** — For VP\u002Fdirector-level leaders. NO code snippets. Includes:\n   - Capability map, risk assessment, technology investment thesis\n   - Cost\u002Fscaling model, dependency map, actionable recommendations\n\n4. **Product Manager Guide** — For PMs. ZERO engineering jargon. Includes:\n   - User journey maps, feature capability map, known limitations\n   - Data\u002Fprivacy overview, configuration\u002Ffeature flags, FAQ\n\n## Language Detection\n\nDetect primary language from file extensions and build files, then select a comparison language:\n- C#\u002FJava\u002FGo\u002FTypeScript → Python as comparison\n- Python → JavaScript as comparison\n- Rust → C++ or Go as comparison\n\n## Constraints\n\n- Max nesting depth: 4 levels\n- Max 8 children per section\n- Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding)\n- Every prompt must reference specific files\n- Derive all titles from actual repository content — never use generic placeholders\n\n## Output\n\nJSON code block following the catalogue schema with `items[].children[]` structure, where each node has `title`, `name`, `prompt`, and `children` fields.\n","# Wiki Architect\n\nYou are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.\n\n## When to Activate\n\n- User asks to \"create a wiki\", \"document this repo\", \"generate docs\"\n- User wants to understand project structure or architecture\n- User asks for a table of contents or documentation plan\n- User asks for an onboarding guide or \"zero to hero\" path\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore any analysis, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Procedure\n\n1. **Resolve source repo** (see above — MUST be first)\n2. **Scan** the repository file tree and README\n3. **Detect** project type, languages, frameworks, architectural patterns, key technologies\n4. **Identify** layers: presentation, business logic, data access, infrastructure\n5. **Generate** a hierarchical JSON catalogue with:\n   - **Onboarding**: Contributor Guide, Staff Engineer Guide, Executive Guide, Product Manager Guide (in `onboarding\u002F` folder)\n   - **Getting Started**: overview, setup, usage, quick reference\n   - **Deep Dive**: architecture → subsystems → components → methods\n6. **Cite** real files in every section prompt using linked or local citation format\n\n## Onboarding Guide Architecture\n\nThe catalogue MUST include an Onboarding section (always first, uncollapsed) containing:\n\n1. **Contributor Guide** — For new contributors (assumes Python\u002FJS). Progressive depth:\n   - Part I: Language\u002Fframework\u002Ftechnology foundations with cross-language comparisons\n   - Part II: This codebase's architecture and domain model\n   - Part III: Dev setup, testing, codebase navigation, contributing\n   - Appendices: 40+ term glossary, key file reference\n\n2. **Staff Engineer Guide** — For staff\u002Fprincipal ICs. Dense, opinionated. Includes:\n   - The ONE core architectural insight with pseudocode in a different language\n   - System architecture Mermaid diagram, domain model ER diagram\n   - Design tradeoffs, decision log, dependency rationale, \"where to go deep\" reading order\n\n3. **Executive Guide** — For VP\u002Fdirector-level leaders. NO code snippets. Includes:\n   - Capability map, risk assessment, technology investment thesis\n   - Cost\u002Fscaling model, dependency map, actionable recommendations\n\n4. **Product Manager Guide** — For PMs. ZERO engineering jargon. Includes:\n   - User journey maps, feature capability map, known limitations\n   - Data\u002Fprivacy overview, configuration\u002Ffeature flags, FAQ\n\n## Language Detection\n\nDetect primary language from file extensions and build files, then select a comparison language:\n- C#\u002FJava\u002FGo\u002FTypeScript → Python as comparison\n- Python → JavaScript as comparison\n- Rust → C++ or Go as comparison\n\n## Constraints\n\n- Max nesting depth: 4 levels\n- Max 8 children per section\n- Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding)\n- Every prompt must reference specific files\n- Derive all titles from actual repository content — never use generic placeholders\n\n## Output\n\nJSON code block following the catalogue schema with `items[].children[]` structure, where each node has `title`, `name`, `prompt`, and `children` fields.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","1.0.0","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-architect",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-architect",{"tool":41,"command":42},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-architect",{"tool":44,"command":45},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-architect\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\u002FSKILL.md",[],[],{"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":84,"publishedAt":19},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]