research-synthesis
Synthesize user research into themes, insights, and recommendations. Use when you have interview transcripts, survey results, usability test notes, support tickets, or NPS responses that need to be distilled into patterns, user segments, and prioritized next steps.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly communicates what the skill does and when to use it. It provides excellent trigger term coverage with specific input types and output formats, making it easy for Claude to select appropriately. The only minor note is the use of second person 'you have' in the trigger clause, but the main action verb is in third person imperative form, so the impact is minimal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'synthesize user research into themes, insights, and recommendations' and further specifies 'distilled into patterns, user segments, and prioritized next steps.' These are concrete, actionable outputs. | 3 / 3 |
Completeness | Clearly answers both what ('Synthesize user research into themes, insights, and recommendations') and when ('Use when you have interview transcripts, survey results, usability test notes, support tickets, or NPS responses that need to be distilled into patterns, user segments, and prioritized next steps'). Explicit 'Use when' clause is present. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'interview transcripts', 'survey results', 'usability test notes', 'support tickets', 'NPS responses', 'user research', 'themes', 'insights', 'patterns', 'user segments'. These are terms a user would naturally use when seeking this kind of analysis. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche of user research synthesis. The specific input types (interview transcripts, NPS responses, usability test notes) and outputs (themes, user segments, prioritized next steps) make it unlikely to conflict with general data analysis or document processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid template-driven skill that excels at defining a concrete, well-structured output format and provides good progressive disclosure. Its main weaknesses are the lack of an explicit synthesis workflow (how to go from raw data to themes to insights) and some unnecessary content like explaining basic research concepts to Claude. Adding a step-by-step analysis process with validation checkpoints would significantly improve it.
Suggestions
Add an explicit multi-step synthesis workflow (e.g., 1. Code raw data → 2. Identify recurring patterns → 3. Validate themes have sufficient evidence → 4. Generate insights → 5. Prioritize recommendations) with validation checkpoints between steps.
Remove the Tips section or reduce it to a single line — Claude already understands the difference between observations and interpretations and the value of specificity.
Trim the 'What I Accept' section to a single line like 'Accepts any qualitative or quantitative user research data (transcripts, surveys, tickets, reviews, etc.)' since the list is self-evident.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'What I Accept' which lists obvious input types Claude would already understand. The output template is detailed but justified as it defines the expected format. The Tips section explains basic research concepts (observations vs interpretations) that Claude already knows. | 2 / 3 |
Actionability | The output template is fully concrete and copy-paste ready — it provides a complete markdown structure with specific formatting for themes, insights-to-opportunities tables, user segments, and prioritized recommendations. The connector integrations give specific, actionable guidance on what to do when each tool is available. | 3 / 3 |
Workflow Clarity | The skill provides a clear output format but lacks an explicit multi-step workflow for how to actually perform the synthesis process (e.g., first code the data, then identify themes, then validate themes against evidence, then prioritize). There's no validation checkpoint — for instance, no step to verify theme saturation or check that insights are grounded in sufficient evidence before generating recommendations. | 2 / 3 |
Progressive Disclosure | The skill appropriately references related content with one-level-deep links: CONNECTORS.md for tool setup and the user-research skill for methods/frameworks. The main content is well-organized into clear sections (Usage, What I Accept, Output, Connectors, Tips) without being monolithic or deeply nested. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.