Skillzwave Logo
Skillzwave

docusaurus-plugin-dev

1 stars
14
B

Helps develop and build Docusaurus plugins using this starter template

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

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

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

exec-briefing

by gtmagents

Use to craft concise executive updates, agendas, and follow-up logs for QBR/EBR sessions.

93
ci cd
Marketplace

makefile-review

by athola

Audit Makefiles for duplication, portability, and idiomatic GNU Make usage.Triggers: Makefile review, build system, GNU Make, portability, deduplic...

80
TECHci cd
Marketplace

build-assistant

by vanman2024

Build Claude Code framework components (agents, slash commands, skills, plugins) following standardized templates. Use when creating new agents, co...

74
TECHci cd
Marketplace

astro-patterns

by vanman2024

Astro best practices, routing patterns, component architecture, and static site generation techniques. Use when building Astro websites, setting up...

63
TECHci cd
Marketplace

Agentic Skill Details

Owner
mcclowes (GitHub)
Repository
docusaurus-plugin-cookie-consent
Stars
1
Type
Technical
Meta-Domain
development
Primary Domain
ci cd
Market Score
14
Agentic Skill Grades →

Agent Skill Grade

B
Score: 83/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
26/30
Ease of Use
22/25
Writing Style
10/10
Utility
18/20
Modifiers: -4

Areas to Improve

  • Description needs trigger phrases
  • Missing TOC in reference file
  • Missing explicit trigger terms

Recommendations

  • Address 1 high-severity issues first
  • 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 poking around Docusaurus plugin development, and your skill caught my attention—the way you've structured the progressive disclosure for something as API-heavy as plugin architecture is genuinely thoughtful.

Links:

The TL;DR

You're at 83/100, solid B territory. This is graded against Anthropic's best practices for agentic skills. Your writing is pristine (10/10), but you're leaving points on the table with missing trigger phrases and some navigation gaps. The skill has real utility for plugin developers—your lifecycle hook patterns and SSR safety guidelines are genuinely useful—but discoverability and spec compliance could use some tightening.

What's Working Well

  • Writing style is chef's kiss (10/10) — Pure imperative voice throughout, zero fluff, appropriate density for Claude-level users. Lines like "Always check ExecutionEnvironment.canUseDOM" are exactly the right tone.
  • Progressive disclosure structure (26/30) — Moving the 359-line reference guide to client-modules-guide.md while keeping SKILL.md as a concise 110-line overview is solid layering. Users get the quick patterns first, then deep dives on demand.
  • Problem-solving power (7/8) — You're addressing real gaps: SSR safety, DOM enhancement patterns, lifecycle hook timing. The validate→doctor→validate LLM workflow is a nice touch that shows you've thought about feedback loops.
  • Terminology consistency — "client modules," "getClientModules()," "onRouteUpdate"—stays locked in throughout. Makes it easy to reference back.

The Big One: Missing Trigger Phrases

Your description needs explicit "Use when" language. Right now it says:

"Helps develop and build Docusaurus plugin...

Browse Category

More development Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?