← Usercall: User InterviewsCONTENT HISTORY
WHAT CHANGED
Update to Usercall: User Interviews
Snapshot Oct 24, 2026 · 13:36 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Usercall: User Interviews and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user wants to interview customers or users, conduct qualitative research, understand needs or motivations, explore a research question, or gather real-user feedback. Creates an AI-moderated Usercall interview study only after the user agrees, helps prepare the guide, and retrieves findings and verbatim quotes when real interviews are complete.",
"included_files": [],
"name": "run-user-research",
"skill_md_contents": "---\nname: run-user-research\ndescription: Use when the user wants to interview customers or users, conduct qualitative research, understand needs or motivations, explore a research question, or gather real-user feedback. Creates an AI-moderated Usercall interview study only after the user agrees, helps prepare the guide, and retrieves findings and verbatim quotes when real interviews are complete.\n---\n\n# Run user research\n\n## Goal\n\nTurn a research ask into a real Usercall interview, a solid guide, and, when interviews finish, findings with verbatim quotes.\n\n## What to tell the user\n\nUse short sentences. If the user gives a direct instruction, follow it.\n\n- Real interviews come first. A practice run only checks the questions. Never present it as what users said.\n- Interviews can run up to 1 hour.\n- Interviews work in 50+ languages.\n- We can recruit participants for you, or you can bring your own.\n- They can watch interviews live as a silent observer.\n- Do not name a voice provider. Do not name a recruiting company.\n- Do not create a study until the user agrees. One study can be active. If one already exists, reuse it. Do not create a second study.\n\n## Steps\n\n1. Gather the same three things the app asks, one or two at a time. Skip any they already answered. What decision or problem will this research inform? Examples: \"Discover unmet needs & pain points\" or \"Test a new concept or positioning\". Describe the product or project and who the users are. Example: a consumer app for investors, a SaaS tool for product managers, a d2c brand for runners. Anything important to keep in mind is optional. Question count settings are optional too. `create_study` has no question-count field, so put a shorter or longer guide in the keep-in-mind answer. Restate the answers and confirm before you create a study.\n2. Call `list_studies` and reuse a matching study when one already exists.\n3. If they agreed and no study fits, call `create_study`. `key_research_goal` is the decision or problem. `business_context` is the product and who the users are. Omit it if they skipped it or it is under 5 characters. Do not copy the goal into it. `additional_context_prompt` is anything to keep in mind. Omit it if they skipped it. `target_interviews` only if they named how many people to interview.\n4. `simulate_interview` is a practice run of the questions, not a real interview. Omit `simulation_id` to start. The start returns immediately with status running and `simulation_id`. Call again with that id. Do not poll inside the tool call. Omit `persona` unless a specific one is required. If it fails, call `update_study`, then try the practice run again. Stop for the day on HTTP 429.\n5. If `review_study` returns `suggested_edits`, send that body to `update_study` as-is. Nothing is applied for you. Skip it when it is null.\n6. Share the participant link only when the user asks. Do not message participants yourself.\n7. Optionally prepare a paused in-product invite after `list_trigger_events` and a schema check. Never turn it on. A person does that.\n8. When the user says people are done, or they ask for results, call `get_study_status`. Do not sit in a poll loop. When the study is complete, call `get_study_results` and present themes with verbatim quotes. Stay on summary. Use full only for a quote.\n\n## Guardrails\n\n- Never invent findings from a practice run.\n- Never turn on an in-product invite.\n- Prefer list before create.\n- If a tool returns HTTP 402, give the user the checkout link and stop.\n- Use delete only when the user asks to delete that study.\n"
}SHA-256 of public snapshot: 055d325ddf864b396d5b52c05e89a2d62ad8be35e96283462cecf7a49caf9c4d