Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Heuristic Evaluation

ASecurity

Conduct expert heuristic evaluations using Nielsen's heuristics and domain-specific criteria.

158 stars
0 votes
0 copies
0 views
Added 10/6/2026
documentationtestinggitdocumentation

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add NVlabs/Skill2Env --skill heuristic-evaluation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Heuristic Evaluation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Heuristic Evaluation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-heuristic-evaluation/badge)](https://www.skillsdirectory.com/skills/nvlabs-heuristic-evaluation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: heuristic-evaluation
description: Conduct expert heuristic evaluations using Nielsen's heuristics and domain-specific criteria.
---
# 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
1. **Visibility of system status** — Users know what is happening
2. **Match real world** — System speaks users' language
3. **User control and freedom** — Easy undo and exit
4. **Consistency and standards** — Follow conventions
5. **Error prevention** — Prevent problems before they occur
6. **Recognition over recall** — Make options visible
7. **Flexibility and efficiency** — Shortcuts for experts
8. **Aesthetic and minimalist design** — No irrelevant information
9. **Error recovery** — Help users recognize and recover from errors
10. **Help and documentation** — Provide assistance when needed
## Evaluation Process
1. Define scope (which screens/flows to evaluate)
2. Walk through as a new user
3. Walk through as an experienced user
4. Walk through each task flow
5. Document each issue found
6. Rate severity
7. 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

Attribution

NVlabsNVlabs
View sourceSee grades on GitHubMore from NVlabs →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

Architecture Diagram Creator

Create comprehensive HTML architecture diagrams with data flows, business context, and system architecture.

6661 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in W...

1798860 votes
View all in documentation →