Skip to the usage guide
Heuristic Evaluationby Owl-Listener

Heuristic Evaluation Skill.

Review interface usability and document the evidence behind each finding, without presenting expert judgment as participant research.

  • UX
  • Design Guidance
Source Review · Heuristic EvaluationSKILL.md
Task UX Produces • A scoped usability-review report • Issues with their location, relevant heuristic and severity rating • Prioritized recommendations tied to evidence Before You Start An agent that can inspect the interface, a defined set of user tasks, and relevant domain constraints.
Editorial summary · source reviewed 2026-10-07 · not a generated example

01 What It Does

Heuristic Evaluation: Review Usability Systematically

Inspect user tasks against usability heuristics and report each issue with its location, severity and a recommendation.

Source-based workflowNot an execution benchmark

The Working Approach

Heuristic Evaluation reviews an interface against Nielsen's heuristics and relevant domain criteria. It starts with a defined set of screens or flows, then considers both a new user's experience and an experienced user's task path.

Each issue should have a location, violated principle, severity, evidence reference, and recommendation. The source encourages independent evaluators and later comparison. This is an expert judgment method; it can identify plausible problems but does not establish their observed frequency among real users.

Expected Deliverables

  • A scoped usability-review report
  • Issues with their location, relevant heuristic and severity rating
  • Prioritized recommendations tied to evidence
See the Example Brief

From Brief to Review

  1. 01
    Define the Review Scope

    Choose real tasks and the screens or flows they traverse.

  2. 02
    Walk the Experience

    Review as both a newcomer and an experienced user, recording concrete breakdowns.

  3. 03
    Prioritize Findings

    Assign a stated severity, reference the affected location, and propose a targeted correction.

02 When to Use It

When to Use It

Use it to inspect a defined flow before participant testing or to investigate usability concerns in existing screens.

A Good Fit

  • Before Participant TestingFind obvious usability problems while recruitment is still pending.
  • A Focused Flow ReviewProduce actionable findings for a known journey rather than a vague visual critique.

Limits to Check

  • Not User-Test EvidenceExpert findings are not observed participant behavior.
  • Judgment Requires ContextSeverity is a reasoned assessment, not an automatically measured score.

Bring These Inputs

  • Interface to ReviewProvide screens or a working flow that can be inspected.
  • User TasksDefine what newcomers and experienced users need to accomplish.
  • Domain ConstraintsIdentify important conventions and consequences of failure.

03 Decisions That Matter

Decisions That Matter

  1. Traceable Findings

    Locations and evidence make issues reproducible by the implementation team.

  2. Priorities With Reasons

    Severity encourages a distinction between cosmetic friction and task-blocking failures.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Setup

Load this task's SKILL.md from the designer-skills repository in your agent's supported skill location. No universal installer command is established by the entry file.

Upstream Source File
https://github.com/Owl-Listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/prototyping-testing/skills/heuristic-evaluation/SKILL.md

Give the agent inspectable screens or access to the flow. Findings are expert assessments, not observations from recruited participants.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use heuristic-evaluation to review this account-recovery flow. Walk it as a new and returning user, record each issue with location and heuristic, assign justified severity from the source scale, and recommend a correction. Label this expert review, not user research.

Inspect the Result

Check the actual output against these observable criteria.

  • Every issue points to an inspectable location.
  • Severity includes a task-based rationale.
  • Recommendations address the recorded issue.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
Owl-Listener
License
MIT
Reviewed Snapshot
2026-10-07 · 9a6930cf84a8
Editorial Source Summary
Inspect user tasks against usability heuristics and report each issue with its location, severity and a recommendation.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Does this require recruited participants?

No. It is an expert-review method; participant testing is a complementary activity.

Should evaluators work together first?

The source recommends independent evaluation before comparing findings.

Can it replace usability testing?

The source recommends combining it with real user testing for a fuller picture.

OpenDesign

Make Room for the Next Design Iteration.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Upstream Source File
https://github.com/Owl-Listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/prototyping-testing/skills/heuristic-evaluation/SKILL.md