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.

52

Quality

56%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./design/skills/user-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

This skill reads more like a reference card or cheat sheet than actionable guidance for Claude. It lists categories and frameworks Claude already knows without providing the concrete templates, example outputs, or step-by-step workflows needed to actually produce research artifacts. The lack of executable examples (e.g., a sample research plan, example interview questions, a synthesis template) severely limits its utility.

Suggestions

Add concrete templates for key deliverables—e.g., a complete example research plan with objectives, methods, timeline, and participant criteria that Claude can adapt.

Include example interview questions with good and bad examples, showing proper open-ended probing technique vs. leading questions.

Define a clear end-to-end workflow: e.g., 1. Clarify research objectives → 2. Select method (with decision criteria) → 3. Create research plan → 4. Build interview guide → 5. Synthesize findings → 6. Produce deliverables.

Remove or significantly compress the methods table and analysis framework list, as these are general UX knowledge Claude already has; replace with specific guidance on how to help users choose between methods based on their constraints.

DimensionReasoningScore

Conciseness

The content is reasonably efficient with good use of tables and lists, but includes some information that is general UX knowledge Claude already possesses (e.g., what affinity mapping is, what A/B testing is for). The method comparison table adds marginal value since Claude knows these methods well.

2 / 3

Actionability

The skill provides only high-level descriptions and categories rather than concrete, executable guidance. There are no example interview questions, no template for a research plan, no sample survey structure, and no specific instructions Claude can follow to produce any of the listed deliverables.

1 / 3

Workflow Clarity

There is no clear workflow for conducting research end-to-end. The sections are disconnected lists (methods, interview structure, analysis, deliverables) without sequencing, decision points, or guidance on how to move from one phase to the next. No validation or feedback loops are present.

1 / 3

Progressive Disclosure

The content is organized into logical sections with clear headers, which is good. However, there are no references to supporting files, and the content sits in a middle ground—too shallow to be self-sufficient but doesn't point anywhere for depth. No bundle files exist to support deeper exploration.

2 / 3

Total

6

/

12

Passed

Description

89%

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

This is a solid skill description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the capability description ('plan, conduct, and synthesize') is somewhat high-level and could benefit from more specific concrete actions or outputs to better differentiate the skill's full range of capabilities.

Suggestions

Expand the capability list with more specific concrete actions, e.g., 'create interview scripts, design survey questionnaires, develop research plans, synthesize findings into actionable insights, build user personas.'

DimensionReasoningScore

Specificity

The description names the domain (user research) and lists some actions ('plan, conduct, and synthesize'), but these are fairly high-level. It doesn't list specific concrete outputs or actions like 'create interview scripts, design survey questionnaires, analyze research findings, build persona documents.'

2 / 3

Completeness

Clearly answers both 'what' (plan, conduct, and synthesize user research) and 'when' (explicit trigger terms listed plus a broader 'when the user needs help with any aspect of understanding their users through research'). The 'Trigger with' clause serves as an explicit 'Use when' equivalent.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms that users would actually say: 'user research plan', 'interview guide', 'usability test', 'survey design', 'research questions'. These cover multiple common variations of how users would phrase requests in this domain.

3 / 3

Distinctiveness Conflict Risk

The skill occupies a clear niche around user research specifically. The trigger terms like 'interview guide', 'usability test', 'survey design', and 'research questions' are distinct and unlikely to conflict with other skills like general data analysis or product management.

3 / 3

Total

11

/

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.

Validation11 / 11 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.