typescript-strict

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:

• GitHub
• Your agentic skill in the SkillzWave marketplace

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:

...