CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-templates/docs-page/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured single-purpose skill that is concrete and actionable throughout, with a solid self-check validation step. It is slightly above the simple-skill line count and could add an explicit error-recovery loop, but otherwise earns its tokens.

Suggestions

Add a brief 'if a self-check fails, fix and re-run' feedback loop after Step 6 to strengthen workflow_clarity toward a 5.

Confirm the body stays near the simple-skill size threshold so progressive_disclosure can fully benefit from the simple-skill exception.

DimensionReasoningScore

Conciseness

Dense with actionable specifics (px ranges, max-width, 350-word minimum, named logical CSS properties) and assumes Claude's competence about HTML/CSS Grid/RTL, with only minor tightening possible.

4 / 5

Actionability

Provides concrete, executable guidance—specific element requirements (shell command, 5–15 line snippet, callout, table), named CSS properties, and an exact artifact format—matching an instruction skill with highly specific direction.

4 / 5

Workflow Clarity

A clear six-step sequence with a Self-check validation checkpoint containing concrete pass criteria; no explicit error-recovery loop, but the artifact is non-destructive so the cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into Workflow and Output-contract sections and fully self-contained with no bundle files to navigate, though it sits just over the simple-skill line count.

4 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit 'Use when' clause and good trigger-term coverage. It could name more concrete actions (e.g., producing a single HTML file, applying the design system) rather than only listing layout regions.

Suggestions

Add a concrete action verb such as 'Produce a single HTML file' to the description so the deliverable format is explicit.

Mention design-system application in the description to round out the 'what' beyond layout regions.

DimensionReasoningScore

Specificity

Names the domain ('documentation page') and three concrete regions (inline-start nav, scrollable article body, inline-end TOC), but lists structural components rather than a comprehensive set of actions and omits that it produces HTML.

3 / 5

Completeness

Explicitly answers both what (three-region documentation page) and when ('Use when the brief mentions...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Five natural English trigger terms ('docs', 'documentation', 'guide', 'API reference', 'tutorial') plus the Chinese '文档' give good coverage, though a few natural synonyms and file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

The three-column docs layout with specific triggers carves a distinct niche, with only minor overlap risk against general page-generation skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.