I took a look at your mexican-cuisine-specialist skill and wanted to share some thoughts.
Links:
The TL;DR
You're at 85/100, solid B-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Writing Style (10/10 - really tight, no fluff), and your Progressive Disclosure Architecture is clean too (28/30). The main drag is Utility (12/20) - you've got the structure right, but there's not enough concrete material for developers to actually use.
What's Working Well
- Writing is pristine. Imperative voice, purely instructional, no marketing BS. That's harder than it looks.
- Modular structure is solid. SKILL.md points to modules, _toc.md provides the roadmap. That's the right pattern.
- Navigation is clear. Good headers, numbered steps, research checklist to validate guidance. The workflow reads well.
The Big One: Low Confidence Legacy Status
Here's what's tanking your utility score: Your skill is flagged as "Low Confidence — Legacy template awaiting research upgrade" in the status section. This is a hard blocker. Developers won't trust a skill that admits it needs research work before use.
The fix: Go through your research checklist in modules/research-checklist.md, validate your Mexican cuisine guidance against reliable sources, and upgrade that confidence status to "Medium" or "High" with specifics about what you've validated. This single change could pull you up +4 points.
Other Things Worth Fixing
-
Add trigger phrases to your description. Right now it's "Authentic Mexican cooking expert covering moles, salsas, tacos..." - no "Use when..." language. Rewrite it: "Performs mexican cuisine specialist operations. Use when asked to 'mexican cuisine specialist', 'run mexican cuisine specialist', or 'mexican cuisine specialist help'." That's a quick +2 points and improves discoverability.
-
Zero examples or templates. Your modules have general guidance, but no concrete input/output pairs. Add a few: "Q: How do I make chile relleno? A: [specific steps]" - shows developers exactly how to interact with this skill. Could add +3 points.
-
Proprietary license might be limiting. Consider switching to MIT or Apache 2.0 for better alignment with open skill conventions. Small lift, +2 points.
Quick Wins
- Upgrade confidence status (research-backed) → +4 points
- Add trigger phrases to description → +2 points
- Add 2-3 concrete examples/templates → +3 points
- Swap to open license → +2 points
That's +11 points for a clean 96/100 if you prioritize these. Focus on the confidence upgrade first—that's the credibility blocker.
Checkout your skill here: SkillzWave.ai | SpillWave 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 took a look at your mexican-cuisine-specialist skill and wanted to share some thoughts.
Links:
The TL;DR
You're at 85/100, solid B-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Writing Style (10/10 - really tight, no fluff), and your Progressive Disclosure Architecture is clean too (28/30). The main drag is Utility (12/20) - you've got the structure right, but there's not enough concrete material for developers to actually use.
What's Working Well
The Big One: Low Confidence Legacy Status
Here's what's tanking your utility score: Your skill is flagged as "Low Confidence — Legacy template awaiting research upgrade" in the status section. This is a hard blocker. Developers won't trust a skill that admits it needs research work before use.
The fix: Go through your research checklist in
modules/research-checklist.md, validate your Mexican cuisine guidance against reliable sources, and upgrade that confidence status to "Medium" or "High" with specifics about what you've validated. This single change could pull you up +4 points.Other Things Worth Fixing
Add trigger phrases to your description. Right now it's
"Authentic Mexican cooking expert covering moles, salsas, tacos..."- no "Use when..." language. Rewrite it:"Performs mexican cuisine specialist operations. Use when asked to 'mexican cuisine specialist', 'run mexican cuisine specialist', or 'mexican cuisine specialist help'."That's a quick +2 points and improves discoverability.Zero examples or templates. Your modules have general guidance, but no concrete input/output pairs. Add a few: "Q: How do I make chile relleno? A: [specific steps]" - shows developers exactly how to interact with this skill. Could add +3 points.
Proprietary license might be limiting. Consider switching to MIT or Apache 2.0 for better alignment with open skill conventions. Small lift, +2 points.
Quick Wins
That's +11 points for a clean 96/100 if you prioritize these. Focus on the confidence upgrade first—that's the credibility blocker.
Checkout your skill here: SkillzWave.ai | SpillWave 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.