CtrlK
BlogDocsLog inGet started
Tessl Logo

docusaurus-config

Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration. Triggers on tasks involving docusaurus.config.js, docusaurus.config.ts, site configuration, URL formats, presets, or theme config.

65

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/docusaurus-config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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, concise skill that provides a solid config template and clear core principles. Its main weaknesses are in actionability (the common tasks section is too vague) and workflow clarity (no explicit validation commands or feedback loops for config changes). The referenced detailed guide is missing from the bundle, limiting the progressive disclosure score.

Suggestions

Add concrete validation steps to the workflow, e.g., 'Run `npx docusaurus build` to verify config is valid' after editing, with error recovery guidance.

Make 'Common Tasks' actionable by showing specific code snippets for common modifications (e.g., adding a plugin, configuring navbar, setting up i18n) or move these to the referenced detailed guide and clarify what it contains.

Provide the referenced 'references/detailed-guide.md' bundle file, or remove the reference if it doesn't exist.

DimensionReasoningScore

Conciseness

The content is lean and efficient. Every section serves a purpose, no concepts are over-explained, and Claude's intelligence is respected throughout. The bullet points are terse and informative.

3 / 3

Actionability

The TypeScript config example is concrete and copy-paste ready, but the 'Common Tasks' section is vague ('Read current config to preserve format', 'Verify required fields') without showing how. The plugin/theme format mention lacks a concrete example.

2 / 3

Workflow Clarity

There's a before/after editing pattern mentioned, but it lacks explicit validation steps or commands. For config editing (which can break a site), there should be a clearer sequence with verification, e.g., running a build or validation command to confirm the config is valid.

2 / 3

Progressive Disclosure

The skill references 'references/detailed-guide.md' for comprehensive examples, which is good structure. However, no bundle files were provided, meaning the referenced file doesn't exist, and the overview itself could benefit from slightly more signposting about what the detailed guide covers.

2 / 3

Total

9

/

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-structured description with excellent trigger terms and clear 'when' guidance. Its main weakness is that the 'what' portion is somewhat generic ('validate or modify') rather than listing specific concrete configuration actions. The niche focus on Docusaurus configuration files makes it highly distinctive.

Suggestions

Expand the capability description with more specific actions, e.g., 'validate configuration structure, update base URLs, configure plugins, modify navbar/footer settings, set up presets and theme config'.

DimensionReasoningScore

Specificity

The description mentions 'validate or modify Docusaurus configuration' which names the domain and two actions, but doesn't list specific concrete actions like 'update URL formats, configure presets, modify theme settings, add plugins'.

2 / 3

Completeness

Clearly answers both 'what' (validate or modify Docusaurus configuration) and 'when' with an explicit 'Use when...' clause and a 'Triggers on...' clause listing specific trigger conditions.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'docusaurus.config.js', 'docusaurus.config.ts', 'site configuration', 'URL formats', 'presets', 'theme config'. These cover both file names and conceptual terms users would naturally mention.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a very specific tool (Docusaurus) and specific config files (docusaurus.config.js/ts). Unlikely to conflict with other skills unless there are multiple Docusaurus-related skills.

3 / 3

Total

11

/

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.

Repository
mcclowes/skills-docusaurus
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.