docusaurus-documentation

Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs. Triggers on tasks involving Docusaurus APIs, markdown features, configuration options, or best practices.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Critical

Do not install without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/docusaurus-documentation/SKILL.md

Quality

Content

50%

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

This skill provides a reasonable template for looking up Docusaurus documentation via WebFetch, with useful URL paths and a clear structure. However, it falls short on actionability by using placeholder code rather than a concrete executable example, and lacks error handling or fallback workflows when fetches fail. The referenced 'references/' directory has no supporting bundle files, weakening the progressive disclosure claim.

Suggestions

Replace the placeholder WebFetch code block with a fully concrete example (e.g., fetching the configuration page with a specific prompt), so Claude can copy-paste the pattern directly.

Add a brief fallback workflow: what to do if a URL returns an error or the content doesn't answer the question (e.g., try the main docs index, search for keywords).

Remove the HTML comment block at the end—it's meta-guidance for skill authors, not actionable content for Claude, and wastes tokens.

Either provide actual bundle files in references/ or remove the reference to avoid a broken link.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary guidance Claude would already know (e.g., 'start with the main docs page if you're unsure'). The HTML comment block at the end, while meta-guidance, adds tokens without value to the skill's execution.	2 / 3
Actionability	Provides a concrete WebFetch pattern with a code block, but the code uses placeholder brackets ([topic], [specific question]) rather than a fully executable example. The URL listings are helpful but the skill is more of a reference map than executable guidance.	2 / 3
Workflow Clarity	Steps are listed for looking up configuration and features, but there's no validation or feedback loop—e.g., what to do if a URL returns a 404 or the page doesn't contain the expected information. For a lookup skill this is less critical, but the fallback guidance ('start with the main docs page') is vague.	2 / 3
Progressive Disclosure	References a 'references/' directory for detailed documentation, which is good structure, but no bundle files are provided so the reference is unverifiable and potentially broken. The main file is reasonably organized with clear sections but the HTML comment block clutters the end.	2 / 3
	Total	8 / 12 Passed

Description

89%

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

This is a solid description with clear trigger guidance and good distinctiveness for the Docusaurus documentation domain. Its main weakness is that the 'what' portion is somewhat generic ('looking up information') rather than listing specific concrete actions like retrieving configuration examples, finding plugin APIs, or troubleshooting build issues. The trigger terms and completeness are strong.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'Retrieves Docusaurus plugin configurations, MDX syntax references, sidebar setup guides, and deployment instructions.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Docusaurus documentation) and mentions some areas like 'APIs, markdown features, configuration options, or best practices,' but does not list specific concrete actions (e.g., 'look up plugin configuration,' 'find MDX syntax examples'). It stays at a category level rather than enumerating distinct capabilities.	2 / 3
Completeness	Explicitly answers both 'what' (looking up information from Docusaurus documentation) and 'when' ('Use when looking up information... Triggers on tasks involving Docusaurus APIs, markdown features, configuration options, or best practices'). The 'Use when' and 'Triggers on' clauses are clearly present.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'Docusaurus,' 'documentation,' 'APIs,' 'markdown features,' 'configuration options,' 'best practices,' and the URL 'docusaurus.io/docs.' These are terms users would naturally use when asking about Docusaurus. Could benefit from mentioning 'MDX' or 'sidebar' but coverage is good.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — it targets a specific tool (Docusaurus) and a specific documentation source (docusaurus.io/docs). This is unlikely to conflict with other skills unless there are multiple Docusaurus-related skills.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mcclowes/skills-docusaurus
Commit: 343dcb2

Reviewed: about 7 hours 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.