docusaurus-config

3 stars
16
A

Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mcclowes/lea/docusaurus-config
skilz install mcclowes/lea/docusaurus-config --agent opencode
skilz install mcclowes/lea/docusaurus-config --agent codex
skilz install mcclowes/lea/docusaurus-config --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mcclowes/lea
2. Copy the agent skill directory:
cp -r lea/.claude/skills/docusaurus-config ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Repository
lea
Stars
3
Type
Non-Technical
Meta-Domain
productivity
Primary Domain
json
Market Score
16

Agent Skill Grade

A
Score: 90/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
26/30
Ease of Use
23/25
Writing Style
9/10
Utility
19/20
Modifiers: +1

Areas to Improve

  • Missing TOC in detailed-guide.md
  • Second-person pronouns in reference
  • Missing before/after examples

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

I've been looking at how people handle Docusaurus configuration lately, and your skill's approach to making it accessible is pretty solid—curious what drove you to focus on the configuration layer specifically rather than plugin development?

Links:

The TL;DR

You're at 90/100, firmly in A territory. This is solid work based on Anthropic's skill best practices. Your strongest area is Utility (19/20)—real problem-solving power for config validation. The weakest is Spec Compliance (12/15), mainly because you're light on trigger phrases and not using optional metadata fields that could boost discoverability.

What's Working Well

  • Progressive disclosure structure: You nailed the layered approach—SKILL.md stays tight and focused while references/detailed-guide.md goes deep. That's exactly how to respect token budgets while enabling exploration.
  • Utility hits the mark: The validation checklist and "restart dev server" feedback loop actually solve real problems developers face. You're not just documenting; you're preventing errors.
  • Metadata triggers are tight: "docusaurus.config.js/ts files" is specific and activates appropriately. Developers looking for config help will find this.

The Big One: Missing Table of Contents

Your detailed-guide.md is 315 lines but has no TOC. That's a navigation problem—when Claude's scanning through 300+ lines, a TOC cuts cognitive load and helps users jump to what they need.

Fix: Add a TOC right after the title:

## Table of Contents
- [Configuration File Structure](#configuration-file-structure)
- [Required Fields](#required-fields)
- [Themes Configuration](#themes-configuration)
- [Plugins](#plugins)
- [Custom Fields](#custom-fields)
- [Validation Checklist](#...

Report Security Issue

Found a security vulnerability in this agent skill?