docusaurus-plugins

Found a docusaurus-plugins skill that handles a pretty specific niche — extending Docusaurus with custom plugin architecture. The 87/100 score suggests solid execution, but I'm curious how you're handling plugin lifecycle and compatibility across Docusaurus versions.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 87/100, solid B-grade territory. This is based on Anthropic's skill best practices rubric. Your Writing Style nailed it at 10/10 — the skill uses perfect imperative voice with zero fluff, packed with technical substance. Utility scores 20/20 too, which means the skill genuinely solves a real problem (understanding 5 distinct plugin types). The weak spot is Spec Compliance at 12/15 — mostly because the description could use more trigger phrases for discoverability.

What's Working Well

• Progressive Disclosure is chef's kiss (28/30). You've got a lean 66-line SKILL.md that offloads everything to 6 focused reference files. That's exactly how this architecture should work.
• Trigger phrases actually work here — terms like 'remark', 'rehype', 'lifecycle' in your description activate naturally when someone needs to build a custom plugin. The description is specific enough that Claude will find this skill in the right context.
• Your examples have real teeth. The references include complete working code with input/output pairs. Someone can actually copy-paste and adapt, which is utility done right.
• Testing patterns baked in. References cover validation, debug logging, and AST explorers — you're not just showing "here's a plugin structure," you're showing "here's how to know it works."

The Big One: Missing Navigation in Large References

Your biggest lift is adding...