Useberry (useberry.com) platform help — a self-serve, prototype-first UX research and usability-testing suite: prototype tests (Figma / Sketch / ProtoPie import), first-click, five-second, preference tests, card sorting, tree testing, single-task flows, surveys, plus user-flow/drop-off maps, click heatmaps, and live moderated interviews. No own panel — recruit through the Prolific integration or a share link. UI-only: no public API, webhooks, Zapier, or MCP; data leaves via CSV export. Use when importing a Figma prototype to test with real users, running a card sort or tree test to fix navigation, setting up a first-click or five-second test, hitting the free plan response cap, recruiting testers via Prolific vs your own users, reading user-flow drop-off or click heatmaps, or choosing between Useberry and Maze / Lyssna / UXtweak / Optimal Workshop. Do NOT use for the validate-before-building method or comparing research tools (use /sales-idea-validation), or an API-native pipeline (use /sales-userintuition).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
sales-useberry
description
Useberry (useberry.com) platform help — a self-serve, prototype-first UX research and usability-testing suite: prototype tests (Figma / Sketch / ProtoPie import), first-click, five-second, preference tests, card sorting, tree testing, single-task flows, surveys, plus user-flow/drop-off maps, click heatmaps, and live moderated interviews. No own panel — recruit through the Prolific integration or a share link. UI-only: no public API, webhooks, Zapier, or MCP; data leaves via CSV export. Use when importing a Figma prototype to test with real users, running a card sort or tree test to fix navigation, setting up a first-click or five-second test, hitting the free plan response cap, recruiting testers via Prolific vs your own users, reading user-flow drop-off or click heatmaps, or choosing between Useberry and Maze / Lyssna / UXtweak / Optimal Workshop. Do NOT use for the validate-before-building method or comparing research tools (use /sales-idea-validation), or an API-native pipeline (use /sales-userintuition).
argument-hint
[describe what you need help with in Useberry]
license
MIT
version
1.0.1
tags
["sales","pre-launch","platform"]
Useberry Platform Help
Useberry (useberry.com) is a self-serve, prototype-first UX research and usability-testing suite — the tool you
reach for when you have a design, prototype, or live site and want real users to test it. It bundles the battery as
blocks you drag into a study: task-based prototype testing (one-click Figma / Sketch / ProtoPie import),
first-click / five-second / preference tests, card sorting and tree testing for IA, single tasks,
surveys, live-site open analytics, and live moderated interviews (Growth+) — results as flow/drop-off
maps, click heatmaps, task success/misclick/time-on-task, Highlights, and Tags. Closest peer Maze (deep Figma
import); other peers Lyssna, UXtweak, Optimal Workshop, PlaybookUX.
The Useberry-specific thing to say every time: it has no participant panel of its own. Recruiting is
either the Prolific integration (a vetted global pool, billed pay-per-use separately from your
subscription) or a share link to your own users — that plus a very tight free plan (10 responses/mo)
is the #1 source of confusion (see Step 4). Two more caveats almost every time: (1) a task-completion
metric is not validated demand — a high success rate / clean tree test tells you the design works, not
that strangers will buy; take a build-or-not go/no-go to a real behavior test via /sales-idea-validation. (2) Useberry is UI-only — no public API, webhooks, Zapier, or MCP, so any
"pipe results into my CRM/warehouse" ask is manual CSV export or a native integration, not REST — route
real pipelines to /sales-userintuition.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer:
What do you want from Useberry?
A) Pick a study/block type — prototype / first-click / five-second / preference / card sort / tree test / single task / survey / open analytics / interview
B) Recruit testers — the Prolific integration (pay-per-use) vs a share link to your own users
C) Fix bad results — junk click-through responses, weak screeners, thin fraud/verification
D) Read results / get data out — user-flow drop-off, click heatmaps, first-click accuracy, card-sort matrix, tree-test findability; CSV export (no API)
Are you testing something you've already built/designed, or still deciding whether to build? The
second is an idea-validation question, not a usability question — flag it in Step 2.
Skip-ahead: if the user's prompt already names the study type and their question is specific, go to Step 3.
Step 2 — Route or answer directly
If the user's question is about…
Route to
Comparing research/idea/synthetic tools across the market, or the validate-before-building method
/sales-idea-validation {question}
An API / webhook / MCP-native research or interview pipeline (Useberry has none)
/sales-userintuition {question}
Running a real behavior demand test (smoke-test page, waitlist, pre-sale) instead of a usability test
/sales-idea-validation or /sales-funnel{question}
Analyzing existing NPS/CSAT/VoC/review feedback (post-launch, not new tests)
/sales-customer-feedback {question}
Deep think-aloud video recordings as the primary output
/sales-userbrain {question}
When routing, give the exact command: "This is a {domain} question — run: /sales-idea-validation {original question}"
Otherwise, answer Useberry-specific questions using Step 3.
Step 3 — Useberry platform reference
Read references/platform-guide.md for the full reference — the block/study-type catalog (what each
one measures + how to read its output), the automation-surface table, best-effort pricing/plan gates (Free
10-response cap, Growth interview metering, Prolific pay-per-use), the data model, recruiting (Prolific vs
share-your-own), and the no-API data-out playbook. Useberry has no public API — no API-reference file.
Answer using only the relevant section — don't dump the full reference.
Step 4 — Actionable guidance
Lead with recruiting: Useberry has no panel of its own. Whenever testers, participants, or "how do I
find users" comes up, say it plainly — you either connect Prolific (a vetted pool, billed
pay-per-use, separate from the subscription — the two costs are easy to confuse) or share a link with
your own users (no per-participant fee). For a small sample the cheapest path is a share link within
the free-plan response cap, not Prolific. Reviewers flag the built-in recruiting as thin, so recommend
Prolific screeners (or your own audience) rather than expecting Useberry to source niche participants.
Warn about the very tight free plan, as best-effort — but confirm what it CAN do.Free (€0) is
capped at ~10 responses/mo, 1 project, 1 seat, 5 blocks/study, 3 versions — but a prototype test
(Figma/Sketch/ProtoPie import), first-click, and the other core blocks do run on it if you
self-recruit via a share link within that cap; only recordings, transcription, live interviews, and
Tags/Highlight Reels are gated to Growth (~300 responses) / Business (SSO/SAML, Brand Kits).
State all figures as best-effort and point to useberry.com/pricing.
Say the caveat: a usability metric is not demand. Make explicit that Useberry measures whether a
built design/flow works (task success, first-click accuracy, findability, drop-off) — it does
not prove strangers will pay. If they're still deciding whether to build, keep the usability
findings but take the go/no-go to a real behavior test (smoke test, pre-sale) via /sales-idea-validation.
Flag it as UI-only when any automation/export comes up. Useberry has no public API, webhooks,
Zapier, or MCP (verify current docs). "Sync results to HubSpot/Snowflake" is a manual CSV export, or
the native integrations — Figma / Sketch / ProtoPie (prototype import, inbound), Prolific
(recruitment), and Google Meet / Teams / Zoom + Google Calendar / Outlook (interview scheduling
only) — not a REST pipeline. If the user needs a programmatic pipeline, tell them so and route to
/sales-userintuition.
Match the block to the question (full catalog in references/platform-guide.md): prototype test
= task success/time on a Figma/Sketch/ProtoPie flow; first-click = where users click first;
five-second = first impression/recall; preference = A/B of designs; card sorting = how users
group/label content; tree testing = findability in nav (no visual); open analytics = click
heatmaps/flows on a live site via the snippet. Don't run a five-second test for navigation.
Set participant counts realistically (rule-of-thumb): ~5 per user group for qualitative usability
(task tests, interviews); ~30+ for quantitative tests (first-click, card sort, tree test, preference).
If you discover a gotcha or tip not in references/learnings.md, append it there with today's date.
Gotchas
Best-effort from research (2026-07) — pricing, the Free 10-response cap, the Prolific pay-per-use model,
interview metering, and the (absent) API/export surface move; verify at useberry.com.
No panel of its own — recruiting is Prolific or your own link. Unlike Lyssna/UXtweak (which have their
own panels), Useberry sources external participants via the Prolific integration, billed
pay-per-use separately from your subscription. Self-recruiting via a share link avoids the fee.
Built-in recruiting is thin — lean on Prolific screeners or bring your own audience.
Usability ≠ demand. Useberry proves a design works, not that anyone will buy — the go/no-go on
building still belongs to a real behavior test (smoke test, pre-sale). Route that to /sales-idea-validation.
No API, no webhooks, no Zapier, no MCP. Useberry is UI-only; data-out is manual CSV export or
native integrations (Figma / Sketch / ProtoPie prototype import; Prolific recruitment;
calendar / Meet / Zoom / Teams for interview scheduling only — not data export). Route pipeline needs
to /sales-userintuition.
The free plan is genuinely small.~10 responses/month, 1 project, 1 seat, 5 blocks/study, 3
versions/project — fine for one quick test, not a real study cadence. Recordings, transcription, live
interviews, Tags & Highlight Reels start on Growth.
Prototype-first, so depth is shallow vs full-suite tools. Reviewers describe metrics as
surface-level and participant fraud/verification as thinner than enterprise suites — tighten Prolific
screeners and attention checks, and don't expect deep statistical analysis.
Figma/Sketch/ProtoPie prototype import can be slow or flaky on large flows. Simplify the prototype
and re-import if a study stalls.
Related skills
/sales-uxtweak — The closest all-in-one usability + information-architecture peer — the same battery (card sort, tree test, first-click / five-second / preference, prototype/website tests) in one seat, with its own 130-country panel; route here to compare or when UI-heavy IA depth (similarity matrix / dendrogram / pietree) matters. Install: npx skills add sales-skills/sales --skill sales-uxtweak -a claude-code
/sales-lyssna — The big-panel usability peer (ex-UsabilityHub) — the same quick-test battery on a 690k+ own panel with a usable free plan; route here to compare, or when you want a built-in panel instead of Useberry's Prolific dependency. Install: npx skills add sales-skills/sales --skill sales-lyssna -a claude-code
/sales-userbrain — The video-first think-aloud usability peer — real testers narrate screen + voice while doing your tasks (AI highlights, transcripts, clips); route here when you want to watch people use it and hear why, not Useberry's flow/heatmap metrics. Install: npx skills add sales-skills/sales --skill sales-userbrain -a claude-code
/sales-uxarmy — The usability + IA peer that brings its own APAC-first panel (20+ Asia-Pacific countries) where Useberry has none and recruits via Prolific — route here when the study targets Asia-Pacific users, or when a card sort / tree test at scale is the job: UXArmy prices those at a fraction of a credit per response. Install: npx skills add sales-skills/sales --skill sales-uxarmy -a claude-code
/sales-idea-validation — The tool-agnostic validate-before-building method + the full research/usability/validator tool landscape (use this to actually decide build-or-not; a passing usability test is not demand). Install: npx skills add sales-skills/sales --skill sales-idea-validation -a claude-code
/sales-prolific — Prolific platform help — the panel Useberry recruits from. Useberry has no panel of its own, so participant recruitment, screeners, demographic filters, and per-participant cost live in Prolific (billed separately); route here to set up the recruitment, target filters, or budget the Prolific reward + platform fee behind a Useberry study. Install: npx skills add sales-skills/sales --skill sales-prolific -a claude-code
/sales-userintuition — The API/webhook/MCP-native real-human interview peer — the pick when you need a programmatic research pipeline Useberry can't offer. Install: npx skills add sales-skills/sales --skill sales-userintuition -a claude-code
/sales-customer-feedback — Real-customer NPS/CSAT/VoC strategy across tools (use to analyze existing feedback; Useberry proactively runs new tests). Install: npx skills add sales-skills/sales --skill sales-customer-feedback -a claude-code
/sales-funnel — Build the smoke-test / fake-door landing page that turns a design hypothesis into a real demand test. Install: npx skills add sales-skills/sales --skill sales-funnel -a claude-code
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code
Examples
Example 1: "How do I recruit testers in Useberry, and why is it charging me on top of my plan?"
User says: "I set up a prototype test but Useberry wants me to pay per participant even though I already
have a subscription. Where's the panel?"
Skill does: Explains Useberry has no panel of its own — external testers come from the Prolific
integration, billed pay-per-use separately from the subscription (that's the extra charge), while a
share link to your own users has no per-participant fee. Recommends the share-link path for a small
sample within the free-plan response cap, and Prolific with tight screeners when you need a vetted/targeted
pool. Notes built-in recruiting is thin, and that even clean results prove the design works, not that
anyone will pay.
Result: The user recruits their own users via a share link and reserves Prolific for targeted samples.
Example 2: "How do I get every completed Useberry study into our warehouse automatically?" (developer/automation)
User says: "I want study results to flow into BigQuery and a Slack channel. How do I set up the API or webhook?"
Skill does: States plainly that Useberry is UI-only — no public API, webhooks, Zapier, or MCP — so
there's no automated REST path. Data-out is manual CSV export; the native integrations are Figma /
Sketch / ProtoPie (prototype import, inbound), Prolific (recruitment), and calendar / Meet / Zoom /
Teams (interview scheduling, not data export) — none move result data into a warehouse. If a live
pipeline is a hard requirement, routes to /sales-userintuition (REST API + HMAC webhooks + MCP), noting
that's real-human interviews, not Useberry's quick-test battery.
Result: The user sets up a scheduled CSV export/ETL instead of hunting for an API that doesn't exist.
Example 3: "Is the free plan enough to test my Figma prototype, or do I have to pay?"
User says: "I'm a solo founder. Can I run a real prototype test on Useberry's free plan, and what will it cost?"
Skill does: Lays out the Free plan (best-effort) — ~10 responses/month, 1 project, 1 seat, 5
blocks, 3 versions — enough for one quick prototype test if you self-recruit via a share link (no
participant fee), but recordings, transcription, live interviews, and Tags/Highlight Reels require
Growth. Explains the two separate costs (subscriptionandProlific participants, pay-per-use),
so the cheapest path is importing the Figma prototype and sharing a link within the 10-response cap. Points
to useberry.com/pricing; flags every figure as best-effort.
Result: The founder imports the Figma prototype and runs a share-link test on the free plan.
Troubleshooting
"Useberry is charging me per participant even though I pay for a plan"
Symptom: A subscription is active but the user is billed again to get responses.
Cause: Useberry has no panel of its own — external participants come from the Prolific
integration, billed pay-per-use separately from the subscription. The two costs are easy to confuse.
Solution: For your own/known users, share a participant link (no per-participant fee) and stay
within the plan's response cap. Use Prolific only when you need a vetted, demographically targeted pool,
and add screeners + attention checks there. Confirm current per-response Prolific pricing before
committing — treat figures as best-effort.
"The free plan runs out almost immediately"
Symptom: Responses stop around ~10, or the user can't add more projects/blocks or use recordings.
Cause: The Free plan caps ~10 responses/month, 1 project, 1 seat, 5 blocks/study, 3
versions/project and gates recordings, transcription, live interviews, and Tags/Highlight Reels.
Solution: Self-recruit via a share link to spend responses on real target users, keep the study to
its highest-signal blocks, and upgrade to Growth for ~300 responses, recordings/transcription, live
interviews (~5/mo), and Tags/Highlight Reels. Confirm current caps at useberry.com/pricing — best-effort.
"How do I automate exports / connect Useberry to my stack?"
Symptom: The user wants results flowing into a CRM, warehouse, or Slack automatically.
Cause: Useberry has no public API, webhooks, Zapier, or MCP — it's UI-only (verify current docs).
Solution: Use manual CSV export for ad-hoc handoff or a scheduled ETL over the exported file. The
native integrations — Figma / Sketch / ProtoPie (prototype import), Prolific (recruitment), and
Google Calendar / Outlook / Meet / Zoom / Teams (interview scheduling only) — don't move result data
out. If an automated, programmatic pipeline is a requirement, use an API-native research tool instead —
route to /sales-userintuition (REST API + HMAC-signed webhooks + MCP server).
