ux-researcher-designer

I notice you're tackling UX research and design as a skill—that's a territory where most tool-builders stay surface-level, so I'm curious how you're structuring the progression from research fundamentals to actual design decisions.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 64/100, solidly in D territory. This is based on Anthropic's 5-pillar framework. Your strongest area is Spec Compliance (12/15)—the frontmatter is clean and triggers are well-chosen. The real drag is Progressive Disclosure Architecture (13/30), where you're missing the layered reference structure that makes skills actually teachable.

What's Working Well

• Good trigger coverage: "user research", "persona creation", "journey mapping" will catch the right moments when Claude needs this skill
• Real working code: Your persona generator script actually produces output with confidence scoring, not just theoretical
• Correct YAML structure: No metadata issues, just straightforward and valid

The Big One: Missing Reference Architecture

Here's what's holding you back—SKILL.md is 300 words of overview, but the actual smarts are buried in a 150+ line Python script. Users have no guide for when to use what, or how the pieces fit together.

The fix: Create a references/ directory with layered docs:

• references/persona-methodology.md - detailed methodology (what makes a persona valid?)
• references/journey-mapping-guide.md - step-by-step journey mapping
• references/example-personas.md - 2-3 real output examples showing what "good" looks like

Then in SKILL.md, add a Research Workflow section with numbered steps that tie back to these docs. This alone buys you +6 points by fixing the PDA score.

##...