CtrlK
BlogDocsLog inGet started
Tessl Logo

mcclowes/docusaurus-themes

Use when swizzling Docusaurus theme components and editing theme elements — wrap or eject components from @docusaurus/theme-classic, override navbar/footer/sidebar/TOC/DocItem, place customised components under src/theme/, and choose safe (--wrap) vs full (--eject) swizzles. Triggers on tasks involving Docusaurus swizzling, theme component customization, navbar, footer, sidebar, or layout modifications.

77

Quality

97%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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-crafted skill with strong actionability, clear workflow sequencing including validation and error recovery, and efficient use of tokens. The main weakness is that the referenced bundle files (references/commands.md and references/components.md) are not provided, so the progressive disclosure structure is aspirational rather than functional. Overall, the content is highly effective for guiding Claude through Docusaurus swizzling tasks.

Suggestions

Provide the referenced bundle files (references/commands.md and references/components.md) to make the progressive disclosure structure functional and complete.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what Docusaurus is or how npm works. Every section adds value — the only minor verbosity is the sentence explaining what swizzling does in the Workflow section, but it's brief and contextually useful for understanding why the workflow order matters.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands throughout — listing components, swizzling with wrap/eject, and building. The workflow gives specific commands at each step rather than abstract descriptions.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with an explicit validation step (step 5: `npm run build`) and a feedback loop ('if it errors, fix the swizzled component and re-run before moving on'). Step 4 includes a verification checkpoint for file placement. This covers the destructive-edit risk well.

3 / 3

Progressive Disclosure

References to `references/commands.md` and `references/components.md` are well-signaled and one level deep, which is good structure. However, no bundle files were provided, so these references point to non-existent files, undermining the actual progressive disclosure. The main content is appropriately concise for an overview.

2 / 3

Total

11

/

12

Passed

Description

100%

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 an excellent skill description that clearly defines its scope around Docusaurus theme swizzling with specific actions, relevant trigger terms, and explicit guidance on when to use it. It uses proper third-person voice throughout and covers both the 'what' and 'when' comprehensively. The highly specialized domain and terminology make it very distinctive among potential skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: swizzling theme components, wrapping or ejecting components from @docusaurus/theme-classic, overriding navbar/footer/sidebar/TOC/DocItem, placing components under src/theme/, and choosing between --wrap vs --eject swizzles.

3 / 3

Completeness

Clearly answers both 'what' (swizzle Docusaurus theme components, wrap/eject, override specific elements, place under src/theme/) and 'when' with an explicit trigger clause ('Triggers on tasks involving Docusaurus swizzling, theme component customization, navbar, footer, sidebar, or layout modifications').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Docusaurus', 'swizzling', 'theme component', 'navbar', 'footer', 'sidebar', 'TOC', 'DocItem', '--wrap', '--eject', 'layout modifications', '@docusaurus/theme-classic'. These cover the terms a developer working with Docusaurus theming would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a very specific niche (Docusaurus theme swizzling) with domain-specific terminology like '@docusaurus/theme-classic', '--wrap', '--eject', and 'src/theme/'. Unlikely to conflict with general web development or other documentation framework skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents