user-research
Skill8 starsChanged 38 days agoMITView on GitHub
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.
17 other projects use a version of this, 1 of them edited.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- strikersam/autonomous-ai-agencytheir own version, first seen Oct 19, 2026
- sankar2code/Claude-Skill_SubAgent-Builder-Collectionstheir own version, first seen Oct 13, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
Used with
Projects with it also use prd-writer, competitive-analysis and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nimbalystSkillprd-writer
Create structured Product Requirements Documents (PRDs) with prioritized requirements. Use when writing product specs, feature requirements, or project briefs.
Also in 3 projects that use this
AnthropicSkillcompetitive-analysis
Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.
Also in 3 projects that use this
Microsoft AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 3
- anthropics/knowledge-work-plugins★ 35k100% same
- KevinReactiv8/claude-skills★ 0100% same
- shahbazaliofficial/Claude-Skills★ 0100% same
Edited · 1
- NinjaSln-labs/agent-skills★ 139% same
Wrote their own version · 13
- aakashg/pm-claude-code-setup★ 152same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- strikersam/autonomous-ai-agency★ 11same name
- kevinaimonster/skill-hub★ 4same name
- sankar2code/Claude-Skill_SubAgent-Builder-Collections★ 2same name
- AxlZero21/Skills★ 1same name
- huangqianqian120/skillslibrary★ 1same name
- nisarth/claude-skills-store★ 1same name
- qike7777/skill-library★ 1same name
- toribryan/design-skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- figma-designSkill
- figma-designSkill
- accessibility-reviewSkill
- animateSkill
- better-accessibilitySkill
- better-colorsSkill
- better-layoutSkill
- better-typographySkill
- better-uiSkill
- breakSkill
- create-design-mdSkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- emil-design-engSkill
- frontend-designSkill
- research-synthesisSkill
- ux-copySkill
The file
Files
User Research
Help plan, execute, and synthesize user research studies.
Research Methods
| Method | Best For | Sample Size | Time |
| User interviews | Deep understanding of needs and motivations | 5-8 | 2-4 weeks |
| Usability testing | Evaluating a specific design or flow | 5-8 | 1-2 weeks |
| Surveys | Quantifying attitudes and preferences | 100+ | 1-2 weeks |
| Card sorting | Information architecture decisions | 15-30 | 1 week |
| Diary studies | Understanding behavior over time | 10-15 | 2-8 weeks |
| A/B testing | Comparing specific design choices | Statistical significance | 1-4 weeks |
Interview Guide Structure
- Warm-up (5 min): Build rapport, explain the session
- Context (10 min): Understand their current workflow
- Deep dive (20 min): Explore the specific topic
- Reaction (10 min): Show concepts or prototypes
- Wrap-up (5 min): Anything we missed? Thank them.
Analysis Framework
- Affinity mapping: Group observations into themes
- Impact/effort matrix: Prioritize findings
- Journey mapping: Visualize the user experience over time
- Jobs to be done: Understand what users are hiring your product to do
Deliverables
- Research plan (objectives, methods, timeline, participants)
- Interview guide (questions, probes, activities)
- Synthesis report (themes, insights, recommendations)
- Highlight reel (key quotes and observations)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.