adversarial-ux-test

Simulate hostile user behavior to identify and triage UX friction points.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies hidden friction, confusing terminology, and accessibility issues by simulating a frustrated, non-technical user who is determined to find flaws in your product.

Core Features & Use Cases

  • Adversarial Persona Generation: Creates a specific, grumpy user profile tailored to your product's target audience.
  • Friction Analysis: Systematically tests core workflows, error recovery, and readability from the perspective of a user who hates technology.
  • Pragmatism Filter: Separates genuine UX bugs and accessibility failures from subjective user complaints, ensuring you only act on high-impact issues.

Quick Start

Run an adversarial ux test on the staging site using a grumpy persona for a non-technical user.

Frequently Asked Questions about adversarial-ux-test

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

FAQPage Schema
How do I simulate hostile user behavior to find UX friction points?

You can simulate hostile user behavior by generating an adversarial, frustrated persona to systematically test your web application's workflows and error recovery. This identifies UX friction points and filters findings into actionable tickets based on severity.

What is adversarial UX testing and how does it work?

Adversarial UX testing evaluates product interfaces through persona-driven testing, accessibility checks, and workflow analysis. It creates a specific, grumpy user profile tailored to your target audience to uncover hidden friction, confusing terminology, and accessibility issues.

How do I separate real accessibility failures from subjective user complaints during QA?

To separate real accessibility failures from subjective complaints, apply a pragmatism filter during persona-driven testing. This filter evaluates findings against objective usability standards and severity, ensuring you only act on high-impact issues.

Can I use a non-technical persona to test core workflows on a staging site?

Yes, you can use a non-technical persona to test core workflows on a staging site. The skill generates a grumpy user profile tailored to your product's audience to systematically evaluate interface friction from a hostile, non-technical perspective.

How do I triage UX friction points into actionable product tickets?

You triage UX friction points into actionable product tickets by filtering persona-driven testing results based on severity and objective usability standards. This pragmatism filter ensures only high-impact issues are converted into actionable development tasks.