CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ux-researcher-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized overview that correctly points to a real bundled script, but as an instructional document it is thin: only one of five claimed capabilities has any guidance, and that guidance misstates the script's CLI. The script is ultimately a library with a demo main(), which the SKILL.md never tells the user how to drive with real data.

Suggestions

Correct the usage line to reflect the actual CLI ('python scripts/persona_generator.py json' for JSON output on sample data) and document how to use real user data, e.g. importing PersonaGenerator and calling generate_persona_from_data(user_data, interview_insights).

Add a minimal example of the expected user_data JSON structure so the copy-paste path from data to persona is executable end-to-end.

Either add brief how-to guidance for journey mapping, usability testing, research synthesis, and design validation, or narrow the skill's scope to persona generation so the body matches what the bundle actually delivers.

DimensionReasoningScore

Conciseness

The ~27-line body is lean with terse bullet lists and zero padding — no explanations of concepts Claude already knows, matching 'lean and efficient; assumes Claude's competence; every token earns its place'. Not a 4 because there is no over-explanation to trim; the 'Core Capabilities' overview and script feature list are structural, not filler.

5 / 5

Actionability

One concrete runnable command is given ('python scripts/persona_generator.py [json]'), but the '[json]' argument is misleading — the script's CLI actually treats 'json' as an output-format flag and always runs on built-in sample data, accepting no user data file. Combined with zero executable guidance for four of the five claimed capabilities, this matches 'some concrete guidance but incomplete; missing key details'. Not a 4 because the gaps are major rather than minor (the documented usage misrepresents the actual CLI); not a 2 because a real, executable command and script do exist.

3 / 5

Workflow Clarity

The single documented action (run the persona script) is stated, but there is no workflow for preparing or supplying real user data (the script's Python API is never mentioned), and no sequence whatsoever for journey mapping, usability testing, research synthesis, or design validation — the skill is not single-purpose by its own claims, so the simple-skill exception does not apply. This fits 'steps listed but checkpoints missing or implicit' territory; not a 2 because the one documented action is concrete and unambiguous, and no destructive/batch operations require a validation cap.

3 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections ('Core Capabilities', 'Key Scripts') and a single one-level-deep, verified reference to scripts/persona_generator.py, which exists and matches its description — fitting both the 'clear overview with well-signaled one-level-deep references' anchor and the under-50-lines scoring note. Not a 4 because there is no misplaced inline content and no organization gap; nothing else in the bundle needs a separate reference file.

5 / 5

Total

16

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid description that explicitly covers both what the skill does and when to use it, with concrete capability names and natural trigger phrases in third-person voice. Main headroom is in the trigger clause, which repeats the capability list rather than adding varied user-mention triggers and leaves out usability testing.

Suggestions

Vary the 'Use for...' clause with user-mention style triggers (e.g., 'Use when the user mentions personas, journey maps, usability tests, or synthesizing interview findings') instead of repeating the capability list verbatim.

Add missing natural trigger terms such as 'usability testing' and 'UX research' to the when-clause so all core capabilities have a trigger keyword.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis' — which matches the anchor 'lists several specific actions; minor gaps in coverage'. It is not a 5 because 'usability testing frameworks' is a deliverable-style noun rather than a crisp action and coverage of the domain's actions is not fully comprehensive; it is well above a 3 (which expects only 1-2 concrete actions).

4 / 5

Completeness

Both 'what' (toolkit including persona generation, journey mapping, usability testing frameworks, research synthesis) and 'when' ('Use for user research, persona creation, journey mapping, and design validation') are explicitly present, satisfying the 'Use when...' requirement. It falls short of a 5 because the when-clause largely mirrors the what-clause instead of adding distinct trigger contexts, and omits 'usability testing' from the triggers; it clearly exceeds a 3, where 'when' would be missing or only weakly implied.

4 / 5

Trigger Term Quality

The trigger clause 'Use for user research, persona creation, journey mapping, and design validation' contains natural phrases a user would say, matching 'good keyword coverage; a few natural terms missing'. Not a 5 because common variants like 'usability testing', 'UX research', 'user interviews', or 'customer journey' are absent; not a 3 because coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — 'UX research and design toolkit for Senior UX Designer/Researcher' — with domain-specific triggers, matching 'mostly distinct; minor overlap risk with closely related skills'. Not a 5 because broad terms like 'design validation' and 'research synthesis' create some overlap risk with general product-design or research skills; not a 3 because it is far more specific than a generic 'works with document files' style description.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

maslennikov-ig/claude-code-orchestrator-kit

Path

.claude/skills/ux-researcher-designer/SKILL.md

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.