Agent skill

Soc User Research

by asgard-ai-platform in asgard-ai-platform/skills

Design and conduct user research using interviews, focus groups, surveys, and field observation.

MITAuto-check passedProduct & Project Management

Install Soc User Research

skills CLI
$ npx skills add asgard-ai-platform/skills --skill soc-user-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install asgard-ai-platform/skills soc-user-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/soc-user-research .claude/skills/soc-user-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
soc-user-research
GitHub stars
242
Token cost
~1.3k tokens
SKILL.md length
523 words
Files
4 (incl. references)
Skills in repo
207
Repo updated
First seen
Licence
MIT

At a glance

Design and conduct user research using interviews, focus groups, surveys, and field observation.

  • Works in 5 steps: Warm-up: Build rapport (2 min) — "Tell… → Context: Understand their world (5 min)… → Core questions: Explore the topic (20… → …
  • The user needs to understand customer needs
  • SKILL.md covers Overview, Framework, Output Format and Examples, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Soc User Research is an agent skill from asgard-ai-platform/skills. Design and conduct user research using interviews, focus groups, surveys, and field observation. Use this skill when the user needs to understand customer needs, validate product assumptions, gather qualitative insights, or design a research study — even if they say 'we need to talk to users', 'how do we validate this idea', or 'what do our customers actually think'.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `examples/sample_scenario.md`, `references/interview-templates.md` and `references/survey-design.md`).

It sits in Product & Project Management, covering User research. The repository describes itself as: 301 open-source coding agent skills across 22 domains — methodology, judgment & gotchas packaged as Claude Agent Skills for the Asgard AI Platform. The licence is MIT.

When your agent uses it

  • The user needs to understand customer needs
  • Validate product assumptions
  • Gather qualitative insights
  • Design a research study — even if they say we need to talk to users

Example prompts

  • “we need to talk to users”
  • “how do we validate this idea”
  • “what do our customers actually think”
  • “/soc-user-research”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Warm-up: Build rapport (2 min) — "Tell me about your role/day"
  2. Context: Understand their world (5 min) — "Walk me through the last time you..."
  3. Core questions: Explore the topic (20 min) — Open-ended, no leading questions
  4. Probing: Go deeper on interesting threads — "Tell me more about that", "Why?"
  5. Wrap-up: Summarize and confirm (3 min) — "Did I understand correctly that...?"

What it can do on your machine

Read from SKILL.md and the folder at commit 4e7f4f8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Soc User Research loads about 1.3k tokens when it runs, and up to ~8.6k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 523 words, ~1,313 tokens.

Download SKILL.mdSave it as .claude/skills/soc-user-research/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
soc-user-research
description
Design and conduct user research using interviews, focus groups, surveys, and field observation. Use this skill when the user needs to understand customer needs, validate product assumptions, gather qualitative insights, or design a research study — even if they say 'we need to talk to users', 'how do we validate this idea', or 'what do our customers actually think'.
metadata.category
WP-18 社會科學院
metadata.tags
social-science, user-research, qualitative-methods

User Research Methods

Overview

User research uncovers what people need, want, and do — through direct observation and conversation, not assumptions. This skill covers four core methods: depth interviews, focus groups, surveys, and field observation, plus when to use each.

Framework

IRON LAW: Method Follows Question

Choose the method based on what you need to learn, not what's convenient.
"Why" questions → Interviews/Observation (qualitative)
"How many" questions → Surveys (quantitative)
"What do they really do" → Observation (behavioral)

Running a survey to answer "why" produces misleading data.
Method Selection
MethodBest ForSampleDepthCost
Depth InterviewUnderstanding motivations, pain points, mental models8-15 peopleVery highMedium
Focus GroupExploring reactions, generating ideas, social dynamics6-10 per group, 2-3 groupsMediumMedium
SurveyMeasuring prevalence, preferences, demographics at scale100+ responsesLowLow-Med
Field ObservationUnderstanding actual behavior in context (not self-reported)5-10 sessionsVery highHigh
Depth Interview Guide
  1. Warm-up: Build rapport (2 min) — "Tell me about your role/day"
  2. Context: Understand their world (5 min) — "Walk me through the last time you..."
  3. Core questions: Explore the topic (20 min) — Open-ended, no leading questions
  4. Probing: Go deeper on interesting threads — "Tell me more about that", "Why?"
  5. Wrap-up: Summarize and confirm (3 min) — "Did I understand correctly that...?"

Rules:

  • Ask about past behavior, not hypothetical future ("What did you do?" not "What would you do?")
  • Never ask "Would you use this?" — people are terrible at predicting their own behavior
  • Silence is a tool — let them fill the gap
Survey Design
  1. Start with screening questions (qualify respondents)
  2. Move from general to specific
  3. Put sensitive/demographic questions last
  4. Limit to 15-20 questions (5-7 min completion)
  5. Use validated scales where possible (Likert, NPS, SUS)

Question types to avoid:

  • Double-barreled: "Is the product fast and reliable?" (which one?)
  • Leading: "Don't you think our app is easy to use?"
  • Hypothetical: "Would you pay $10/month for this feature?"
Analysis

Qualitative (interviews, observation):

  • Affinity mapping: Group observations into themes
  • Look for patterns across 5+ participants
  • Quote verbatim — don't paraphrase

Quantitative (surveys):

  • Descriptive stats first (means, distributions)
  • Cross-tabulate by segments
  • Statistical significance for comparisons (p < 0.05)

Output Format

markdown
# User Research Plan: {Project}

## Research Questions
1. {what we need to learn}

## Method
- Type: {interview / focus group / survey / observation}
- Rationale: {why this method for this question}
- Sample: {who, how many, recruitment criteria}
- Timeline: {duration}

## Discussion Guide / Survey Instrument
{Key questions or survey structure}

## Analysis Plan
{How findings will be synthesized}

Examples

Show full SKILL.md (210 more words)Show less
Correct Application

Scenario: Understanding why users abandon a food delivery app at checkout

  • Method: Depth interviews (need to understand "why", not "how many")
  • Sample: 10 users who abandoned in the last 30 days (recruit via in-app data)
  • Key question: "Walk me through your last order that you didn't complete. What happened?" (behavioral, past-tense, open-ended ✓)
Incorrect Application
  • Survey asking "Would you complete your order if we removed the delivery fee?" → Hypothetical. Users will say yes but behavior may not change. Should observe actual behavior or test with a real experiment.

Gotchas

  • 5 users find 85% of usability problems (Nielsen): For usability testing, diminishing returns after 5. For understanding motivations, need 8-15.
  • Self-reported behavior ≠ actual behavior: People overestimate how healthy they eat, how often they exercise, and how much they'd pay. Observation and behavioral data > self-report.
  • Recruitment bias: If you recruit "users of our app", you miss non-users and churned users. Define the population carefully.
  • Interviewer bias: The interviewer's reactions (nodding, "great!") influence responses. Stay neutral.
  • Surveys measure what you ask, not what matters: If you didn't think to ask about a pain point, the survey won't reveal it. Use qualitative research first to discover the right questions.

References

  • For interview script templates, see references/interview-templates.md
  • For survey design best practices, see references/survey-design.md

© asgard-ai-platform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in soc-user-research of asgard-ai-platform/skills.

  • SKILL.md
  • examples/sample_scenario.md
  • references/interview-templates.md
  • references/survey-design.md

Open the folder on GitHubat commit 4e7f4f8

Compare with similar skills

Soc User Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Soc User Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Soc User Research this skillasgard-ai-platform/skills242—~1.3kAutomated safety check: PassMIT
User Research Cookiycookiy-ai/user-research-skill1.6k—~954Automated safety check: PassMIT
Fable DomainSahir619/fable-method2.3k—~2.6kAutomated safety check: PassMIT
Produck Feedback To Buildtryproduck/produck-skills511—~1kAutomated safety check: PassApache-2.0
Customer InterviewsRefoundAI/lenny-skills1.4k—~1.7kAutomated safety check: PassMIT
Product Discovery Brief Builderopen-mercato/skills231—~3kAutomated safety check: PassMIT

Similar skills

  • User Research Cookiy

    cookiy-ai/user-research-skill

    End-to-end user research assistant — qualitative and quantitative.

    1.6k GitHub stars~954 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Fable Domain

    Sahir619/fable-method

    Discuss a domain with the user, research it from real sources, then generate a trusted skill bundle for it - a step-by-step workflow with a flowchart, a domain adapter, a trap fixture, and a smoke…

    2.3k GitHub stars~2.6k tokensUpdated 8 days ago
    Product & Project ManagementAuto-check passed
  • Produck Feedback To Build

    tryproduck/produck-skills

    Pulls full in-context user feedback tickets through the Produck MCP server and turns them into an aligned product change instead of a guess.

    511 GitHub stars~1k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Customer Interviews

    RefoundAI/lenny-skills

    Help users conduct high-impact customer interviews that move beyond surface-level feature requests to identify root emotional frustrations and specific causal triggers.

    1.4k GitHub stars~1.7k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed
  • Guides a product discovery conversation and writes product-brief.md with the problem, evidence, scope, decisions and the next open question, for existing, client or own ideas.

    231 GitHub stars~3k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check passed
  • Discovery Synthesis

    andreaskelm/pm-brain

    Plan customer discovery, turn interview snapshots into synthesis and evidence-based opportunities, build or update an Opportunity Solution Tree, map jobs and segments, and design RAT tests for the…

    234 GitHub stars~2.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from asgard-ai-platform/skills

All 207 skills in this repo
  • Algo Ecom Bm25

    asgard-ai-platform/skills

    Implement BM25 ranking function for e-commerce product search relevance scoring.

    242 GitHub stars~1.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Algo Mfg Cpk

    asgard-ai-platform/skills

    Calculate Cpk process capability index to assess whether a process meets specification requirements.

    242 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Algo Price Elasticity

    asgard-ai-platform/skills

    Calculate price elasticity of demand to quantify how price changes affect sales volume.

    242 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Algo Rank Bayesian

    asgard-ai-platform/skills

    Apply Bayesian averaging to rank items by combining observed ratings with prior expectations.

    242 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Algo Rank Elo

    asgard-ai-platform/skills

    Implement Elo rating system to rank items or players from pairwise comparison outcomes.

    242 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Algo Rank Wilson

    asgard-ai-platform/skills

    Calculate Wilson Score confidence intervals for ranking items by positive proportion with sample size correction.

    242 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Soc User Research

What does Soc User Research do?

Design and conduct user research using interviews, focus groups, surveys, and field observation. Soc User Research is an agent skill from asgard-ai-platform/skills. Design and conduct user research using interviews, focus groups, surveys, and field observation.

When should I use Soc User Research?

Soc User Research fits situations like: the user needs to understand customer needs; validate product assumptions; gather qualitative insights; design a research study — even if they say we need to talk to users.

How do I install Soc User Research in Claude Code?

Run `npx skills add asgard-ai-platform/skills --skill soc-user-research -a claude-code`. Or copy the skill folder (soc-user-research in asgard-ai-platform/skills) into .claude/skills/soc-user-research in your project. Claude Code loads it when a task matches its description.

How do I install Soc User Research in Codex?

Run `npx skills add asgard-ai-platform/skills --skill soc-user-research -a codex`. Or copy the skill folder (soc-user-research in asgard-ai-platform/skills) into .agents/skills/soc-user-research in your project. Codex loads it when a task matches its description.

Can I use Soc User Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asgard-ai-platform/skills --skill soc-user-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/soc-user-research, .gemini/skills/soc-user-research, .github/skills/soc-user-research and .opencode/skills/soc-user-research in your project.

What does Soc User Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Soc User Research is instructions for the agent only.

Does Soc User Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Soc User Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Soc User Research use?

Soc User Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Soc User Research use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.3k tokens, read only when the agent opens those files.

What are the alternatives to Soc User Research?

Skills that share tags, products or a category with Soc User Research: User Research Cookiy (cookiy-ai/user-research-skill, 1.6k stars), Fable Domain (Sahir619/fable-method, 2.3k stars), Produck Feedback To Build (tryproduck/produck-skills, 511 stars) and Customer Interviews (RefoundAI/lenny-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Soc User Research?

asgard-ai-platform (a GitHub organization) maintains it in asgard-ai-platform/skills, which has 242 GitHub stars. The repository holds 207 skills in this directory. The repository was last updated on June 6, 2026.

Source: asgard-ai-platform/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.