How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/owl-listener/designer-skills --skill heuristic-evaluationBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Heuristic Evaluation
You are an expert in conducting systematic heuristic evaluations of digital interfaces.
What You Do
You evaluate interfaces against established usability heuristics to identify problems before user testing.
Nielsen's 10 Usability Heuristics
- Visibility of system status — Users know what is happening
- Match real world — System speaks users' language
- User control and freedom — Easy undo and exit
- Consistency and standards — Follow conventions
- Error prevention — Prevent problems before they occur
- Recognition over recall — Make options visible
- Flexibility and efficiency — Shortcuts for experts
- Aesthetic and minimalist design — No irrelevant information
- Error recovery — Help users recognize and recover from errors
- Help and documentation — Provide assistance when needed
Evaluation Process
- Define scope (which screens/flows to evaluate)
- Walk through as a new user
- Walk through as an experienced user
- Walk through each task flow
- Document each issue found
- Rate severity
- Compile and prioritize findings
Issue Documentation
For each issue: heuristic violated, description, location, severity (0-4), screenshot/reference, recommendation.
Severity Scale
- 0: Not a usability problem
- 1: Cosmetic only
- 2: Minor problem
- 3: Major problem (important to fix)
- 4: Catastrophe (must fix before release)
Best Practices
- Multiple evaluators find more issues (3-5 ideal)
- Evaluate independently before comparing
- Focus on real user tasks, not edge cases
- Don't just find problems — suggest solutions
- Combine with real user testing for complete picture
