create-docs

Create complete documentation sites for projects. Use when asked to: "create docs", "add documentation", "setup docs site", "generate docs", "document my project", "write docs", "initialize documentation", "add a docs folder", "create a docs website". Generates Docus-based sites with search, dark mode, MCP server, and llms.txt integration.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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.

Highly actionable and well-structured, with concrete copy-paste-ready artifacts and sensible reference delegation. The main gap is the absence of an explicit validation/verification step in a batch file-generation workflow, which caps workflow clarity.

Suggestions

Add a validation checkpoint after Initialize/Generate, e.g. "Run [pm] install and [pm] run dev; confirm the site builds and serves at http://localhost:3000 before finalizing."

Move the theming/deployment and the auth-utils example into a reference file (e.g. references/deployment.md) to keep SKILL.md focused on the core workflow and improve progressive disclosure.

Collapse the default and i18n variants into a single template with an i18n addendum to reduce repetition.

Dimension	Reasoning	Score
Conciseness	The ~499-line body is almost entirely tables, directory trees, and code with no padding of concepts Claude already knows, though the dual default/i18n repetition and inlined theming/deployment/example offer minor trimming opportunities.	4 / 5
Actionability	Complete package.json, nuxt.config.ts, .gitignore, monorepo workspace configs, a correct/wrong MDC component table, and deployment commands give copy-paste-ready guidance covering the common cases.	5 / 5
Workflow Clarity	The 5-step Analyze→Initialize→Generate→Configure→Finalize sequence is well defined, but this multi-file batch operation has no explicit validation checkpoint (e.g., verify install/build/dev succeeds), capping it at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	Three real one-level-deep references (templates.md, writing-guide.md, mdc-components.md) are clearly signaled via links and the body delegates heavy template/writing/component material, though some setup content (theming, deployment, full example) is inlined.	4 / 5
	Total	16 / 20 Passed

Description

91%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 description that clearly states what the skill does and when to use it, with a rich set of natural trigger phrases. Minor overlap risk with generic documentation skills and a feature-leaning action list keep it just below perfect.

Dimension	Reasoning	Score
Specificity	"Create complete documentation sites" and "Generates Docus-based sites with search, dark mode, MCP server, and llms.txt integration" name several concrete capabilities, though they read more as a feature list than a comprehensive enumeration of distinct actions.	4 / 5
Completeness	It explicitly answers both what (create Docus-based sites with named features) and when ("Use when asked to:" followed by concrete trigger phrases).	5 / 5
Trigger Term Quality	Nine natural phrases a user would actually say ("create docs", "write docs", "document my project", "add a docs folder") give comprehensive synonym coverage of the intent.	5 / 5
Distinctiveness Conflict Risk	The Docus-specific niche and concrete triggers make it mostly distinct, but broad phrases like "add documentation" and "write docs" carry minor overlap risk with general doc/README skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nuxt-content/docus
Path: docs/skills/create-docs/SKILL.md
Commit: 5d75559

Reviewed: 3 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.