New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Wiki Researcher

by microsoft in microsoft/skills

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

OfficialMITAuto-check passedResearch & Science

Install Wiki Researcher

skills CLI
$ npx skills add microsoft/skills --skill wiki-researcher -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/skills wiki-researcher --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/plugins/deep-wiki/skills/wiki-researcher .claude/skills/wiki-researcher && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wiki-researcher
GitHub stars
3.1k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
547 words
Files
1
Skills in repo
150
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Check for git remote: Run git remote… → Ask the user: "Is this a local-only… → Determine default branch: Run git… → …
  • The user wants an in-depth investigation
  • SKILL.md covers When to Activate, Source Repository Resolution…, Core Invariants (NON-NEGOTIABLE) and Process: 5 Iterations, plus 1 more section
  • Calls git

What it does

Wiki Researcher is an agent skill from microsoft/skills, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Deep research. It works with Azure DevOps and Git. The repository describes itself as: Skills, MCP servers, Custom Agents, Agents.md for SDKs to ground Coding Agents. The licence is MIT.

When your agent uses it

  • The user wants an in-depth investigation
  • Needs to understand how something works across multiple files
  • Asks for comprehensive analysis of a specific system

Example prompts

  • “Use the wiki-researcher skill to conduct multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow…”
  • “/wiki-researcher”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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)?"
  3. Determine default branch: Run git rev-parse --abbrev-ref HEAD
  4. Do NOT proceed until source repo context is resolved

What it can do on your machine

Read from SKILL.md and the folder at commit 3898ec8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wiki Researcher loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 547 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/skills at commit 3898ec8, republished under its MIT licence (© microsoft). 547 words, ~1,118 tokens.

Download SKILL.mdSave it as .claude/skills/wiki-researcher/SKILL.md (or your agent's skills folder).
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
metadata.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 TypeRequired 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
Show full SKILL.md (233 more words)Show less

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

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/plugins/deep-wiki/skills/wiki-researcher of microsoft/skills.

Open the folder on GitHubat commit 3898ec8

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in microsoft/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Wiki Researcher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wiki Researcher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wiki Researcher this skillmicrosoft/skills3.1k1 repos~1.1kAutomated safety check: PassMIT
Diagram312362115/claude107—~2.7kAutomated safety check: PassMIT
Asksd0xdev/sd0x-harness192—~2.1kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Deep Research WorkflowTokenRhythm/opensquilla7.1k—~1.3kAutomated safety check: PassApache-2.0
Deep Researchsanjay3290/ai-skills4319 repos~683Automated safety check: NotesApache-2.0

Similar skills

  • Diagram

    312362115/claude

    专业图表生成技能：根据需求自动选择合适的图表类型，生成符合设计规范的 PNG 图表. An agent skill from 312362115/claude.

    107 GitHub stars~2.7k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Ask

    sd0xdev/sd0x-harness

    Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~2.1k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Deep Research Workflow

    TokenRhythm/opensquilla

    Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.

    7.1k GitHub stars~1.3k tokensUpdated today
    Research & ScienceAuto-check passed

  • Deep Research

    sanjay3290/ai-skills

    Execute autonomous multi-step research using Google Gemini Deep Research Agent.

    431 GitHub starsUsed in 9 repos~683 tokens
    Research & ScienceAuto-check: notes

  • Horizontal-Vertical Deep Research

    KKKKhazix/khazix-skills

    Runs a two-axis deep research method on a product, company, concept or person: its full history over time, compared with peers today, delivered as a typeset PDF report.

    21k GitHub stars~2.1k tokensUpdated 8 days ago
    Research & ScienceAuto-check passed

More from microsoft/skills

All 150 skills in this repo

  • Azure Event Hubs Python SDK Guide

    microsoft/skills

    Official

    Covers producer, consumer, and checkpoint-store setup for Azure Event Hubs streaming in Python, with Entra ID auth and partition targeting.

    3.1k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Realtime Podcast Generation

    microsoft/skills

    Official

    Builds podcast-style audio narration from text with Azure OpenAI's GPT Realtime Mini over WebSocket, from a Python FastAPI backend to a React player.

    3.1k GitHub starsUsed in 1 repo~947 tokens
    Auto-check passed

  • Frontend UI Dark TS

    microsoft/skills

    Official

    Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations.

    3.1k GitHub starsUsed in 5 repos~3.6k tokens
    Auto-check passed

  • Pydantic Models Py

    microsoft/skills

    Official

    Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants.

    3.1k GitHub starsUsed in 5 repos~496 tokens
    Auto-check passed

  • Azure AI Projects Python SDK

    microsoft/skills

    Official

    Reference for building on Microsoft Foundry with the azure-ai-projects Python SDK: project clients, versioned agents, evaluations, connections, datasets and indexes.

    3.1k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Skill Creator

    microsoft/skills

    Official

    Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services.

    3.1k GitHub starsUsed in 5 repos~17k tokens
    Auto-check passed

Works with

Categories

Questions about Wiki Researcher

What does Wiki Researcher do?

Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Wiki Researcher is an agent skill from microsoft/skills, published by the product's own GitHub organization. Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis.

When should I use Wiki Researcher?

Wiki Researcher fits situations like: the user wants an in-depth investigation; needs to understand how something works across multiple files; asks for comprehensive analysis of a specific system.

How do I install Wiki Researcher in Claude Code?

Run `npx skills add microsoft/skills --skill wiki-researcher -a claude-code`. Or copy the skill folder (.github/plugins/deep-wiki/skills/wiki-researcher in microsoft/skills) into .claude/skills/wiki-researcher in your project. Claude Code loads it when a task matches its description.

How do I install Wiki Researcher in Codex?

Run `npx skills add microsoft/skills --skill wiki-researcher -a codex`. Or copy the skill folder (.github/plugins/deep-wiki/skills/wiki-researcher in microsoft/skills) into .agents/skills/wiki-researcher in your project. Codex loads it when a task matches its description.

Can I use Wiki Researcher in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/skills --skill wiki-researcher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wiki-researcher, .gemini/skills/wiki-researcher, .github/skills/wiki-researcher and .opencode/skills/wiki-researcher in your project.

What does Wiki Researcher need to run?

Going by SKILL.md and its folder, Wiki Researcher needs the command-line tools its instructions call (git).

Does Wiki Researcher access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Wiki Researcher safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wiki Researcher use?

Wiki Researcher is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wiki Researcher use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Wiki Researcher?

Skills that share tags, products or a category with Wiki Researcher: Diagram (312362115/claude, 107 stars), Ask (sd0xdev/sd0x-harness, 192 stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Deep Research Workflow (TokenRhythm/opensquilla, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wiki Researcher?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/skills, which has 3,094 GitHub stars. The repository holds 150 skills in this directory. The repository was last updated on October 9, 2026.

Source: microsoft/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.