usability-heuristics

Audit UI implementations against Nielsen's 10 Usability Heuristics for User Interface Design. Produces a structured issue log with severity ratings, heuristic mappings, and remediation guidance. Use when conducting heuristic evaluations, reviewing UI code for usability compliance, or auditing existing interfaces.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete GOOD/BAD code and review-flag checklists per heuristic, but it is a long monolithic document that restates familiar concepts and lacks validation checkpoints in its audit workflow. Splitting the per-heuristic detail into reference files and trimming restated definitions would lift the weaker dimensions.

Suggestions

Move the ten per-heuristic detail blocks (Definition/Key Takeaway/Examples/Review flags) into a references file and keep SKILL.md as an overview pointing to it, improving progressive disclosure and conciseness.

Add an explicit validation step to the audit workflow (e.g. verify every Critical/Major finding has Location + Evidence + Recommendation, and confirm the summary table counts match the findings) before producing the final issue log.

Trim restated heuristic definitions and Key Takeaway paragraphs that restate what Claude already knows about Nielsen's heuristics to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Mostly efficient per-section, but at ~800 lines the body repeats the same Definition/Key Takeaway/What-to-look-for/Examples/Review-flags/Cross-references structure ten times and restates concepts (e.g. full heuristic definitions) Claude already knows, so it could be tightened considerably.	2 / 3
Actionability	Each heuristic ships concrete, copy-paste-ready GOOD/BAD HTML snippets plus explicit "Review flags" checklists (e.g. "Flag form submit buttons without loading/disabled states"), fully executable and specific.	3 / 3
Workflow Clarity	The audit workflow is sequenced (checklist → per-heuristic review → Issue Log Format → priority summary), but there are no validation checkpoints or feedback loops verifying the produced issue log is complete or well-formed before reporting, capping clarity at 2.	2 / 3
Progressive Disclosure	Content is well-organized into sections, but it is a monolithic single file with no bundle references (references/, scripts/, assets/ are absent) while naming three companion skills inline — material that could be split out is kept inline rather than signaled one level deep.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, uses third-person voice, includes an explicit "Use when..." trigger clause, and carves out a clear niche distinct from the companion `laws-of-ux` skill. It satisfies every anchor at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Audit UI implementations", "Produces a structured issue log with severity ratings, heuristic mappings, and remediation guidance" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers what (audit UI against Nielsen's 10 heuristics, produce structured issue log) and when ("Use when conducting heuristic evaluations, reviewing UI code for usability compliance, or auditing existing interfaces").	3 / 3
Trigger Term Quality	Natural trigger phrases users would say ("heuristic evaluation", "usability audit", "reviewing UI code for usability compliance", "auditing existing interfaces") give good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to Nielsen's 10 Usability Heuristics with a distinct niche and explicit cross-reference to the companion `laws-of-ux` skill, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (798 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: RoleModel/rolemodel-skills
Commit: f61959b

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.