Localized reading guide
wiki-page-writerPurpose, usage and source
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.
Source retrieved:
- Source repository
- microsoft/skills
- SKILL.md
.github/plugins/deep-wiki/skills/wiki-page-writer/SKILL.md- Repository stars
- 3,157
- Repository updated
- 2026-10-31
- Categories
- Documents
- 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
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.
How the upstream workflow works
Procedure
Plan: Determine scope, audience, and documentation budget based on file count Analyze: Read all relevant files; identify patterns, algorithms, dependencies, data flow Write: Generate structured Markdown with diagrams and citations Validate: Verify file paths exist, class names are accurate, Mermaid renders correctly
Upstream passage · L39 ↗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
Upstream passage · L14 ↗Wiki Page Writer
You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.
Upstream passage · L10 ↗---
title: "Page Title"
description: "One-line description"
---Requirements and setup
Depth Requirements (NON-NEGOTIABLE)
TRACE ACTUAL CODE PATHS — Do not guess from file names. Read the implementation. EVERY CLAIM NEEDS A SOURCE — File path + function/class name.
Upstream passage · L31 ↗VitePress Compatibility
Escape bare generics outside code fences: List not bare List No in Mermaid blocks
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
- 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.
- 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.
- 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.
- 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.
Read further in the source
Related Skills
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.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
00d66a64919edca5bca2c673373444e36a4b5461- Source SHA-256
f1270ea4123116e846bf2dc7a53a9e396ed43d694cdb7be22b9a35da9a40feb6