adversarial-ux-test

Run adversarial persona browsing to identify UX friction and create prioritized tickets.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/eddielueng/hermes-agent-zh --skill adversarial-ux-test-eddielueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/eddielueng/hermes-agent-zh/tree/main/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/eddielueng/hermes-agent-zh --skill adversarial-ux-test-eddielueng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams discover genuine UX pain points by putting products through an intentionally difficult, tech-resistant persona and then converting that feedback into actionable improvements.

Core Features & Use Cases

  • Adversarial persona testing: Roleplays the hardest possible user to stress navigation, comprehension, onboarding, and accessibility.
  • Pragmatism filter for signal: Separates true UX bugs and high-value usability issues from persona “noise” and low-priority complaints.
  • Ticket creation with evidence: Produces prioritized, actionable tickets (with persona verbatim quotes, objective issue statements, and suggested fixes) and includes screenshots for every pain point.
  • Use case: Before launch or after a feature batch, test a staging URL to identify where real users will get lost, abandon flows, or misinterpret terminology, then ship only the fixes that matter.

Quick Start

Tell the agent to run an adversarial UX test on your staging URL using a persona matched to your target audience.

Frequently Asked Questions about adversarial-ux-test

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

FAQPage Schema
How do I test my staging environment for real UX friction before launch?

To test staging for real UX friction, roleplay an adversarial, tech-resistant persona browsing core workflows to surface usability failures. The test captures screenshots and console errors, then applies a pragmatism filter to classify issues before creating actionable tickets.

What is an adversarial persona in usability testing?

An adversarial persona in usability testing is an intentionally difficult, tech-resistant user profile used to stress navigation, comprehension, and onboarding. It helps identify genuine conversion friction and accessibility failures by simulating the hardest possible user interactions.

How do I separate real UX bugs from user complaints during testing?

To separate real UX bugs from user complaints, apply a pragmatism filter to classify findings into RED, YELLOW, WHITE, and GREEN categories. This filters out persona noise and low-priority complaints, ensuring only high-value usability issues become actionable tickets.

Can I use this approach to evaluate onboarding and paywall friction?

Yes, you can use this approach to evaluate onboarding, paywall, and cold-start friction. The persona-driven browsing tests core workflows on deployed or staging applications to identify exactly where users abandon flows or misinterpret terminology.

What is the best way to document accessibility and error recovery issues?

The best way to document accessibility and error recovery issues is to collect screenshot evidence and check console errors during persona-driven browsing. This produces prioritized tickets with objective issue statements, persona quotes, and suggested fixes.