Skills ux-audit
📦

ux-audit

Content revision r1 Safe ⚙️ External commands

Audit UX with Heuristic Reviews

Teams miss usability issues before release. This skill guides structured UX audits with scores, critical issues, and prioritized recommendations.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "ux-audit" from https://skillstore.io/skills/dami-randle-ux-audit.md and its manifest at https://skillstore.io/api/skills/dami-randle-ux-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dami-randle-ux-audit.md Signed manifest GET /api/skills/dami-randle-ux-audit/manifest Signed lockfile GET /api/skills/dami-randle-ux-audit/lockfile

Test it

Using "ux-audit". Audit a new onboarding page before release.

Expected outcome:

  • Summary Score: Good. The structure is clear, but progress feedback is weak.
  • Critical Issue: Users may not know whether account setup is complete.
  • Recommendation: Add a visible progress indicator and a clear completion state.

Using "ux-audit". Review a settings form with save and error states.

Expected outcome:

  • Heuristic Concern: System status is unclear after saving changes.
  • Key Issue: Error messages appear far from the affected fields.
  • Recommendation: Place inline validation beside each field and keep a persistent save result message.

Using "ux-audit". Evaluate checkout flow usability for mobile users.

Expected outcome:

  • Summary Score: Fair. The flow has clear steps, but recovery paths are limited.
  • Critical Issue: Users cannot easily edit shipping details after payment review.
  • Recommendation: Add editable review sections and preserve entered data after validation errors.

Security Audit

Safe
v9 • 7/6/2026 Open versioned report

All four static findings are false positives caused by Markdown code fences and inline code references in SKILL.md. No prompt injection, data exfiltration intent, or business-logic abuse evidence was found in the reviewed file.

1
Files scanned
88
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (4)
SKILL.md:60-80 SKILL.md:80-85 SKILL.md:85-86 SKILL.md:86-87
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/dami-randle-ux-audit/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dami-randle-ux-audit/security.svg)](https://skillstore.io/skills/dami-randle-ux-audit?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dami-randle-ux-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dami-randle-ux-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dami-randle-ux-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Dami-Randle. (2026). ux-audit security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dami-randle-ux-audit/audits/9

BibTeX citation

@techreport{dami-randle-dami-randle-ux-audit-2026, author = {Dami-Randle}, title = {ux-audit security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/dami-randle-ux-audit/audits/9}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "ux-audit security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "Dami-Randle" date-released: "2026-07-06" url: "https://skillstore.io/skills/dami-randle-ux-audit/audits/9" identifiers: - type: other value: "skillstore:dami-randle-ux-audit:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Review a Feature Before Release

Find usability blockers and quick improvements before a product launch.

Improve a Design Review

Turn subjective feedback into structured findings with priorities and rationale.

Prepare Engineering Fixes

Convert interface issues into prioritized recommendations with estimated effort.

Try These Prompts

Audit a Single Page 
Use the ux-audit skill to review this page. Evaluate heuristics, visual hierarchy, interactions, and content. Return scores, critical issues, and recommendations.
Review a Component 
Audit this component for usability. Check labels, states, feedback, error handling, and consistency. Include positive patterns and prioritized fixes.
Evaluate a User Flow 
Audit this user flow from entry to completion. Identify friction, unclear status, recovery gaps, and missing guidance. Prioritize issues by user impact.
Prioritize Release Fixes 
Audit this feature using the provided goals, users, and release constraints. Rank P0 to P2 usability risks and recommend fixes with effort estimates.

Best Practices

  • Provide screenshots, user goals, and target audience details before the audit.
  • Ask for severity, priority, and effort so recommendations are actionable.
  • Review the positive patterns as well as the critical issues.

Avoid

  • Do not request a full product audit without sharing specific screens or flows.
  • Do not treat heuristic scores as a replacement for user research.
  • Do not ask for visual polish only when the goal is usability analysis.

Frequently Asked Questions

What does this skill audit?
It audits pages, components, features, and flows for usability issues and improvement opportunities.
Does it use Nielsen heuristics?
Yes. The skill evaluates work against Nielsen usability heuristics and related UX best practices.
Can it review screenshots?
Yes. It can review screenshots when the user provides the image and enough product context.
Does it test accessibility compliance?
No. It can note obvious accessibility concerns, but it does not run WCAG compliance testing.
What output should users expect?
Users should expect a summary score, heuristic scores, critical issues, recommendations, and positive patterns.
Who should use this skill?
Product managers, designers, and engineering leads can use it before releases or design reviews.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Dami-Randle/logidocs-certify/tree/main/.claude/skills/ux-audit

Ref

34f316ba14ef36c7a620fc09f2676d2429997a77

Maintenance freshness

7/18/2026

Usage

11 downloads · 196 views

File structure

📄 SKILL.md