agentsclimarketplace

Auditing website usability

Skill qte77/claude-code-plugins/plugins/website-audit/skills/auditing-website-usability

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install
npx -y skills add qte77/claude-code-plugins --skill auditing-website-usability

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.

SKILL.md

3.0 KB, as published. Nobody here has run it

Website Usability Audit

Target: $ARGUMENTS

Conducts focused usability audits and generates implementable UX fixes. Complements auditing-website-accessibility (WCAG compliance) with UX-focused analysis. No overlap: accessibility handles ARIA/contrast/keyboard; this handles task completion, friction, and clarity.

Audit Areas

Forms

  • Smart defaults and field reduction
  • Logical grouping and progressive disclosure
  • Inline validation with helpful messaging

Navigation

  • Information architecture and menu depth (target: <3 levels)
  • Mobile usability and touch targets
  • Breadcrumbs, search, and task completion paths

Input Validation

  • Real-time feedback and error prevention
  • Clear error messages with recovery guidance
  • Submission confirmation

Microcopy

  • Button labels, form hints, and instructional text
  • Error message clarity and actionability
  • User confidence messaging

Workflow

  1. Identify scope from $ARGUMENTS (URL, file, or directory)
  2. Audit task flows - map primary user journeys, identify friction
  3. Inspect forms - field count, grouping, validation behavior
  4. Review navigation - menu depth, mobile patterns, findability
  5. Evaluate microcopy - labels, errors, guidance text
  6. Classify findings by impact on task completion
  7. Generate fixes with specific code changes

Output Format

Findings

CRITICAL (Task Completion Blockers)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
  Fix: [Specific code/design change]
  Metric: [What improves - conversion, completion, error rate]

OPTIMIZATIONS (Friction Reduction)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
  Fix: [Specific code/design change]
  Metric: [What improves]

Implementation Checklist

- [ ] [Fix description] - Impact: [High/Medium/Low]

Group fixes by: Forms, Navigation, Validation, Microcopy.

Rules

  • Prioritize task-completion blockers before friction reduction
  • Every finding must include a specific, implementable fix
  • No time estimates -- prioritize by impact only
  • Defer WCAG/accessibility concerns to auditing-website-accessibility
  • Keep output concise: findings + fixes + checklist only

Further Reading

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.