synthetic-user-testing

synthetic-user-testing is a skill for Claude Code from Owl-Listener/designpowers. It costs 71 tokens per session (2,100 once invoked), scanned A, original, MIT.

A method for checking an interface by acting out realistic tasks from different user perspectives, such as someone with low vision or limited movement.

In plain words
What is it for?
Walk through key tasks as named personas after fixes, check unclear user flows, and report what works or fails from each person's perspective.
Why use it?
It finds problems that code review and standard checks may miss because they appear only during actual use.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook shipped together

Good fit Walk through key tasks as named personas after fixes, check unclear user flows, and report what works or fails from each person's perspective.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designpowers/synthetic-user-testing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designpowers --skill synthetic-user-testing
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for synthetic-user-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/synthetic-user-testing.svg)](https://agentmods.dev/skills/owl-listener/designpowers/synthetic-user-testing)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/synthetic-user-testing"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/synthetic-user-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,100 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.02100
Opus 5 $0.00036 $0.01050
Sonnet 5 $0.00014 $0.00420
Haiku 4.5 $0.00007 $0.00210

Measured 9d ago against content hash b92662cd20ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

synthetic-user-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/synthetic-user-testing/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Synthetic User Testing

Synthetic user testing is the closest thing to putting the design in front of real people without leaving the pipeline. You walk through the interface as each persona, attempting real tasks, and report what works, what breaks, and what feels wrong — from their perspective, not yours.

This is not a checklist exercise. It is an act of empathy disciplined by specifics. When you test as Jordan (low-vision, uses 200% zoom and high contrast), you don't ask "is contrast sufficient?" — you ask "can Jordan find the 'continue reading' button at 200% zoom when three articles are competing for attention?"

When to Use

  • After the fix round — the design-builder has addressed findings from critic, accessibility-reviewer, and heuristic-evaluator. Now validate that the fixes work and no new issues were introduced
  • Before verification-before-shipping — synthetic testing feeds directly into the persona walkthrough in the verification report
  • When the design-critic flags persona coverage gaps — if the critique says "unclear whether Persona X can complete Task Y," run a synthetic test to find out
  • When the team is unsure about a flow — synthetic testing turns "I think this works for screen reader users" into "here's exactly where a screen reader user would get stuck"

Process

Step 1: Gather Test Context

Before testing, assemble:

  • Personas from inclusive-personas (via design-state.md)
  • Key tasks from the design brief — the things the design must enable
  • The build — test the actual implementation, not the spec
  • Assistive technology context — for each persona, what tools they use and how (zoom level, screen reader, keyboard-only, switch access, etc.)

Step 2: Define Test Scenarios

For each key task in the brief, write a scenario that a persona would actually encounter. Scenarios are not "test case 1" — they are moments:

Format:

SCENARIO: [Natural situation trigger]
TASK: [What the persona is trying to accomplish]
PERSONA: [Name] — [key ability context]
SUCCESS: [What "done" looks like for this persona]

Read the full file on GitHub · 193 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 193 lines · 71 tokens per session scan A b92662cd20ce

Subscribe to this mod's changes

synthetic-user-testing is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 2,100 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

scenario-design

Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…

BlackBeltTechnology/pi-agent-dashboard · 88 tokens

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

frontend-mockup-loop

Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…

BlackBeltTechnology/pi-agent-dashboard · 185 tokens

frontend-mockup-loop-dashboard

Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens