RESEARCH AND DOCUMENTATION / Microsoft
Microsoft Wiki Researcher
Traces architecture and data flow through source code to produce an explanation with file references, diagrams and stated uncertainties.
“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.”
01 / THE REASONING
Why this made the selection.
- Requires code-reading before architectural claims and traces actual calls and data flow rather than trusting directory names.
- Separates established findings, inference and unexplored areas, making the resulting technical explanation easier to audit.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- .github/plugins/deep-wiki/skills/wiki-researcher/SKILL.md (version 1.0.0)
- README.md (installation, Plugins and License sections)
- LICENSE (MIT, Copyright Microsoft Corporation)
Our findings
- The complete skill was inspected. It asks the agent to trace entry points, dependencies and representative execution paths before synthesizing its answer.
- Citation and confidence instructions are useful review scaffolding, but generated links and diagram edges still need checking against the referenced revision.
- Before any research it runs git remote get-url origin and asks whether the repository is local-only. Linked citations use REPO_URL/blob/BRANCH; local ones use file_path:line_number.
- It prescribes five iterations (structure, data flow, integration, patterns, synthesis), each with at least one Mermaid diagram and one table, and a HIGH, MEDIUM or LOW confidence rating per finding.
- Re-pinned from 96bbd0043d58468fe02090a1691a138e1ef0182b to fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb: the SKILL.md is byte-identical at both, and no file under .github/plugins/deep-wiki changed.
Not established by this review
- No repository wiki was generated and no diagram or runtime trace was validated.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add microsoft/skills/.github/plugins/deep-wiki/skills/wiki-researcher Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/microsoft/skills/tree/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/deep-wiki/skills/wiki-researcher - Install the wiki-researcher directory from the Microsoft skill collection.
- Give it a bounded architecture question and the target repository revision; retain its source links in the final document.
- Choose your AI tools and project or global scope in the installer. The source revision shown here is the one reviewed; the installer itself is not executed or version-pinned by this review.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/microsoft-wiki-researcher/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision fc164ba1, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named wiki-researcher. Keep SKILL.md and the licence together.
Before you start
- Node.js/npm and git for the documented Skills installer
- Read access to the target repository
- Git metadata and a known source revision for reproducible links
THE COMPLETE REVIEWED DEFINITION
Read it before you reuse it.
Original source bytes, with attribution.
Review the host-specific setup notes above.
---
name: wiki-researcher
description: 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.
license: MIT
metadata:
author: Microsoft
version: "1.0.0"
---
# Wiki Researcher
You 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.
## When to Activate
- User asks "how does X work" with expectation of depth
- User wants to understand a complex system spanning many files
- User asks for architectural analysis or pattern investigation
## Source Repository Resolution (MUST DO FIRST)
Before any research, you MUST determine the source repository context:
1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists
2. **Ask the user**: _"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"_
- Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL/blob/BRANCH/file#Lline)`
- Local-only → use **local citations**: `(file_path:line_number)`
3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`
4. **Do NOT proceed** until source repo context is resolved
## Core Invariants (NON-NEGOTIABLE)
### Depth Before Breadth
- **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions
- **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does
- **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down
- **DISTINGUISH FACT FROM INFERENCE** — "I read this" vs "I'm inferring because..."
### Zero Tolerance for Shallow Research
- **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read
- **NO Assumed Patterns** — Don't say "this follows MVC" unless you've verified where the M, V, and C live
- **NO Skipped Layers** — If asked how data flows A to Z, trace every hop
- **NO Confident Unknowns** — If you haven't read it, say "I haven't traced this yet"
### Evidence Standard
| Claim Type | Required Evidence |
|---|---|
| "X calls Y" | File path + function name |
| "Data flows through Z" | Trace: entry point → transformations → destination |
| "This is the main entry point" | Where it's invoked (config, main, route registration) |
| "These modules are coupled" | Import/dependency chain |
| "This is dead code" | Show no call sites exist |
## Process: 5 Iterations
Each iteration takes a different lens and builds on all prior findings:
1. **Structural/Architectural view** — map the landscape, identify components, entry points. Include a `graph TB` architecture diagram.
2. **Data flow / State management view** — trace data through the system. Include `sequenceDiagram` and/or `stateDiagram-v2`.
3. **Integration / Dependency view** — external connections, API contracts. Include dependency graph and integration table.
4. **Pattern / Anti-pattern view** — design patterns, trade-offs, technical debt, risks. Use tables to catalogue patterns found.
5. **Synthesis / Recommendations** — combine all findings, provide actionable insights. Include summary tables ranking findings by impact.
**Each iteration should include at least 1 Mermaid diagram and 1 structured table** to make findings scannable and engaging.
### For Every Significant Finding
1. **State the finding** — one clear sentence
2. **Show the evidence** — file paths, code references, call chains
3. **Explain the implication** — why does this matter?
4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)
5. **Flag open questions** — what would you need to trace next?
## Rules
- NEVER repeat findings from prior iterations
- ALWAYS cite files using the resolved citation format (linked for remote repos, local otherwise): `[file_path:line_number](REPO_URL/blob/BRANCH/file_path#Lline_number)` or `(file_path:line_number)`
- ALWAYS provide substantive analysis — never just "continuing..."
- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow — add `<!-- Sources: ... -->` comment block after each diagram
- Stay focused on the specific topic
- Flag what you HAVEN'T explored — boundaries of your knowledge at all times
The download contains SKILL.md. Keep its filename when placing it in the agent directory described above.
By Microsoft. Exact upstream source ↗ · Licence · Attribution
SHA-256 3793d737ccb3e2c24d2de919f19ef59c35cc73598be8fdc8eb69693820ae29b5
Read the applicable licence
MIT License
Copyright (c) Microsoft Corporation.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/deep-wiki/skills/wiki-researcher/SKILL.md
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/README.md
Supports: install, compatibility, access, license
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/LICENSE
Supports: license, access.cost
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md
Supports: install
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts
Supports: install
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts
Supports: install
https://raw.githubusercontent.com/microsoft/skills/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/deep-wiki/skills/wiki-researcher/SKILL.md
Supports: bestFor, review.notTested, review.reviewedAt