C✳CODEZ.WIN
🌐 English

Localized reading guide

wiki-researcherPurpose, usage and source

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.

Source retrieved:

Source repository
microsoft/skills
SKILL.md
.github/plugins/deep-wiki/skills/wiki-researcher/SKILL.md
Repository stars
3,157
Repository updated
2026-10-31
Categories
research
Last collected

License: MIT

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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.

How the upstream workflow works

Process: 5 Iterations

Each iteration takes a different lens and builds on all prior findings: Structural/Architectural view — map the landscape, identify components, entry points. Include a graph TB architecture diagram. Data flow / State management view — trace data through the system. Include sequenceDiagram and/or stateDiagram-v2. Integration / Dependency view — external connections, API contracts. Include dependency graph and integration table.

Upstream passage · L55 ↗

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

Upstream passage · L14 ↗

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.

Upstream passage · L10 ↗

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
00d66a64919edca5bca2c673373444e36a4b5461
Source SHA-256
3793d737ccb3e2c24d2de919f19ef59c35cc73598be8fdc8eb69693820ae29b5
Back to the full Skill catalog