Found your skill while auditing some TypeScript tooling—the strict mode enforcement is exactly what teams need when they're scaling up. Curious how you're handling the edge cases where strict mode butts heads with third-party libraries that weren't built for it?
Links:
The TL;DR
You're at 84/100, solid B territory. This is based on Anthropic's skill best practices. Your Progressive Disclosure Architecture is the strongest pillar (27/30)—the layering between SKILL.md and your two reference files is clean. Weakest spot is Spec Compliance (12/15), mainly because your description doesn't spell out the specific problems you're solving.
What's Working Well
- Progressive Disclosure is tight. You've got the main skill file handling Quick Start and Core Principles, then references/type-guards.md and references/generics.md handling deeper patterns. That layering is exactly what you want for token efficiency.
- Your examples are practical. The code samples show real input/output patterns and actually solve problems developers face—not abstract toy code.
- Trigger phrases are solid. "writing TypeScript" and "strict mode" activate appropriately when someone needs this. The generics and type guards coverage is exactly what people hit when enforcing strictness.
The Big One: Missing Problem Clarity in Your Description
Your description talks features ("covers type definitions, generics, and declaration files") instead of problems ("helps teams enforce null safety, prevent implicit any errors, and handle complex generic constraints"). Right now someone skimming the marketplace might not immediately connect "this is what I need" because the pain points aren't explicit.
Fix: Rewrite your description to lead with problems:
"Guides enforcing TypeScript strict mode across codebases—handles null/undefined safety, implicit any errors, generic constraints, and type guard patterns that teams struggle with when scaling up."
This is a +2 point swing and makes discoverability way better.
Other Things Worth Fixing
-
Add TOCs to your reference files. Both generics.md and type-guards.md are 80+ lines but start cold with ## headers. Add a Contents section at the top so people can jump to what they need. Low lift, +1 point.
-
Your Common Patterns section (lines 68-73) needs workflow steps. Right now it's a bullet list of guidelines. Make it actionable: "1. Enable strict mode in tsconfig.json, 2. Run tsc --noEmit to surface all errors, 3. Fix null/undefined errors first, 4. Add type guards for unions." +1 point.
-
Add a Validation section. Show how to verify strict mode compliance: "Run tsc --noEmit --strict and check --noImplicitAny output." This gives people a feedback loop to know they're done. +1 point.
Quick Wins
- Rewrite description for problem clarity (+2 points) — biggest bang for buck
- Add TOCs to reference files (+1 point) — 5 minutes
- Add numbered workflow steps (+1 point) — clarifies Common Patterns
- Add validation steps (+1 point) — completes the user journey
These four fixes alone get you to 90+ and solidly into A territory.
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.
Found your skill while auditing some TypeScript tooling—the strict mode enforcement is exactly what teams need when they're scaling up. Curious how you're handling the edge cases where strict mode butts heads with third-party libraries that weren't built for it?
Links:
The TL;DR
You're at 84/100, solid B territory. This is based on Anthropic's skill best practices. Your Progressive Disclosure Architecture is the strongest pillar (27/30)—the layering between SKILL.md and your two reference files is clean. Weakest spot is Spec Compliance (12/15), mainly because your description doesn't spell out the specific problems you're solving.
What's Working Well
The Big One: Missing Problem Clarity in Your Description
Your description talks features ("covers type definitions, generics, and declaration files") instead of problems ("helps teams enforce null safety, prevent implicit any errors, and handle complex generic constraints"). Right now someone skimming the marketplace might not immediately connect "this is what I need" because the pain points aren't explicit.
Fix: Rewrite your description to lead with problems:
This is a +2 point swing and makes discoverability way better.
Other Things Worth Fixing
Add TOCs to your reference files. Both generics.md and type-guards.md are 80+ lines but start cold with ## headers. Add a Contents section at the top so people can jump to what they need. Low lift, +1 point.
Your Common Patterns section (lines 68-73) needs workflow steps. Right now it's a bullet list of guidelines. Make it actionable: "1. Enable strict mode in tsconfig.json, 2. Run tsc --noEmit to surface all errors, 3. Fix null/undefined errors first, 4. Add type guards for unions." +1 point.
Add a Validation section. Show how to verify strict mode compliance: "Run
tsc --noEmit --strictand check --noImplicitAny output." This gives people a feedback loop to know they're done. +1 point.Quick Wins
These four fixes alone get you to 90+ and solidly into A territory.
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.