adversarial-ux-test

Tests web apps as a hostile non-technical persona and filters complaints into actionable UX tickets.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill adversarial-ux-test-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/xu1713/openhorse --skill adversarial-ux-test-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Traditional QA finds bugs but misses friction — the confusing terminology, excessive clicks, and cold-start problems that make real users abandon a product. This Skill surfaces genuine UX issues by roleplaying the hardest possible user, then filtering their complaints so only real problems become tickets. ## Core Features & Use Cases - Persona-Based Testing: Generates or adopts a specific tech-resistant persona (age, tech comfort, core task) and browses the app fully in character, attempting real workflows rather than feature tours. - Pragmatism Filter: Classifies every complaint as RED (real UX bug), YELLOW (low priority), WHITE (persona noise), or GREEN (feature request), so teams never ship raw rants as tickets. - Actionable Ticket Creation: Produces up to 10 tickets with verbatim persona quotes, objective issue descriptions, and suggested fixes, plus screenshots of every pain point. - Use Case: Before a product launch, run the test on your staging site as a 60-year-old non-technical user to catch onboarding gaps, jargon, and signup friction your team has become blind to. ## Quick Start Run an adversarial UX test on my staging site as a grumpy non-technical user and create tickets for the real issues.

Frequently Asked Questions about adversarial-ux-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial UX test on my web app?

Tell the agent to run an adversarial UX test on your app's URL, optionally specifying a persona type. The agent browses the app in character, attempts the persona's core tasks, captures screenshots, and produces filtered tickets for genuine issues.

What is the pragmatism filter in persona-based UX testing?

The pragmatism filter classifies each persona complaint as RED (real bug), YELLOW (low priority), WHITE (persona noise), or GREEN (feature request). Only RED and GREEN items become tickets, preventing grumpy-persona rants from polluting the backlog.

Can I provide my own user persona for UX testing?

Yes, you can supply a persona or let the agent generate one based on your target audience. A good persona specifies age, tech comfort level, the one task they need to accomplish, and what would make them give up.

Does adversarial UX testing work on local development environments?

No, the Skill requires testing on a staging or deployed app, not local dev. It also recommends registering as a new user rather than using pre-seeded admin accounts to capture the real cold-start experience.

What are the limitations of persona-based UX testing?

Sessions are limited to one persona and a maximum of 10 tickets, so coverage is narrow by design. Findings reflect extreme-user friction and must pass the pragmatism filter before representing typical user problems.