docusaurus-plugins

Use when creating Docusaurus plugins (remark, rehype, theme, content, lifecycle) to extend markdown, modify HTML, or add custom functionality. Triggers on tasks involving custom remark/rehype plugins, content plugins, theme plugins, or Docusaurus lifecycle hooks.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Critical

Do not install without reviewing

Quality

Content

87%

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

This is a well-structured skill that efficiently provides an actionable quick start and clear navigation to detailed reference files. Its main weakness is the lack of validation/verification steps—given that AST manipulation can silently produce incorrect output, a brief testing or verification step would strengthen the workflow. The progressive disclosure is exemplary with clear, descriptive links to topical reference files.

Suggestions

Add a brief validation/testing step (e.g., 'Test plugin: run `npx docusaurus build` and verify output in `build/` directory' or a quick AST inspection snippet) to provide a feedback loop for plugin development.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what Docusaurus is or how plugins work conceptually—it jumps straight to a working example and concise bullet points. The HTML comment at the bottom is meta-guidance for maintainers, not wasted tokens for Claude's consumption.	3 / 3
Actionability	The quick start provides a fully executable remark plugin with real code including the import, AST traversal, and config integration comment. The core principles section gives concrete, specific guidance about each plugin type and what functions/hooks to use.	3 / 3
Workflow Clarity	For a skill covering 5 plugin types with AST manipulation, there are no validation checkpoints or error recovery steps. The skill doesn't describe how to test or verify a plugin works correctly after creation, which is important for AST-manipulating operations that can silently produce incorrect output.	2 / 3
Progressive Disclosure	Excellent structure with a concise overview and well-signaled one-level-deep references to 6 specific reference files covering each plugin type and packaging. The main file stays focused as a quick reference while clearly directing to detailed guides.	3 / 3
	Total	11 / 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 well-crafted description that clearly identifies its niche (Docusaurus plugin development) and provides explicit trigger guidance. It covers both 'what' and 'when' effectively with good trigger term coverage. The main weakness is that the capability actions could be more concrete — listing specific operations like 'create custom MDX components, add syntax transformers, implement plugin lifecycle methods' would strengthen specificity.

Suggestions

Add more concrete action verbs and specific operations, e.g., 'create custom MDX transformers, implement swizzled theme components, add build lifecycle hooks' instead of the more generic 'extend markdown, modify HTML, add custom functionality'.

Dimension	Reasoning	Score
Specificity	Names the domain (Docusaurus plugins) and lists categories (remark, rehype, theme, content, lifecycle) with some actions ('extend markdown, modify HTML, add custom functionality'), but the actions are somewhat general rather than listing multiple concrete specific operations.	2 / 3
Completeness	Clearly answers both 'what' (creating Docusaurus plugins to extend markdown, modify HTML, add custom functionality) and 'when' with explicit trigger guidance ('Use when creating Docusaurus plugins... Triggers on tasks involving custom remark/rehype plugins, content plugins, theme plugins, or Docusaurus lifecycle hooks').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'Docusaurus plugins', 'remark', 'rehype', 'theme plugins', 'content plugins', 'lifecycle hooks', 'custom remark/rehype plugins'. These cover the key variations a developer would use when asking about this topic.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — Docusaurus plugin development is a clear niche. The specific mention of remark/rehype plugins, theme plugins, content plugins, and lifecycle hooks makes it very unlikely to conflict with general web development or other documentation framework 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 10 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.