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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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 a clear sequenced workflow and well-structured single reference, though it is moderately verbose in places. Conciseness is the only area with meaningful room to tighten.

Suggestions

Trim the inline markdown report template and the longest lists (moderation principles, anti-patterns, failure patterns) to the highest-signal items; consider moving the full report template into the reference file.

Consider relocating the complete report scaffold to references/task-script-patterns.md or a second reference, keeping SKILL.md as a lean overview of synthesis steps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's prior knowledge, but the full report template and the long moderation/failure-pattern lists could be tightened, so it does not reach the lean level-3 anchor.	2 / 3
Actionability	Concrete, copy-ready guidance throughout — sample sizes (5–8, 15–30), per-segment timing, severity tiers, output filenames, and good/bad task-framing examples — meeting the fully-actionable anchor for an instruction-only skill.	3 / 3
Workflow Clarity	A clear 5-phase framework and 10-step workflow with explicit feedback loops — pilot-then-refine, synthesize-during, and re-test after fixes — matching the checkpoint-with-recovery anchor.	3 / 3
Progressive Disclosure	An overview body with one clearly-signaled, one-level-deep reference (references/task-script-patterns.md, verified to exist), matching the well-organized multi-file anchor.	3 / 3
	Total	11 / 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, trigger-rich, complete, and clearly distinct from neighboring research skills, using appropriate third-person voice. It is somewhat verbose for a frontmatter description, but no description-rubric dimension penalizes verbosity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'test design, task scripts, moderation, observation, and findings synthesis' — matching the multi-action anchor; not the level below, which would name only a domain and some actions.	3 / 3
Completeness	Explicitly states both what it does (test design through findings synthesis) and when to use it ('Use this skill whenever the user wants to test usability...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Broad coverage of natural terms users would say — 'usability test', 'moderated test', 'think aloud', 'prototype testing', 'design validation' — beyond the partial-coverage level 2 anchor.	3 / 3
Distinctiveness Conflict Risk	A clear usability-testing niche with distinct trigger phrases and explicit boundary against ux-research/cro-optimization, making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 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
Commit: f1bc195

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