AGENT SKILL

wiki-researcher

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
所属仓库
microsoft/skills
最近更新
2026-11-14
Stars
★ 3.2k
Forks
368

01 前言 Front Matter

name
wiki-researcher
license
MIT
metadata
{ "author": "Microsoft", "version": "1.0.0" }
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.

03 SKILL.md 正文

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

04 同仓库更多 Skills

microsoft
microsoft/skills

azure-advisor-cost-optimization

Analyze Azure Advisor Cost/IdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: "find unused Azure resources", "what resources am I paying for but no longer using", "idle-resource savings", "historical idle-resource savings", "are these idle resources safe to delete". Generic Cost, other subcategories, and cross-category requests use azure-advisor.

★ 3.2k
microsoft
microsoft/skills

skill-creator

Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.

Skill与智能体开发
★ 3.2k
microsoft
microsoft/skills

podcast-generation

Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.

前端开发后端与接口
★ 3.2k
microsoft
microsoft/skills

microsoft-docs

Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.

Skill与智能体开发
★ 3.2k
microsoft
microsoft/skills

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).

Skill与智能体开发
★ 3.2k
microsoft
microsoft/skills

kql

KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: KQL, Kusto, ADX, Azure Data Explorer, Fabric Real-Time Intelligence, EventHouse, Log Analytics, log analysis, data exploration, time series, anomaly detection, summarize, where clause, join, extend, project, let statement, parse operator, extract function, any mention of pipe-forward query syntax.

数据分析师内容创作者写作与文案Skill与智能体开发
★ 3.2k