[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F3KMX30VR45XAWKHJKFGP":3,"skill-same:01M73F3KMX30VR45XAWKHJKFGP":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},"01M73F3KMX30VR45XAWKHJKFGP","wiki-researcher",null,"Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how something works across multiple files, or asks for comprehensive analysis of a specific system or pattern.","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-researcher\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wiki-researcher\ndescription: Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how something works across multiple files, or asks for comprehensive analysis of a specific system or pattern.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Researcher\n\nYou are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.\n\n## When to Activate\n\n- User asks \"how does X work\" with expectation of depth\n- User wants to understand a complex system spanning many files\n- User asks for architectural analysis or pattern investigation\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore any research, 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## Core Invariants (NON-NEGOTIABLE)\n\n### Depth Before Breadth\n- **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions\n- **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does\n- **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down\n- **DISTINGUISH FACT FROM INFERENCE** — \"I read this\" vs \"I'm inferring because...\"\n\n### Zero Tolerance for Shallow Research\n- **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read\n- **NO Assumed Patterns** — Don't say \"this follows MVC\" unless you've verified where the M, V, and C live\n- **NO Skipped Layers** — If asked how data flows A to Z, trace every hop\n- **NO Confident Unknowns** — If you haven't read it, say \"I haven't traced this yet\"\n\n### Evidence Standard\n\n| Claim Type | Required Evidence |\n|---|---|\n| \"X calls Y\" | File path + function name |\n| \"Data flows through Z\" | Trace: entry point → transformations → destination |\n| \"This is the main entry point\" | Where it's invoked (config, main, route registration) |\n| \"These modules are coupled\" | Import\u002Fdependency chain |\n| \"This is dead code\" | Show no call sites exist |\n\n## Process: 5 Iterations\n\nEach iteration takes a different lens and builds on all prior findings:\n\n1. **Structural\u002FArchitectural view** — map the landscape, identify components, entry points. Include a `graph TB` architecture diagram.\n2. **Data flow \u002F State management view** — trace data through the system. Include `sequenceDiagram` and\u002For `stateDiagram-v2`.\n3. **Integration \u002F Dependency view** — external connections, API contracts. Include dependency graph and integration table.\n4. **Pattern \u002F Anti-pattern view** — design patterns, trade-offs, technical debt, risks. Use tables to catalogue patterns found.\n5. **Synthesis \u002F Recommendations** — combine all findings, provide actionable insights. Include summary tables ranking findings by impact.\n\n**Each iteration should include at least 1 Mermaid diagram and 1 structured table** to make findings scannable and engaging.\n\n### For Every Significant Finding\n\n1. **State the finding** — one clear sentence\n2. **Show the evidence** — file paths, code references, call chains\n3. **Explain the implication** — why does this matter?\n4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)\n5. **Flag open questions** — what would you need to trace next?\n\n## Rules\n\n- NEVER repeat findings from prior iterations\n- ALWAYS cite files using the resolved citation format (linked for remote repos, local otherwise): `[file_path:line_number](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile_path#Lline_number)` or `(file_path:line_number)`\n- ALWAYS provide substantive analysis — never just \"continuing...\"\n- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow — add `\u003C!-- Sources: ... -->` comment block after each diagram\n- Stay focused on the specific topic\n- Flag what you HAVEN'T explored — boundaries of your knowledge at all times\n","# Wiki Researcher\n\nYou are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.\n\n## When to Activate\n\n- User asks \"how does X work\" with expectation of depth\n- User wants to understand a complex system spanning many files\n- User asks for architectural analysis or pattern investigation\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore any research, 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## Core Invariants (NON-NEGOTIABLE)\n\n### Depth Before Breadth\n- **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions\n- **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does\n- **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down\n- **DISTINGUISH FACT FROM INFERENCE** — \"I read this\" vs \"I'm inferring because...\"\n\n### Zero Tolerance for Shallow Research\n- **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read\n- **NO Assumed Patterns** — Don't say \"this follows MVC\" unless you've verified where the M, V, and C live\n- **NO Skipped Layers** — If asked how data flows A to Z, trace every hop\n- **NO Confident Unknowns** — If you haven't read it, say \"I haven't traced this yet\"\n\n### Evidence Standard\n\n| Claim Type | Required Evidence |\n|---|---|\n| \"X calls Y\" | File path + function name |\n| \"Data flows through Z\" | Trace: entry point → transformations → destination |\n| \"This is the main entry point\" | Where it's invoked (config, main, route registration) |\n| \"These modules are coupled\" | Import\u002Fdependency chain |\n| \"This is dead code\" | Show no call sites exist |\n\n## Process: 5 Iterations\n\nEach iteration takes a different lens and builds on all prior findings:\n\n1. **Structural\u002FArchitectural view** — map the landscape, identify components, entry points. Include a `graph TB` architecture diagram.\n2. **Data flow \u002F State management view** — trace data through the system. Include `sequenceDiagram` and\u002For `stateDiagram-v2`.\n3. **Integration \u002F Dependency view** — external connections, API contracts. Include dependency graph and integration table.\n4. **Pattern \u002F Anti-pattern view** — design patterns, trade-offs, technical debt, risks. Use tables to catalogue patterns found.\n5. **Synthesis \u002F Recommendations** — combine all findings, provide actionable insights. Include summary tables ranking findings by impact.\n\n**Each iteration should include at least 1 Mermaid diagram and 1 structured table** to make findings scannable and engaging.\n\n### For Every Significant Finding\n\n1. **State the finding** — one clear sentence\n2. **Show the evidence** — file paths, code references, call chains\n3. **Explain the implication** — why does this matter?\n4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)\n5. **Flag open questions** — what would you need to trace next?\n\n## Rules\n\n- NEVER repeat findings from prior iterations\n- ALWAYS cite files using the resolved citation format (linked for remote repos, local otherwise): `[file_path:line_number](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile_path#Lline_number)` or `(file_path:line_number)`\n- ALWAYS provide substantive analysis — never just \"continuing...\"\n- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow — add `\u003C!-- Sources: ... -->` comment block after each diagram\n- Stay focused on the specific topic\n- Flag what you HAVEN'T explored — boundaries of your knowledge at all times\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-researcher",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-researcher",{"tool":41,"command":42},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-researcher",{"tool":44,"command":45},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-researcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-researcher\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",[],[]]