CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, applied usability framework with excellent concrete guidance, specific numeric standards, and a well-organized one-level reference bundle. It runs long for an overview (author bios, affiliate links, re-explanations of principles Claude already knows) and never states the audit workflow as an explicit sequence in the body.

Suggestions

Add an explicit ordered audit workflow in the body (e.g., 1. Run the Quick Diagnostic, 2. Apply Nielsen/Krug heuristics to flagged areas, 3. Rate each issue on the 0-4 severity scale, 4. Score 0-10 and list improvements to reach 10/10) so the sequence doesn't have to be inferred or pulled from references/audit-template.md.

Remove or trim the "About the Author" and "Further Reading" sections — biographical detail and affiliate book links don't help Claude execute a usability audit.

Cut the "Why it works" paragraphs and "Core Principle" restatements; keep only the applied tables, copy patterns, and examples, and push the fuller treatment into references/krug-principles.md to slim the SKILL.md overview.

DimensionReasoningScore

Conciseness

The bulk is dense applied guidance (tables, before/after copy patterns), but there is unnecessary material: a two-paragraph "About the Author" section ("Steve Krug is a usability consultant who has been helping companies... since the 1990s"), affiliate-tagged "Further Reading" links, "Why it works" paragraphs re-explaining well-known principles, and a "Core Principle" section that repeats the intro ("Don't Make Me Think" appears as both section thesis and restated foundation). Not 2 because most sections are high-signal rather than padded; not 4 because the biographical and explanatory material is clearly trimmable.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: an explicit output protocol ("rate them 0-10... Always provide the current score and specific improvements needed to reach 10/10"), a concrete severity scale table (0-4 with priorities), before/after copy rewrites ("Before: 'Please kindly note that you will need to enter your password...' After: 'Enter your password to continue.'"), and specific numeric standards ("Minimum 44x44 px touch targets", "WCAG AA minimum (4.5:1 contrast ratio)"). Specific examples cover the common cases.

5 / 5

Workflow Clarity

All the pieces of an audit workflow exist — the Quick Diagnostic question table, the severity rating scale, the 0-10 scoring protocol, and method sequencing ("Heuristic evaluation | Before user testing") — but they are never assembled into an explicit ordered process with checkpoints; the actual audit procedure is delegated to references/audit-template.md. Not 4 because the sequence for conducting an evaluation must be inferred from section order rather than followed as stated steps.

3 / 5

Progressive Disclosure

All seven referenced files (krug-principles.md, nielsen-heuristics.md, audit-template.md, dark-patterns.md, wcag-checklist.md, cultural-ux.md, heuristic-conflicts.md) exist in references/, are one level deep, clearly signaled inline ("See: [references/krug-principles.md] for full Krug methodology"), and indexed in a "Reference Files" section with descriptions. Not 5 because the four Krug law sections carry roughly 150 lines of inline tables, copy patterns, and ethical boundaries that overlap with krug-principles.md, making the overview heavier than a clean split.

4 / 5

Total

15

/

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.

A strong description that clearly states capability, gives comprehensive natural trigger phrases, and explicitly fences off adjacent skills. Its only weakness is that the action list itself is brief (evaluate/improve) with scope conveyed as covered topics rather than concrete actions.

DimensionReasoningScore

Specificity

"Evaluate and improve interface usability using heuristic analysis" names the domain and two concrete actions, but the remainder is coverage description ("Covers Nielsens 10 heuristics, severity ratings, and information architecture") and trigger clauses rather than additional specific actions. It falls below anchor 4, which expects several distinct concrete actions listed, and clearly above anchor 2's minimal/generic actions.

3 / 5

Completeness

Explicitly answers "what" ("Evaluate and improve interface usability using heuristic analysis") and "when" ("Use when the user mentions...", "Also trigger when reviewing a design for usability issues") with concrete trigger phrases. This matches anchor 5 exactly; anchor 4 would require the when-clause to be less explicit or specific than it is here.

5 / 5

Trigger Term Quality

Nine natural quoted trigger phrases ("usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", "usability testing") plus contextual triggers ("improving form completion rates", "evaluating information architecture and navigation") give comprehensive coverage including synonyms and phrasings users would actually say. Not below 5 because no common variation of the request is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (usability heuristic evaluation) with distinct trigger terms, plus explicit disambiguation against neighbors: "For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology." Minimal conflict risk; no anchor below fits better.

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

valeriibeck-star/claude-skills

Path

skills/ux-heuristics/SKILL.md

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.