wiki-page-writer

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is dense, directive, and actionable with a clear gated workflow, but it front-loads reference-grade formatting detail inline and fails to signal the existing acceptance-criteria.md reference file, weakening progressive disclosure.

Suggestions

Link references/acceptance-criteria.md from the body (e.g., under a 'Examples' or 'Acceptance criteria' section) so the bundled reference is discoverable and one level deep.

Move the detailed Mermaid color palette, citation-format variants, and cross-reference link syntax into a reference file, keeping SKILL.md as an overview that points to them.

Make the Validate step concrete with a specific check (e.g., a command or explicit checklist) rather than 'Verify file paths exist, class names are accurate'.

Dimension	Reasoning	Score
Conciseness	Mostly lean directive prose with concrete specs (hex colors, citation formats), but the repeated ALL-CAPS emphasis ('NON-NEGOTIABLE', 'MUST DO FIRST', 'Do NOT proceed') and some overlap between 'Depth Requirements' and 'Mandatory Requirements' add tokens that could be trimmed.	4 / 5
Actionability	Provides concrete executable commands ('git remote get-url origin', 'git rev-parse --abbrev-ref HEAD') and copy-paste-ready format templates (frontmatter, citation syntax, Mermaid colors), though there is no full end-to-end example page tying it together.	4 / 5
Workflow Clarity	A clear four-step Procedure (Plan, Analyze, Write, Validate) plus a gated Source Repository Resolution sequence with an explicit 'Do NOT proceed until... resolved' checkpoint; the Validate step is present but described qualitatively rather than as a concrete check command.	4 / 5
Progressive Disclosure	The body is well-sectioned but inlines substantial reference-style detail (color palettes, citation format variants, cross-reference link syntax, VitePress compat rules) that belongs in a separate file, and the existing references/acceptance-criteria.md is never linked or signaled from the body.	3 / 5
	Total	15 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capabilities and trigger conditions with natural user phrasing. Its only weakness is modest overlap risk with broader documentation skills and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth' — covering several distinct actions comprehensively, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both what (generates documentation pages with diagrams, citations, first-principles depth) and when ('Use when writing documentation, generating wiki pages, creating technical deep-dives...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage — 'writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems' — with useful synonyms, though a few common variations (e.g., 'API docs', 'README') are absent, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The dark-mode Mermaid + source-citation + first-principles niche is fairly distinct, but 'writing documentation' / 'documenting components' could overlap with general documentation skills, so minor overlap risk remains.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing, 3 deeper-than-1-level, 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: freightCognition/linehaulai-claude-marketplace
Path: plugins/deep-wiki/skills/wiki-page-writer/SKILL.md
Commit: 88571a6

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.