CtrlK
BlogDocsLog inGet started
Tessl Logo

adversarial-ux-test

Roleplay a hostile user to find and triage UX pain points.

52

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/dogfood/adversarial-ux-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill with a clear sequenced workflow and a mandatory triage/validation gate. Its main weakness is mild verbosity in the framing sections rather than any structural problem.

Suggestions

Trim the 'Why This Works' section and persona-color commentary to reduce token overhead while keeping the friction-category list.

Add a brief recovery note for when browser tools fail or the app is unreachable, to round out workflow validation.

Consider moving the Example Personas table and/or Tips into a reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient actionable guidance, but the 'Why This Works' section and persona-color framing ('automated mom test — but angry') add explanation that could be tightened.

3 / 5

Actionability

Highly actionable for an instruction-only skill: a fill-in rant template, 6 concrete filter criteria, good/bad persona examples, and an industry persona table; minor gaps on browser-tool usage specifics.

4 / 5

Workflow Clarity

A clear 6-step sequence with the mandatory pragmatism filter as an explicit validation gate, a 'zero complaints → regenerate persona' feedback loop, and a max-10-tickets constraint; minor validation gaps around tool failure recovery.

4 / 5

Progressive Disclosure

Well-organized with clear section headers (Steps 1-6, Tips, Example Personas, Rules) and no external references needed; over 50 lines so the simple-skill exception does not apply, but structure and navigation are good.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a distinct niche with a couple of concrete actions, but it lacks an explicit 'when to use' trigger clause and broader keyword coverage. It is solid but not comprehensive.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when reviewing a product's usability, before demos/launches, or when dogfooding reveals friction').

Broaden trigger terms to include natural synonyms users say — 'usability test', 'UX review', 'user testing', 'grumpy user test'.

Expand the action list slightly (e.g., 'generate personas, roleplay their tasks, and triage complaints into tickets') to improve specificity.

DimensionReasoningScore

Specificity

Names the domain ('UX pain points') with concrete actions ('find and triage') plus the 'roleplay a hostile user' method, but coverage is not comprehensive — no mention of personas, filtering, or ticket creation.

3 / 5

Completeness

The 'what' is clear ('Roleplay a hostile user to find and triage UX pain points') but there is no explicit 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'hostile user' and 'UX pain points' are relevant natural terms, but common variations like 'usability test', 'UX review', or 'user testing' are missing.

3 / 5

Distinctiveness Conflict Risk

The adversarial-persona UX testing niche is mostly distinct; minor overlap risk with closely related dogfood/QA skills (metadata lists related_skills: [dogfood]).

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.