cs-ux-researcher

UX research agent for research planning, persona generation, journey mapping, and usability test analysis. Use when product decisions need user evidence — e.g., planning interview scripts and recruiting criteria for a discovery study, or synthesizing usability-test sessions into prioritized findings and updated personas.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-ux-researcher/SKILL.md

Quality

Content

53%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.

The content is well-structured and highly actionable, with executable commands and clear per-workflow sequencing. Its main weaknesses are verbosity (heavy path repetition and explanation of familiar concepts) and missing validation/verification checkpoints around batch interview processing and the opportunity-prioritization step.

Suggestions

Tighten the body: collapse the repeated long relative paths into a short variables/aliases section or table, and trim explanations of concepts Claude already knows (persona definitions, basic interview-analysis flow).

Add explicit validation checkpoints to batch workflows — e.g., verify each transcript was analyzed before aggregation, and confirm the journey-opportunities CSV exists/imports before running the prioritizer, with a fix-and-retry loop on failure.

Move the detailed workflow walkthroughs and integration-example scripts into reference files under references/ or assets/ so SKILL.md serves as a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The ~500-line body restates concepts Claude already knows (e.g., what personas are, basic interview-analysis steps) and repeats the same long relative paths verbatim dozens of times across workflows and examples, making it noticeably padded.	2 / 5
Actionability	Workflows contain concrete, executable commands (e.g., 'python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt') with mostly complete invocations, though some rely on external scripts whose presence is assumed.	4 / 5
Workflow Clarity	Steps are clearly sequenced per workflow, but batch operations (looping over many interview transcripts, regenerating personas) and the journey-opportunities CSV overwrite include no validation or verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	Structure is clear with well-labeled sections and one-level-deep references to external skill files, but no local bundle files exist and all workflow detail is inlined in the monolithic SKILL.md rather than split into dedicated files.	4 / 5
	Total	13 / 20 Passed

Description

83%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.

The description is strong: it states concrete capabilities and provides an explicit 'Use when...' clause with realistic trigger examples, satisfying both the what and when requirements. It is written in third person and stays largely free of fluff, with only minor gaps in keyword coverage and a slight overlap risk with adjacent product skills.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete capabilities ('research planning, persona generation, journey mapping, and usability test analysis'), with minor gaps in coverage rather than full enumeration of every action.	4 / 5
Completeness	Explicitly answers both what ('UX research agent for research planning, persona generation, journey mapping, and usability test analysis') and when ('Use when product decisions need user evidence — e.g., ...') with concrete trigger examples.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing users would say ('planning interview scripts and recruiting criteria', 'synthesizing usability-test sessions'), though a few common synonyms (e.g., 'user interviews', 'usability testing') are lightly covered rather than exhaustively.	4 / 5
Distinctiveness Conflict Risk	The UX-research niche is clear and unlikely to trigger for unrelated skills, but the orchestration framing ('product decisions need user evidence') creates minor overlap risk with a general product-manager agent.	4 / 5
	Total	17 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (532 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 8 suspicious	Warning

	Total	13 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/cs-ux-researcher/SKILL.md
Commit: 19392f7

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

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.