Wiki Page Writer
Generates evidence-backed technical Wiki pages with source citations and deep Mermaid diagrams.
The skill requires repository-context resolution, distinguishes remote from local citations, and requires sourcing for non-trivial claims, providing some data-flow transparency and attribution. It does not specify sensitive-data handling, credential protection, confirmation boundaries, external-link risks, or rollback, so points are deducted.
The workflow and output requirements are fairly explicit, including path checks, Mermaid compatibility rules, and missing-evidence markers. However, it depends on git commands and user interaction without diagnosing failures such as missing remotes, invalid branches, or failed Mermaid validation; under static calibration it remains below 10.
Activation conditions cover component documentation, technical deep-dives, and wiki-page generation, so the main audience and scenarios are clear. Non-fit boundaries, precise input/output contracts, semantic exclusions, and Chinese-language support are not defined; mandatory remote citations may also be environment-sensitive, so points are deducted.
The SKILL.md has clear metadata, MIT licensing, a version, activation conditions, staged procedure, structural conventions, and compatibility constraints. It lacks a changelog, explicit maintenance owner or update path, installation notes, FAQs, and troubleshooting guidance, so points are deducted.
It gives concrete guidance for producing structured technical documentation with citations, diagrams, and progressive disclosure, so the core task is plausibly achievable. Mandatory minimum source-file and diagram counts may impose disproportionate cost, and no representative output or result verification is provided, so points are deducted.
The skill specifies file-path, function/class, and line citations and asks for path and Mermaid validation. The supplied material contains no skill-specific test suite, example output, or third-party execution evidence; the repository test evidence does not cover this skill's key paths, so points are deducted.
- Resolve repository provenance and default branch before proceeding; the skill lacks a clear recovery path when no remote exists or git commands fail.
- The minimum citation-file and diagram counts may over-engineer small documentation tasks.
- When using GitHub or Azure DevOps links, confirm accessibility and avoid exposing credentials or sensitive paths in citations.
- This assessment is static only; no commands, page generation, or Mermaid rendering were executed.
What does this skill do, and when should you use it?
Wiki Page Writer is a Microsoft Agent Skills skill for producing technical documentation, Wiki pages, and technical deep dives. It resolves source-repository context before writing, then analyzes relevant implementation files and traces actual code paths. Its required output format includes VitePress frontmatter, dark-mode Mermaid diagrams, file citations, structured tables, pseudocode, and cross-references. It fits engineering teams that need traceable documentation, but its workflow depends on repository context and access to the relevant files.
The skill first checks the Git remote and current branch, then asks whether the source is local-only or whether a remote repository URL is available. It plans the documentation scope, reads relevant implementation files, analyzes dependencies, algorithms, and data flow, and produces Markdown with VitePress frontmatter, 3–5 Mermaid diagrams, source citations, tables, pseudocode, and a Related Pages section. It then validates file paths, class names, and Mermaid syntax.
- An engineering team documenting a specific component or system in a reviewable technical Wiki page.
- A developer tracing implementation paths and data flow for a technical deep dive.
- A documentation maintainer adding Mermaid architecture diagrams and source citations to a VitePress site.
- A project team generating structured pages for a Wiki catalogue.
What are this skill's strengths and limitations?
- Requires repository and branch resolution before documentation begins, supporting traceable citations.
- Requires analysis of actual implementation paths instead of guessing from filenames.
- Defines concrete standards for VitePress frontmatter, dark-mode Mermaid diagrams, tables, pseudocode, and related-page links.
- Well suited to structured, progressively disclosed technical deep dives.
- It will not proceed until source-repository context is resolved.
- Each page requires citations from at least five different source files, which may be difficult for small or evidence-poor projects.
- The requirement for 3–5 Mermaid diagrams may be excessive for a simple documentation task.
- The supplied SKILL.md does not list dedicated scripts, a test suite, or client-specific compatibility validation.
- The repository README identifies the collection as a Work in Progress.
How do you install this skill?
The repository README documents collection installation with npx skills add microsoft/skills; select the required skills in the wizard. This skill is located at .github/plugins/deep-wiki/skills/wiki-page-writer/SKILL.md. The README also documents Copilot CLI plugin installation: /plugin marketplace add microsoft/skills, followed by /plugin install deep-wiki@skills. The source does not further document client-specific skill selection or loading steps.
How do you use this skill?
With the skill loaded, use a prompt such as “Generate a technical Wiki page for this component with Mermaid diagrams, source citations, and VitePress frontmatter.” The skill first requires source-repository context. A remote repository produces linked citations; a local-only repository produces local path citations.