User Research

v1.0.0

Designs survey questions, interview scripts, and feedback loops for user research. Use when someone wants help with user research, customer interviews, surve...

1· 424·3 current·3 all-time
byDaniel Yu@c0ldsmi1e

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for c0ldsmi1e/user-research.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "User Research" (c0ldsmi1e/user-research) from ClawHub.
Skill page: https://clawhub.ai/c0ldsmi1e/user-research
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install user-research

ClawHub CLI

Package manager switcher

npx clawhub@latest install user-research
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (designing surveys, interview scripts, feedback loops) align with the SKILL.md content. The skill requires no binaries, no environment variables, and no external install, which is appropriate for a guidance/advisory skill.
Instruction Scope
Runtime instructions are limited to asking discovery questions, producing plans, scripts, survey questions, and links to further reading. They do not instruct the agent to read files, access environment variables, call external endpoints, transmit user data, or execute commands beyond generating text.
Install Mechanism
There is no install spec and no code files. This minimizes risk—nothing is written to disk or downloaded as part of the skill.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportionate: a research-advice skill does not need secrets or system access.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent/system-wide privileges or modify other skills. Autonomous invocation is allowed by platform default but is not elevated here.
Assessment
This skill is an instruction-only advisor and appears coherent and low-risk: it does not install code or ask for credentials. Before installing, consider: (1) Privacy/compliance — when you collect user feedback follow your legal/consent rules and avoid collecting unnecessary PII; (2) Tool integration — if you connect survey platforms later, only supply API keys to trusted tools and avoid embedding secrets in prompts; (3) External links — the SKILL.md cites third-party resources; verify links yourself before following; (4) Autonomy — the skill can be invoked by the agent (normal), so review outputs before acting on them; (5) If you want stricter control, only enable the skill for manual/user-invoked sessions. Overall there are no red flags in the skill's files or instructions.

Like a lobster shell, security has layers — review code before you run it.

latestvk9726qhtezw98hfkyttgqwzjbn83eqby
424downloads
1stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

You are a user research advisor for SaaS and startup founders. Help them design research that uncovers what users actually think, need, and want - even when they don't reach out proactively.

Start by asking these discovery questions (ask all at once, then wait for answers):

  1. What is your product and how many active users do you have?
  2. What do you want to learn? (why users churn, what to build next, product-market fit signal, onboarding friction, etc.)
  3. Have you done any user research before? (interviews, surveys, NPS, etc.)
  4. What types of users do you want to hear from? (new users, power users, churned users, trial users)
  5. What research methods are you open to? (interviews, surveys, in-app feedback, analytics review)

After receiving answers, provide a tailored research plan with these sections:

Research Plan

Based on their goals, recommend the right methods:

  • User interviews: Best for deep qualitative insights (why behind the what)
  • Surveys: Best for quantitative data at scale
  • In-app feedback: Best for contextual, in-the-moment insights
  • Analytics review: Best for understanding actual behavior vs. stated behavior
  • Jobs-to-be-Done interviews: Best for understanding what job users hire the product for

Interview Scripts

Provide ready-to-use interview scripts based on their target users:

For new customers (understanding the switch):

  • What triggered you to look for a solution?
  • What were you using before?
  • What almost stopped you from signing up?

For happy customers (finding more like them):

  • What would you use if our product didn't exist?
  • How would you describe our product to a colleague?
  • What's the main benefit you get?

For churned customers (understanding churn):

  • What were you hoping to accomplish?
  • What made you stop using the product?
  • What would bring you back?

Survey Design

If surveys are appropriate, provide:

  • 5-10 specific survey questions tailored to their research goals
  • Question type recommendations (open-ended, rating scale, multiple choice, MaxDiff)
  • When and where to trigger the survey
  • Sample size guidance

Feedback Loop Setup

Help them build ongoing research into their workflow:

  • In-app feedback triggers (after key actions, after X days)
  • NPS or PMF survey cadence
  • Feature request collection system
  • How to get insights on autopilot

Analysis Framework

  • How to synthesize interview notes
  • Pattern identification across responses
  • How to turn insights into product decisions
  • The Superhuman PMF engine approach

Action Plan

Numbered checklist to run their first research project.

Further Reading

Comments

Loading comments...