CtrlK
BlogDocsLog inGet started
Tessl Logo

product-research

Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.

67

Quality

81%

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

The canonical home for this skill is product-research in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is operationally strong with concrete commands and a clear sequenced workflow, but it is held back by repeated distinct-from content across three sections and by references to bundle files (scripts/, references/, assets/) that are not actually present. Tightening the redundancy and shipping the referenced files would lift the weaker dimensions.

Suggestions

Consolidate the distinct-from information: keep either the 'Do NOT use' bullet or the 'Distinct from' table, not both, since the description already states the distinctions — this directly tightens conciseness.

Provide the referenced bundle files (scripts/study_designer.py, scripts/saturation_planner.py, scripts/insight_synthesizer.py, references/*.md, assets/research_plan_template.md) so the signaled references resolve and navigation works — this is the main blocker for progressive_disclosure.

Trim the forcing-question library to the questions plus a one-line canon pointer each, dropping the 'Recommended' elaboration, to reduce padding without losing the grill discipline.

DimensionReasoningScore

Conciseness

Mostly efficient and operational, but the distinct-from information is repeated three ways (in the description, the 'Do NOT use' bullet, and the 'Distinct from' table) and the forcing-question library carries recommended-answer plus canon-citation padding per item, so it could be tightened — matching the score-3 anchor over the score-4 anchor which requires only minor trims.

3 / 5

Actionability

Provides concrete, flag-level CLI commands with example values ('study_designer.py --goal {discovery|evaluative|validation} --stage ... --profile ...', 'insight_synthesizer.py --input observations.json --min-sources 3') plus quick `--sample` examples; the minor gap is that the referenced scripts are not present in the bundle, so commands are not actually runnable as-is — matching score-4 rather than the fully-executable score-5.

4 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced with per-step commands and an explicit checkpoint in step 4 (treat ANECDOTE-flagged clusters as signals, not findings) and a redirect-honoring check in step 2; it falls short of score-5 only because there is no explicit validate→fix→retry feedback loop, fitting the score-4 anchor.

4 / 5

Progressive Disclosure

The body is well-sectioned and signals one-level-deep references (References list, Scripts table, assets/research_plan_template.md), but the references/, scripts/, and assets/ directories do not exist in the bundle, so the referenced paths are broken navigation — fitting the score-3 anchor (references present but navigation not actually usable) rather than score-4/5 which require working file structure.

3 / 5

Total

14

/

20

Passed

Description

100%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, opens with an explicit 'Use when' trigger, and explicitly distinguishes the skill from neighboring skills to avoid conflict. It is dense but every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation)', 'computing method-based saturation/sample size with an explicit confidence level', 'synthesizing coded observations into insights while flagging single-source anecdotes' — with comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Opens with an explicit 'Use when' trigger clause and states concrete 'what' actions (method selection, saturation sizing, insight synthesis), clearly and explicitly answering both what and when with trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Covers natural research terms a user would say — 'product/user research', 'generative interviews', 'usability test', 'concept test', 'saturation/sample size', 'confidence level', 'coded observations', 'insights', 'anecdotes' — including synonyms; no file extensions apply to this method skill, so the score-5 anchor fits.

5 / 5

Distinctiveness Conflict Risk

An explicit 'Distinct from' clause names neighbors — ux-researcher-designer, product-discovery, experiment-designer — and carves a clear 'research-ops method + insight-repository layer' niche, giving minimal conflict risk per the score-5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 13 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.