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.
65
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./design/skills/user-research/SKILL.mdQuality
Discovery
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 description with excellent trigger terms and completeness, clearly answering both what the skill does and when to use it. Its main weakness is that the 'what' portion is somewhat high-level—listing more specific concrete actions (e.g., 'create interview scripts, design survey questionnaires, synthesize findings into reports') would strengthen it. The trigger terms are well-chosen and naturally match what users would say.
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'create interview scripts, design survey questionnaires, build usability test plans, synthesize findings into actionable reports' instead of the general 'plan, conduct, and synthesize user research'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists some actions ('plan, conduct, and synthesize user research') but these are fairly high-level. It doesn't enumerate specific concrete outputs or capabilities like 'create interview scripts, design survey questionnaires, analyze usability test results, generate research reports.' | 2 / 3 |
Completeness | Clearly answers both 'what' (plan, conduct, and synthesize user research) and 'when' (explicit trigger terms listed plus a broader catch-all 'when the user needs help with any aspect of understanding their users through research'). | 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 user research activities. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around user research specifically, with distinct trigger terms like 'interview guide', 'usability test', and 'survey design' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 for user research concepts than an actionable skill for Claude. It lacks concrete examples of what Claude should produce (e.g., a sample research plan, example interview questions), has no workflow sequencing, and mostly lists information Claude already knows about UX research methods.
Suggestions
Add concrete example outputs for each deliverable type (e.g., a sample research plan with objectives, a set of example interview questions for a specific scenario) so Claude knows exactly what to produce.
Define a clear workflow: when a user asks for research help, what steps should Claude follow? E.g., 1) Clarify research objectives, 2) Recommend method, 3) Generate appropriate artifact.
Remove or drastically condense the methods table and analysis framework—Claude already knows these concepts. Focus instead on project-specific decision criteria and templates.
Add example input/output pairs showing what a user might ask and what Claude should produce in response.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient with good use of tables and lists, but includes some information that Claude already knows (e.g., general research method descriptions, basic interview structure). The analysis framework section lists well-known UX concepts without adding novel guidance. | 2 / 3 |
Actionability | The skill describes research concepts at a high level but provides no concrete, executable guidance. There are no example outputs (e.g., a sample research plan, interview questions, or synthesis report template), no specific instructions for what Claude should produce, and no copy-paste ready artifacts. | 1 / 3 |
Workflow Clarity | There is no clear workflow for how Claude should conduct or support user research. The sections list categories of information (methods, analysis, deliverables) but don't sequence them into a process with decision points or validation steps. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers and uses tables/lists effectively. However, for a skill covering this many research methods and deliverables, it would benefit from linking to separate detailed guides (e.g., a full interview guide template, survey design guide) rather than providing only surface-level coverage inline. | 2 / 3 |
Total | 6 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- anthropics/knowledge-work-plugins
- Commit
f55b539
- 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.