CtrlK
BlogDocsLog inGet started
Tessl Logo

user-research

Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

61

Quality

71%

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 ./design/skills/user-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-organized, token-efficient reference overview that assumes Claude's competence. Its weakness is actionability and workflow clarity: guidance stays at the framework level without concrete examples, templates, or quality checkpoints.

Suggestions

Add concrete examples such as sample interview questions or a survey-item template to make the guidance directly executable.

Surface an explicit end-to-end research workflow (plan -> recruit -> conduct -> synthesize -> report) with quality checkpoints like data saturation or member-checking.

Optionally link one-level-deep reference files for detailed artifacts (e.g., an interview-guide template) to deepen actionability without bloating SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean — tables and short bullet lists with no preamble explaining what user research is — though the opening line restates the description and a few items could be trimmed further.

4 / 5

Actionability

It gives structured guidance (timed interview sections, named frameworks, a deliverables list) but lacks concrete artifacts like sample interview questions, survey item types, or synthesis templates that would make it directly executable.

3 / 5

Workflow Clarity

The interview guide is a clear sequenced 5-step flow, but the overall research process (plan, conduct, synthesize) is only implied and lacks validation/quality checkpoints such as confirming饱和度 or reviewing findings.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and it is organized into clearly labeled sections, matching the simple-skill exception for a 5.

5 / 5

Total

15

/

20

Passed

Description

78%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 cleanly answers both what and when with multiple natural trigger phrases in third-person voice. It is slightly generic in its action verbs and has minor overlap risk with broader UX/product skills.

Suggestions

Expand the action list with more concrete capabilities (e.g., "recruit participants, write interview guides, run usability sessions, analyze themes") to lift specificity.

Add common synonyms such as "UX research" or "user testing" to broaden trigger coverage.

Tighten the niche boundary by contrasting with adjacent skills (e.g., specify it covers research, not design or analytics).

DimensionReasoningScore

Specificity

"Plan, conduct, and synthesize user research" names the domain and three actions, but they are high-level verbs rather than the comprehensive, concrete action list of the 4/5 anchors.

3 / 5

Completeness

It explicitly states what ("Plan, conduct, and synthesize user research") and when ("Trigger with ... or when the user needs help with any aspect of understanding their users"), with concrete trigger phrases matching the 5 anchor.

5 / 5

Trigger Term Quality

Five natural trigger phrases ("user research plan", "interview guide", "usability test", "survey design", "research questions") give good coverage, though common synonyms like "UX research" or "user testing" are absent.

4 / 5

Distinctiveness Conflict Risk

"User research" is a clear niche with specific triggers, but it has minor overlap risk with adjacent product/UX-design skills rather than the minimal conflict of the 5 anchor.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/knowledge-work-plugins
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.