CtrlK
BlogDocsLog inGet started
Tessl Logo

ux-audit-walkthrough

Minimalist UX/Interaction Audit Expert that deconstructs complex interactions through cognitive load and operational efficiency lenses. Use this skill when you need to perform a UX walkthrough audit on a Figma prototype or web interface, evaluating usability based on principles like fewer clicks, less UI elements, no hidden logic, and self-explanatory design.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is a well-structured, actionable audit methodology with concrete tool calls, a scoring framework, and a report template. Its main weaknesses are minor promotional padding around the ZIP export and the absence of an explicit error-recovery feedback loop.

Suggestions

Trim the promotional ZIP-export language (the 'strongly recommended... for stakeholder sharing and tracking improvements' note and the redundant ZIP-contents note) to improve conciseness.

Add an explicit validate-fix-retry feedback loop for the audit (e.g., re-walkthrough after identifying a breakpoint to confirm the redesign resolves the friction) to raise workflow clarity.

Tighten abstract phase directives like 'provide a streamlined redesign approach' with a concrete template or criteria so the guidance is fully executable.

DimensionReasoningScore

Conciseness

Mostly lean methodology that assumes Claude's competence (no explaining of what Figma or cognitive load is), with only minor padding such as the promotional 'strongly recommended to download... for stakeholder sharing' note and the redundant ZIP-contents note that could be trimmed.

4 / 5

Actionability

Provides concrete, executable specifics — named tools with parameters (capture_screenshot(sendToLLM=true), download_current_chat_report_zip), exact placeholder syntax [[screenshot:N]], a numeric scoring rubric (base 80, -10/-5/-2), and a full report template — though a few phase directives like 'provide a streamlined redesign approach' remain somewhat abstract.

4 / 5

Workflow Clarity

Clear sequenced phases (Pre-Flight → Phase 1-4) with checkpoints (screenshot 'Verify result' step, 'Logic Integrity' breakpoint callout), but lacks an explicit validate-fix-retry feedback loop, keeping it below anchor 5.

4 / 5

Progressive Disclosure

Well-organized single-file methodology with clear section headers and no nested external references; appropriate as a self-contained skill, though at ~170 inline lines it slightly exceeds the under-50-line simple-skill exception that would merit a 5.

4 / 5

Total

16

/

20

Passed

Description

87%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.

The description is strong: it explicitly covers both what the skill does and when to use it, with concrete audit principles and distinct triggers. The only mild weakness is that the stated actions are variations of a single composite activity rather than multiple distinct operations.

DimensionReasoningScore

Specificity

Names the domain ('UX/Interaction Audit') and several concrete elements — 'cognitive load and operational efficiency lenses', 'fewer clicks, less UI elements, no hidden logic, and self-explanatory design' — though the actual actions collapse to one composite activity (audit/evaluate), keeping it just below the comprehensive multi-action anchor 5.

4 / 5

Completeness

Explicitly states what ('deconstructs complex interactions... evaluating usability based on principles like...') and when ('Use this skill when you need to perform a UX walkthrough audit on a Figma prototype or web interface') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('UX walkthrough audit', 'Figma prototype', 'web interface', 'usability') with good coverage, but misses common synonyms like 'usability review' or 'heuristic evaluation'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (minimalist UX/interaction auditing of Figma/web prototypes) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
AIPexStudio/AIPex
Reviewed

Table of Contents

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.