usability-testing

Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task completion. Triggers on usability test, usability testing, moderated test, unmoderated test, task script, think aloud, prototype testing, user testing, design validation, task completion. Also triggers when the user has built something and wants to know if real users can use it before shipping.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 well-structured, actionable instruction skill with a clear phased workflow and a pilot/re-test feedback loop, plus one appropriately signaled reference file. It is slightly held back by minor verbosity in the report template and feedback loops that could be stated more explicitly.

Suggestions

Make validation checkpoints explicit in the Workflow (e.g., bold a 'Validate' step after the pilot and after synthesis, mirroring a validate→fix→retry pattern).

Trim the inline report template and duplicate anti-patterns; consider moving the full report skeleton into the reference file to tighten the body.

Move some of the worked task-script examples into references/task-script-patterns.md to reduce inline length and strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-organized, assuming Claude's competence (no preamble on what usability testing is), but the inline report template and some anti-patterns slightly overlap earlier guidance and could be trimmed.	4 / 5
Actionability	Highly concrete and actionable: task selection criteria, sample-size ranges, a timed session structure, severity definitions, a report template, and named output filenames — all directly usable for an instruction-only skill.	5 / 5
Workflow Clarity	Clear 5-phase framework and 10-step workflow with a pilot checkpoint ("Pilot 1-2 sessions before main batch. Refine tasks if needed") and a re-test loop; the feedback loops are present but somewhat implicit rather than explicit validate-then-retry checkpoints.	4 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled, real one-level-deep reference (references/task-script-patterns.md); the body is fairly long though, and parts of the inline report template/task examples could arguably live in the reference.	4 / 5
	Total	17 / 20 Passed

Description

96%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, comprehensive description that clearly states capabilities and includes an extensive set of natural trigger terms plus a scenario clause. The only minor gap is the absence of explicit boundary contrast with sibling research skills within the description itself.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "test design, task scripts, moderation, observation, and findings synthesis" — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (first sentence) and 'when' ("Use this skill whenever... Triggers on... Also triggers when...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms with synonyms ("usability test/testing", "moderated/unmoderated test", "user testing", "prototype testing", "think aloud", "task completion") plus a realistic scenario phrasing users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (usability testing) with distinct triggers and minimal conflict risk, but the description alone does not contrast against adjacent research skills (ux-research, cro-optimization), leaving minor overlap with 'user testing'/'design validation'.	4 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/usability-testing/SKILL.md
Commit: a67dd34

Reviewed: 8 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.