Skillzwave Logo
Skillzwave

docusaurus-glossary

1 stars
14
B

Use when working with docusaurus-plugin-glossary to configure, manage glossary terms, troubleshoot issues, and explain features

Also in: json

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/docusaurus-plugin-glossary/docusaurus-glossary
skilz install mcclowes/docusaurus-plugin-glossary/docusaurus-glossary --agent opencode
skilz install mcclowes/docusaurus-plugin-glossary/docusaurus-glossary --agent codex
skilz install mcclowes/docusaurus-plugin-glossary/docusaurus-glossary --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/docusaurus-plugin-glossary
2. Copy the agent skill directory:
cp -r docusaurus-plugin-glossary/.claude/skills/docusaurus-glossary ~/.claude/skills/
View on GitHub

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

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

mastering-github-cli

by SpillwaveSolutions

GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" com...

100
TECHgithub
Marketplace

mastering-github-cli

by SpillwaveSolutions

GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" com...

100
TECHgithub
Marketplace

signal-intel

by gtmagents

Use when consolidating intent, product usage, and third-party signals to prioritize ABM actions.

91
github
Marketplace

meal-prep-efficiency-guru

by sandraschi

Expert in batch cooking, meal planning, food storage, and efficient kitchen workflows

88
github
Marketplace

Agentic Skill Details

Owner
mcclowes (GitHub)
Repository
docusaurus-plugin-glossary
Stars
1
Type
Non-Technical
Meta-Domain
development
Primary Domain
github
Market Score
14
Agentic Skill Grades →

Agent Skill Grade

B
Score: 86/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
28/30
Ease of Use
23/25
Writing Style
9/10
Utility
19/20
Modifiers: -4

Areas to Improve

  • Missing TOC in configuration.md
  • Core Principles could be more concise
  • Lack of troubleshooting input/output 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 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 s...

Browse Category

More development Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?