ux-researcher-designer
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.
79
59%
Does it follow best practices?
Impact
90%
1.15xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./product-team/ux-researcher-designer/SKILL.mdQuality
Discovery
77%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description does a solid job listing specific UX research capabilities and includes an explicit 'Use for...' clause, making it functional for skill selection. However, the trigger terms in the 'Use for' clause largely repeat the capability list rather than expanding coverage with natural user language variations. The inclusion of the job title 'Senior UX Designer/Researcher' is unnecessary and doesn't aid in skill matching.
Suggestions
Expand trigger terms to include more natural user language variations such as 'user interviews', 'wireframes', 'user flows', 'heuristic evaluation', 'UX audit', or 'prototype testing'.
Remove the role descriptor 'Senior UX Designer/Researcher' as it describes the user rather than helping Claude distinguish when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis.' These are distinct, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis') and when ('Use for user research, persona creation, journey mapping, and design validation'), with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'user research', 'persona creation', 'journey mapping', 'design validation', and 'usability testing', but misses common variations users might say such as 'user interviews', 'wireframes', 'UX audit', 'user flows', 'heuristic evaluation', or 'A/B testing'. | 2 / 3 |
Distinctiveness Conflict Risk | The UX research domain is fairly specific, but terms like 'design validation' and 'research synthesis' could overlap with general design or data analysis skills. The mention of 'Senior UX Designer/Researcher' as a role is unusual and doesn't help with distinctiveness—it describes the user rather than narrowing the skill's niche. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured with good progressive disclosure and clear workflow organization, but suffers significantly from verbosity — it teaches Claude UX methodology that it already knows (severity scales, interview question types, research method selection) rather than focusing on tool-specific instructions and project-specific conventions. The actionability is moderate since only the persona_generator.py script provides truly novel executable guidance; the remaining workflows are methodology descriptions rather than concrete tool usage.
Suggestions
Cut the Quick Reference Tables section entirely — Claude already knows UX research methods, severity scales, interview question types, and confidence levels. This alone would save ~60 lines.
Remove the Trigger Terms section — these are generic UX phrases that don't add value and waste tokens.
Integrate the Validation Checklists directly into each workflow as explicit checkpoint steps (e.g., 'Before proceeding, verify: [checklist]') to create proper feedback loops.
Focus content on what's unique to this project: the persona_generator.py tool usage, specific file paths, team conventions, and project-specific data formats rather than general UX methodology.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It includes extensive reference tables (interview question types, severity scales, research method selection) that Claude already knows as a senior UX researcher would. The trigger terms section, detailed table of contents, and exhaustive tool output samples add significant token bloat without proportional value. | 1 / 3 |
Actionability | The workflows provide structured steps with concrete examples (JSON input format, task format templates, coding tags), but much of the guidance is methodological knowledge Claude already possesses rather than tool-specific executable instructions. The only truly executable element is the persona_generator.py script invocation; the rest is UX methodology description rather than concrete commands. | 2 / 3 |
Workflow Clarity | Each workflow has numbered steps with clear sequencing, but validation checkpoints are weak. Workflow 1 has a validation step (step 4) but it's manual and vague ('show to 3-5 real users'). Workflows 2-4 lack explicit validation/feedback loops — there's no 'if this fails, do X' guidance. The validation checklists at the end are disconnected from the workflows themselves. | 2 / 3 |
Progressive Disclosure | The skill appropriately references external files (persona-methodology.md, journey-mapping-guide.md, usability-testing-frameworks.md, example-personas.md) at one level deep with clear signaling. The knowledge base section provides a clean navigation table. Content is split between overview workflows and detailed references. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- alirezarezvani/claude-skills
- Commit
f567c61
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.