nurture-testing

I've been digging into your testing skill and I'm curious why you chose the nurture-focused approach—that's a pretty different angle from most testing frameworks I see out there, but at a 64/100 there seem to be some gaps in how it's structured that might be limiting its reach.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 64/100, solidly in D-grade territory. This is based on Anthropic's skill best practices rubric across 5 pillars. Your strongest area is Spec Compliance (12/15)—the metadata and formatting are clean. But Progressive Disclosure Architecture is dragging you down hard at 15/30. The core issue is you've got good foundational content, but it's all crammed into 32 lines with no layering, no references directory, and no actual templates to back up what you're describing.

What's Working Well

• Solid spec compliance – Your YAML frontmatter is valid and the skill name follows hyphen-case conventions correctly
• Clear "When to Use" scenarios – You've got specific trigger phrases like "QA nurture campaigns" and "regression test nurture flows" that actually help with discoverability
• Consistent terminology – You stick with "nurture flows," "experiments," and "regression tests" throughout, which keeps things coherent
• Grep-friendly structure – The file is well-organized enough for basic searching (+1 modifier bonus)

The Big One: Missing Reference Files

Here's what's killing your PDA score: You mention Templates section with "Experiment brief + tracker," "QA matrix," and "Evidence archive folder structure," but then... nothing. No actual files. This violates the layered structure principle that makes skills token-efficient and useful.

Fix: Create a references/ su...