docs-page

A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".

Quality

90%

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

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

An exemplary SKILL.md body: fully directive, quantified guidance with a copy-paste output contract and an explicit self-check validation step. The only minor gap is that the body sits slightly over the simple-skill line length with no offloaded reference material.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive throughout — "Pick a topic", "Lay out three regions", with hard numbers ("240–280px", "350 words", "5–15 lines") and zero explanation of concepts Claude already knows. Every line earns its place.	5 / 5
Actionability	Guidance is fully concrete and executable for the common case: exact pixel ranges, named CSS logical properties ("margin-inline-start", "inset-inline-end"), quantified prose requirements, and a copy-paste <artifact> output template. No pseudocode or vague direction.	5 / 5
Workflow Clarity	Steps 1–6 form a clear sequence ending in an explicit Self-check checklist (line length, mono token usage, accent restraint, responsive behavior). The operation is generative rather than destructive, so no error-recovery loop is required.	5 / 5
Progressive Disclosure	No bundle files exist, and the ~54-line body is well organized into Workflow and Output contract sections with no buried references. It falls just short of the simple-skill 5 threshold because the body slightly exceeds 50 lines and a few self-check details could plausibly live in a separate reference file.	4 / 5
	Total	19 / 20 Passed

Description

83%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: concrete structural specifics paired with an explicit 'Use when…' clause containing natural trigger terms. Both what and when are answered clearly, with only minor gaps in synonym coverage and slight overlap risk from broad terms like 'guide'.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete structural specifics ("inline-start nav, scrollable article body, inline-end table of contents") rather than generic language. It stops short of a 5 because it describes one artifact's parts rather than multiple discrete concrete actions with comprehensive coverage.	4 / 5
Completeness	It clearly answers both what ("A documentation page — inline-start nav, scrollable article body, inline-end table of contents") and when ("Use when the brief mentions 'docs', 'documentation', 'guide', 'API reference', or 'tutorial'") with explicit, concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Trigger terms "docs", "documentation", "guide", "API reference", "tutorial" are all natural phrases a user would say. A few common variations/synonyms (e.g., "manual", "readme", "spec") are missing, so it does not reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (a three-region docs-page layout artifact) with distinct triggers, but broadly applicable terms like "guide" and "tutorial" carry minor overlap risk with general writing or documentation-generation skills.	4 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: plugins/_official/examples/docs-page/SKILL.md
Commit: 1b47e60

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.