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.

70

Quality

87%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear phased workflow and concrete tool guidance. Its main weakness is verbosity in the persona and export sections, which inflates the token budget without adding capability.

Suggestions

Compress the 'Role/Profile' and 'Core Philosophy' sections — Claude already understands cognitive-load concepts; keep only the four operational principles and their decision rules.

Make the Pre-Flight section mandatory-or-omit: the 'recommended but not mandatory' framing adds tokens without giving a clear instruction.

Tighten the Phase 4 export workflow: the bullet list re-explains tool behavior Claude can read from the tool description; state only the call to make and the placeholder convention.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete tool calls and templates, but padded sections — the 'Role/Profile' prose, restated philosophy, a 'recommended but not mandatory' Pre-Flight section, and the verbose export-workflow explanation — could be trimmed.

2 / 3

Actionability

It gives concrete, executable guidance: exact tool invocations like `capture_screenshot(sendToLLM=true)` and `download_current_chat_report_zip`, a `[[screenshot:N]]` placeholder convention with a worked example, and a precise scoring framework with point values.

3 / 3

Workflow Clarity

The audit is sequenced into clear phases (Pre-Flight → Phase 1–4) with an explicit per-step logging template and a screenshot re-capture verification loop serving as a validation checkpoint.

3 / 3

Progressive Disclosure

This is a single-file skill with no bundle files and no external references; content is well-organized into clearly headed sections, which per the rubric's simple-skill note warrants a top score.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that pairs concrete capabilities with an explicit trigger clause and a distinct niche. Its only weakness is the second-person phrasing, which the guidelines penalize on specificity.

Suggestions

Rewrite in third-person voice (e.g., 'Performs a UX walkthrough audit...') to match the recommended style and recover the specificity score.

Consider adding a couple more concrete output-oriented actions (e.g., 'generates a UX health score and diagnostic report') to the front of the description for an even stronger capability list.

DimensionReasoningScore

Specificity

The description names concrete actions ('perform a UX walkthrough audit', 'evaluating usability') and lists the four principles, which is comprehensive; however it uses second-person voice ('Use this skill when you need to'), which the guidelines penalize by reducing the specificity score by one.

2 / 3

Completeness

It explicitly answers both 'what' (deconstructs interactions, audits, evaluates usability) and 'when' via an explicit 'Use this skill when...' clause.

3 / 3

Trigger Term Quality

It covers natural user terms — 'UX walkthrough audit', 'Figma prototype', 'web interface', 'usability' — that a user would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The niche is clear (UX walkthrough audit on Figma prototypes / web interfaces) with distinct triggers unlikely to conflict with unrelated skills.

3 / 3

Total

11

/

12

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.