CtrlK
BlogDocsLog inGet started
Tessl Logo

ux-ui-audit

Audit or critique an existing digital product artifact or flow and return evidence-backed, severity-calibrated findings. Trigger on "audit this", "critique this screen", "review this flow", "usability review", "heuristic evaluation", or "find UX issues" when inspectable evidence is available. Use dashboard-redesign for dashboard redesigns and design-system-review for system-wide library reviews. Do not use for greenfield design.

92

1.93x
Quality

91%

Does it follow best practices?

Impact

91%

1.93x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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, highly actionable audit process: a clear sequenced workflow with validation checkpoints and a pre-delivery checklist, supported by well-signaled one-level-deep reference files that all exist. The only minor gap is conciseness, where a recap checklist and the inline worked-example block add some redundancy.

DimensionReasoningScore

Conciseness

The body is dense procedural guidance that assumes Claude's competence (it does not re-explain UX, WCAG, or library basics), but the closing "Quality bar" section recapitulates several earlier points and the full worked-example markdown block adds length that could be trimmed, keeping it just short of fully lean.

4 / 5

Actionability

For an instruction-only skill the guidance is highly actionable: concrete evidence-recording formats (`location -> user action or condition -> observed response -> consequence`), an evidence register schema, a journey-map pattern, an exact severity scale (S0-S3 + Opportunity), and a copy-paste-ready finding template with a worked example.

5 / 5

Workflow Clarity

A clear 9-step sequence (Frame, Evidence map, Trace, Lenses, Validate, Synthesize, Calibrate, Recommend, Report) is paired with explicit validation checkpoints (state assumptions, label evidence quality, "Needs verification" handling) and a pre-delivery "Quality bar" checklist; the destructive/batch cap does not apply since this is a read-only diagnostic skill.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that signals eight one-level-deep reference files, each with conditional reading guidance (e.g. "Read [references/ai-experience.md] only when AI ... affects the experience"), and all referenced paths resolve to real files in ./references/ with no nested references.

5 / 5

Total

19

/

20

Passed

Description

90%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 strong overall: it clearly states what the skill does and when to use it, lists comprehensive natural trigger phrases, and draws explicit boundaries against sibling skills. The only soft spot is specificity, where the action set reduces to a single audit activity rather than several distinct concrete actions.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Audit or critique an existing digital product artifact or flow and return evidence-backed, severity-calibrated findings"), but does not list several distinct actions as the score-4 anchor requires — it is essentially one audit action plus its output characterization.

3 / 5

Completeness

It explicitly answers both what (audit/critique an existing artifact or flow and return evidence-backed, severity-calibrated findings) and when ("Trigger on ... when inspectable evidence is available"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Six natural trigger phrases users would actually say are listed ("audit this", "critique this screen", "review this flow", "usability review", "heuristic evaluation", "find UX issues"), covering synonyms comprehensively; file extensions are not applicable to this skill type.

5 / 5

Distinctiveness Conflict Risk

A clear niche (auditing existing artifacts) is paired with explicit routing to sibling skills ("Use dashboard-redesign for dashboard redesigns and design-system-review for system-wide library reviews. Do not use for greenfield design"), giving minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aditya-ariosity/ux-ui-skills
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.