hypothesis-library

I've been diving into property-based testing frameworks lately, and your hypothesis-library skill caught my attention—though the 50/100 score suggests there might be some gaps between the concept and execution that are worth digging into.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

TL;DR

You're at 50/100, solidly in F grade territory. This is based on Anthropic's skill evaluation best practices across five pillars. Your Spec Compliance is actually solid (11/15)—the frontmatter is valid and naming conventions are right—but Progressive Disclosure Architecture (12/30) and Utility (8/20) are where you're losing the most points. The core issue: you've got a great framework concept, but it's missing the teeth to be actually useful.

What's Working Well

• Consistent terminology: You use 'hypothesis', 'learnings', and 'experiment' consistently throughout—no confusing terminology shifts that would make users stumble.
• Solid metadata schema thinking: The idea of using ID, theme, persona, funnel stage, and metrics is the right foundation for structured experimentation tracking.
• Logical section flow: "When to Use" → "Framework" → "Templates" → "Tips" follows a reasonable progression that's easy to scan.

The Big One: Missing Reference Files Kills Progressive Disclosure

Your skill lists three templates—intake form, learning card, portfolio dashboard—but provides zero actual content. This is a critical gap. You're telling users "here are templates" without showing them what they look like, which means they either guess or bounce.

The fix: Create three reference files:

• references/intake-form.md – actual template with example fields
• references/learning-card.md – structured format showing context/...