CtrlK
BlogDocsLog inGet started
Tessl Logo

ux-acceptance-tester

Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An efficient, highly actionable instruction-only skill with a clear sequenced workflow, explicit stop and recovery conditions, and a validation safeguard against false passes. No improvements needed for a self-contained tester persona.

DimensionReasoningScore

Conciseness

The body is lean and directive, assuming Claude's competence ('Act as the person described in the tester brief', 'Observe the full page... before acting') with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete, executable guidance throughout: 'Take one meaningful, user-visible action at a time', 'Use screenshots as well as accessibility information', 'do not repeat an action that has already failed twice', plus a fully specified report template.

5 / 5

Workflow Clarity

Clear sequence (observe -> act -> record -> choose next -> recover -> capture evidence -> stop) with explicit stop conditions ('goal visibly complete, interface prevents progress, or brief limit reached'), a recovery feedback loop, and a validation safeguard ('Do not convert uncertainty into a pass').

5 / 5

Progressive Disclosure

A self-contained, single-purpose skill with no external references needed, organized into clear sections (Boundaries, Run the journey, Report); no bundle files exist, so well-organized sections suffice.

5 / 5

Total

20

/

20

Passed

Description

78%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.

A clear, third-person description that states both capability and usage context with concrete actions and a distinct niche. It could add natural trigger synonyms ('acceptance test', 'user journey') and frame the 'when' as explicit user-facing triggers to reach the top anchor.

Suggestions

Add natural trigger synonyms a user would say, e.g. 'Use when the user asks for a UX acceptance test, user journey test, or black-box browser walkthrough.'

Reframe the 'when' clause from a constraint ('Use only in...') into an explicit trigger phrase so the activation condition reads as a natural user request.

DimensionReasoningScore

Specificity

Names the domain ('goal-driven, black-box UX acceptance journey in a browser') and several concrete actions ('report the path, friction, and observable outcome'), but the action set is bounded by the single purpose rather than comprehensively enumerated.

4 / 5

Completeness

Explicitly states both what ('Perform a goal-driven, black-box UX acceptance journey... and report...') and when ('Use only in an isolated tester context with a supplied start URL and brief'), though the 'when' is framed as a usage constraint rather than a natural trigger phrase.

4 / 5

Trigger Term Quality

Includes natural terms like 'UX acceptance journey', 'browser', 'start URL', and 'brief', but omits common synonyms a user might say such as 'acceptance test' or 'user journey test'.

4 / 5

Distinctiveness Conflict Risk

The 'black-box UX acceptance journey in a browser' niche is highly specific with distinct triggers, giving minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
emdash-cms/emdash
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.