SkillAgentSearch skills...

wiki-researcher

Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis

Install / Use

npx skills add microsoft/skills --skill wiki-researcher

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of wiki-researcher

wiki-researcher scores 83/100 on our quality scale, 331st of 421 Education & Research skills we index.

Its SKILL.md is 4.4 KB long, well organised into 10 sections and no code examples: a solid amount of guidance for an agent.

With 3,051 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wiki-researcher is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

wiki-researcher compared with similar skills

All 4 of these similar skills score higher than wiki-researcher; compare them before choosing.

SkillScoreStarsUpdatedFormat
wiki-researcher (this skill)by microsoft833.1k54d agoSKILL.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install wiki-researcher?
Run npx skills add microsoft/skills --skill wiki-researcher. The install tabs above show the steps for each supported agent.
Which AI agents does wiki-researcher work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wiki-researcher safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wiki-researcher still maintained?
The repository was last updated about 2 months ago, so wiki-researcher is actively maintained.

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

Related Skills

View on GitHub
GitHub Stars3.1k
CategoryEducation
Updated1mo ago
Forks349

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions