prism-syntax

I discovered your prism-syntax skill while evaluating syntax highlighting implementations, and the way you've structured the progressive disclosure around language detection is genuinely clever—feels like you anticipated exactly where developers would need the most flexibility.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 91/100, solid A-grade territory. This evaluation follows Anthropic's skill best practices rubric. Your strongest area is Utility (19/20)—the skill actually solves real problems—and your weakest is Spec Compliance (12/15), which is mostly about metadata discoverability. The core skill itself is genuinely well-built.

What's Working Well

• Progressive Disclosure Architecture is chef's kiss. Your SKILL.md stays lean at 79 lines, with three reference files picking up exactly the right level of detail. Developers can jump in immediately with the Quick Start, then dive deeper when needed.
• Examples are your secret weapon. Input/output pairs throughout, plus a complete 4-step Docusaurus integration template. That's the kind of thing that actually saves people hours.
• Token economy is tight. Every sentence serves a purpose. No fluff, no marketing speak—just "here's how to build a custom language for Prism" and you show them how.
• Utility hits hard (19/20). You're solving a real gap: custom language development in Prism.js isn't obvious, and you've got everything from basic patterns to Docusaurus integration to debugging tricks.

The Big One

Your trigger phrases are too sparse. You've got 1-2 in your description, but Claude works better with more discovery signals. Right now someone looking for "custom syntax highlighting" or "adding language support" might not find this.

The fix: Expand your descriptio...