I spotted your docusaurus-glossary skill while reviewing our grading pipeline, and the way you've approached glossary management as a first-class Docusaurus feature is clean—most projects treat it as an afterthought, but you've given it real structure.
Links:
The TL;DR
You're at 86/100, solidly in B territory. This is based on Anthropic's Claude Skills best practices. Your strongest area is Utility (19/20)—the skill actually solves real problems—but Spec Compliance (11/15) and Writing Style (9/10) are dragging you down a bit.
What's Working Well
- Utility is your ace card (19/20). You've identified a genuine gap: configuring and troubleshooting Docusaurus glossary plugins isn't straightforward, and you've built something that walks through both preset and manual config approaches. That's bang for your buck.
- Progressive Disclosure is tight (28/30). SKILL.md is only 81 lines—no fluff—and you've smartly pushed configuration, usage, and troubleshooting into separate reference files. That's exactly how these should work.
- Trigger phrases nail the discoverability. "configure", "manage", "troubleshoot"—these catch the right developer looking for Docusaurus glossary help.
The Big One: Missing Input/Output Examples in Troubleshooting
This is holding back your Utility score. Your troubleshooting section tells developers what to do but doesn't show what errors look like before they try your solution.
Current problem: Readers hit a glossary issue, find your troubleshooting guide, but can't tell which scenario matches their error.
The fix: Add concrete before/after examples to references/troubleshooting.md:
## Glossary terms not showing
**Example error output**:
- Glossary page renders empty, or
- "Failed to load glossary" in console, or
- No auto-linked terms appear in markdown
**Causes & solutions:**
- Verify `glossary/glossary.json` exists at `<siteDir>/glossary/glossary.json`
- Check console for load errors
- Restart Docusaurus dev server
This addition alone would bump Utility from 19→20 and show you're thinking like someone actually using this.
Other Things Worth Fixing
-
Add a table of contents to references/configuration.md (124 lines). Just link to section headers. +1 point toward PDA.
-
Tighten Core Principles in SKILL.md (lines 34-39). You're using 4 bullets to explain concepts that could be a single paragraph: "Auto-linking terms via preset with tooltips, single-source glossary JSON, component-based <GlossaryTerm /> for manual control, preset auto-configures remark plugin." Saves tokens, same info. +1 point toward Writing Style.
-
Add 1-2 more trigger phrases to the description (currently just "configure, manage, troubleshoot"). "docusaurus glossary setup", "auto-linking", or "glossary plugin config" would help more people find you.
Quick Wins
- Add troubleshooting error examples (+1 Utility)
- TOC in configuration.md (+1 PDA)
- Tighten Core Principles bullet list (+1 Writing)
- Expand description triggers (+discoverability)
These four moves get you from 86→89, solid A territory.
Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.
I spotted your docusaurus-glossary skill while reviewing our grading pipeline, and the way you've approached glossary management as a first-class Docusaurus feature is clean—most projects treat it as an afterthought, but you've given it real structure.
Links:
The TL;DR
You're at 86/100, solidly in B territory. This is based on Anthropic's Claude Skills best practices. Your strongest area is Utility (19/20)—the skill actually solves real problems—but Spec Compliance (11/15) and Writing Style (9/10) are dragging you down a bit.
What's Working Well
The Big One: Missing Input/Output Examples in Troubleshooting
This is holding back your Utility score. Your troubleshooting section tells developers what to do but doesn't show what errors look like before they try your solution.
Current problem: Readers hit a glossary issue, find your troubleshooting guide, but can't tell which scenario matches their error.
The fix: Add concrete before/after examples to
references/troubleshooting.md:This addition alone would bump Utility from 19→20 and show you're thinking like someone actually using this.
Other Things Worth Fixing
Add a table of contents to
references/configuration.md(124 lines). Just link to section headers. +1 point toward PDA.Tighten Core Principles in SKILL.md (lines 34-39). You're using 4 bullets to explain concepts that could be a single paragraph: "Auto-linking terms via preset with tooltips, single-source glossary JSON, component-based
<GlossaryTerm />for manual control, preset auto-configures remark plugin." Saves tokens, same info. +1 point toward Writing Style.Add 1-2 more trigger phrases to the description (currently just "configure, manage, troubleshoot"). "docusaurus glossary setup", "auto-linking", or "glossary plugin config" would help more people find you.
Quick Wins
These four moves get you from 86→89, solid A territory.
Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.