synthetic-users
Skill1 starsChanged 38 days agoMITView on GitHub
Use AI simulated users to pressure test assumptions, sharpen interview questions and anticipate objections, clearly labelled as hypotheses, never evidence. Use when someone asks about synthetic users, AI personas, simulated user interviews, or wants quick feedback on a concept before real research.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pedroromeroluna/ai-first-product-skillstheir own version, first seen Oct 20, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- The-Utopia-Studio/skills★ 6same name
- pedroromeroluna/ai-first-product-skills★ 5same name
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 repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- analytics-insightsSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- interview-guideSkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- stakeholder-interviewsSkill
- survey-designSkill
- usability-test-analysisSkill
- usability-test-planSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Widen the frame: ask for perspectives the team hasn't considered (people using screen readers, people on slow connections, people new to …
- Distinctive: line 19
Ground each synthetic user in real research: when you have it (a persona and quotes), and say when you don't.
- Distinctive: line 30
Don't count synthetic answers as participants, put them in research reports as findings, quote them as users, or use them to decide whether …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Synthetic users
Asking an AI to role play users is fast and tempting, and it can't replace people: it tells you what's typical in its training data, not what your users do. Used carefully, it's good for one thing: getting sharper before you talk to real people.
Good uses
- Stress test assumptions: "What would make a cautious comparer not trust this price?" Then check the answers with real users.
- Sharpen a guide: rehearse interview questions and spot leading or confusing ones.
- Anticipate objections and edge cases to cover in a test.
- Widen the frame: ask for perspectives the team hasn't considered (people using screen readers, people on slow connections, people new to the country), then recruit those people.
How
- Ground each synthetic user in real research when you have it (a persona and quotes), and say when you don't.
- Ask for reasoning, not verdicts: "What would you look for first, and why?" rather than "Would you buy this?"
- Generate several distinct perspectives, and ask each what would make them leave.
- Turn every output into a hypothesis with a plan to test it: "Hypothesis: people won't trust a price without seeing the insurer. Test: usability task 2."
Output
A list of hypotheses and better questions, each labelled "synthetic, not evidence", with how to validate it.
Don't
- Don't count synthetic answers as participants, put them in research reports as findings, quote them as users, or use them to decide whether something ships.
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.

