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 Page Writer

by microsoft in microsoft/skills

Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

OfficialMITAuto-check passedDevelopment

Install Wiki Page Writer

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

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

GitHub CLI
$ gh skill install microsoft/skills wiki-page-writer --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-page-writer .claude/skills/wiki-page-writer && 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-page-writer
GitHub stars
3.1k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
616 words
Files
1
Skills in repo
150
Repo updated
First seen
Licence
MIT

At a glance

Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

  • Works in 4 steps: Check for git remote: Run git remote… → Ask the user: "Is this a local-only… → Determine default branch: Run git… → …
  • Writing documentation
  • SKILL.md covers When to Activate, Source Repository Resolution…, Depth Requirements… and Procedure, plus 1 more section
  • Calls git

What it does

Wiki Page Writer is an agent skill from microsoft/skills, published by the product's own GitHub organization. Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.

Its SKILL.md is about 1.5k 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 Development, covering Technical documentation, Citation management and Theming and dark mode. 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

  • Writing documentation
  • Generating wiki pages
  • Creating technical deep-dives
  • Documenting specific components

Example prompts

  • “Use the wiki-page-writer skill to generate rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and…”
  • “/wiki-page-writer”

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 Page Writer loads about 1.5k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 616 words of instructions outside code blocks.

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

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). 616 words, ~1,455 tokens.

Download SKILL.mdSave it as .claude/skills/wiki-page-writer/SKILL.md (or your agent's skills folder).
name
wiki-page-writer
description
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
license
MIT
metadata.author
Microsoft
metadata.version
1.0.0

Wiki Page Writer

You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.

When to Activate

  • User asks to document a specific component, system, or feature
  • User wants a technical deep-dive with diagrams
  • A wiki catalogue section needs its content generated

Source Repository Resolution (MUST DO FIRST)

Before generating any page, 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

Depth Requirements (NON-NEGOTIABLE)

  1. TRACE ACTUAL CODE PATHS — Do not guess from file names. Read the implementation.
  2. EVERY CLAIM NEEDS A SOURCE — File path + function/class name.
  3. DISTINGUISH FACT FROM INFERENCE — If you read the code, say so. If inferring, mark it.
  4. FIRST PRINCIPLES — Explain WHY something exists before WHAT it does.
  5. NO HAND-WAVING — Don't say "this likely handles..." — read the code.

Procedure

  1. Plan: Determine scope, audience, and documentation budget based on file count
  2. Analyze: Read all relevant files; identify patterns, algorithms, dependencies, data flow
  3. Write: Generate structured Markdown with diagrams and citations
  4. Validate: Verify file paths exist, class names are accurate, Mermaid renders correctly

Mandatory Requirements

VitePress Frontmatter

Every page must have:

---
title: "Page Title"
description: "One-line description"
---
Mermaid Diagrams
  • Minimum 3–5 per page (scaled by scope: small=3, medium=4, large=5+)
  • Use at least 2 different diagram types — don't repeat the same type. Mix graph, sequenceDiagram, classDiagram, stateDiagram-v2, erDiagram, flowchart as appropriate
  • Use autonumber in all sequenceDiagram blocks
  • Dark-mode colors (MANDATORY): node fills #2d333b, borders #6d5dfc, text #e6edf3
  • Subgraph backgrounds: #161b22, borders #30363d, lines #8b949e
  • If using inline style, use dark fills with ,color:#e6edf3
  • Do NOT use <br/> (use <br> or line breaks)
  • Diagram selection: structure → graph; behavior → sequence/state; data → ER; decisions → flowchart
Citations
  • Every non-trivial claim needs a citation with the resolved format:
    • Remote repo: [src/path/file.ts:42](REPO_URL/blob/BRANCH/src/path/file.ts#L42)
    • Local repo: (src/path/file.ts:42)
    • Line ranges: [src/path/file.ts:42-58](REPO_URL/blob/BRANCH/src/path/file.ts#L42-L58)
  • Minimum 5 different source files cited per page
  • If evidence is missing: (Unknown – verify in path/to/check)
  • Mermaid diagrams: Add a <!-- Sources: file_path:line, file_path:line --> comment block immediately after each diagram
  • Tables: Include a "Source" column with linked citations when listing components, APIs, or configurations
Show full SKILL.md (245 more words)Show less
Structure
  • Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References → Related Pages
  • Use tables aggressively — prefer tables over prose for any structured information (APIs, configs, components, comparisons)
  • Summary tables first: Start each major section with an at-a-glance summary table before details
  • Use comparison tables when introducing technologies or patterns — always compare side-by-side
  • Include a "Source" column with linked citations in tables listing code artifacts
  • Use bold for key terms, inline code for identifiers and paths
  • Include pseudocode in a familiar language when explaining complex code paths
  • Progressive disclosure: Start with the big picture, then drill into specifics — don't front-load details
Cross-References Between Wiki Pages
  • Inline links: When mentioning a concept, component, or pattern covered on another wiki page, link to it inline using relative Markdown links: [Component Name](../NN-section/page-name.md) or [Section Title](../NN-section/page-name.md#heading-anchor)
  • Related Pages section: End every page with a "Related Pages" section listing connected wiki pages:
    markdown
    ## Related Pages

| Page | Relationship |
|------|-------------|
| [Authentication](../02-architecture/authentication.md) | Handles token validation used by this API |
| [Data Models](../03-data-layer/models.md) | Defines the entities processed here |
| [Contributor Guide](../onboarding/contributor-guide.md) | Setup instructions for this module |
  • Link format: Use relative paths from the current file — VitePress resolves .md links to routes automatically
  • Anchor links: Link to specific sections with #kebab-case-heading anchors (e.g., [error handling](../02-architecture/overview.md#error-handling))
  • Bidirectional where possible: If page A links to page B, page B should link back to page A
VitePress Compatibility
  • Escape bare generics outside code fences: `List<T>` not bare List<T>
  • No <br/> in Mermaid blocks
  • All hex colors must be 3 or 6 digits

© 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-page-writer 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 Page Writer 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 Page Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wiki Page Writer this skillmicrosoft/skills3.1k1 repos~1.5kAutomated safety check: PassMIT
Wiki Page WriteraAAaqwq/AGI-Super-Team1052 repos~709Automated safety check: PassMIT
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Debate ReviewamElnagdy/review-skills1322 repos~986Automated safety check: PassMIT
Mermaid Diagramsjjmartres/opencode1336 repos~1.9kAutomated safety check: PassMIT
Acquire Codebase Knowledgegithub/awesome-copilot40k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Wiki Page Writer

    aAAaqwq/AGI-Super-Team

    Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

    105 GitHub starsUsed in 2 repos~709 tokens
    DevelopmentAuto-check passed

  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Debate Review

    amElnagdy/review-skills

    Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.

    132 GitHub starsUsed in 2 repos~986 tokens
    DevelopmentAuto-check passed

  • Mermaid Diagrams

    jjmartres/opencode

    Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.

    133 GitHub starsUsed in 6 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    DevelopmentAuto-check passed

  • Azdo Internal

    microsoft/aspire

    Official

    A skill your agent uses when asked to trigger or inspect Aspire internal Azure DevOps builds, source-index runs, or release validation on dnceng/internal; push to the internal mirror; download build…

    6.4k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-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 Page Writer

What does Wiki Page Writer do?

Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Wiki Page Writer is an agent skill from microsoft/skills, published by the product's own GitHub organization. Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

When should I use Wiki Page Writer?

Wiki Page Writer fits situations like: writing documentation; generating wiki pages; creating technical deep-dives; documenting specific components.

How do I install Wiki Page Writer in Claude Code?

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

How do I install Wiki Page Writer in Codex?

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

Can I use Wiki Page Writer 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-page-writer -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-page-writer, .gemini/skills/wiki-page-writer, .github/skills/wiki-page-writer and .opencode/skills/wiki-page-writer in your project.

What does Wiki Page Writer need to run?

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

Does Wiki Page Writer 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 Page Writer 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 Page Writer use?

Wiki Page Writer 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 Page Writer use?

About 1.5k tokens (SKILL.md is roughly 5.8k 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 Page Writer?

Skills that share tags, products or a category with Wiki Page Writer: Wiki Page Writer (aAAaqwq/AGI-Super-Team, 105 stars), Doc Sync (JetBrains/ideavim, 10k stars), Debate Review (amElnagdy/review-skills, 132 stars) and Mermaid Diagrams (jjmartres/opencode, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wiki Page Writer?

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.