qte77/auditing-website-usability
plugins/website-audit/skills/auditing-website-usability/SKILL.md
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins auditing-website-usabilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 2:52 AM39.7s1 file scanned
SKILL.md
- name:
- auditing-website-usability
- description:
- Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
- compatibility:
- Designed for Claude Code
- allowed-tools:
- Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch
- argument-hint:
- [url-or-file-path]
- stability:
- stable
- content-hash:
- sha256:0e7c6cbfc6559f5799d96568468a418ca323f0fbd15dc5ed294decd5e56874a8
- last-verified-cc-version:
- 1.0.34
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
- Identify scope from $ARGUMENTS (URL, file, or directory)
- Audit task flows - map primary user journeys, identify friction
- Inspect forms - field count, grouping, validation behavior
- Review navigation - menu depth, mobile patterns, findability
- Evaluate microcopy - labels, errors, guidance text
- Classify findings by impact on task completion
- 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
- Nielsen Norman Group — UX Research
- Usability.gov — User Interface Design
- Baymard Institute — UX Benchmarks
Related Skills
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026
qte77/researching-website-design
development
VerifiedTrustedCommunity
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
1SKILL.mdUpdated Apr 18, 2026
qte77/auditing-website-accessibility
development
VerifiedTrustedCommunity
Audits website accessibility for WCAG 2.1 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
1SKILL.mdUpdated Apr 18, 2026