CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-ux-flow

Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced audit skill with concrete grep patterns and explicit verification checkpoints. Its main shortcoming is progressive disclosure: all content is inlined in a single long file with no reference bundle, and a couple of sections (Scope, Invocation Examples) are redundant.

Suggestions

Move the 11 detection categories (Phase 2) into a references/ file (e.g. DETECTION_CATEGORIES.md) and keep SKILL.md as an overview that links to it, improving progressive disclosure.

Remove the duplicate Scope section at the end (lines 290-292) since the same scope is already stated near the top (line 10).

Consider trimming or relocating the Invocation Examples block, which mostly restates trigger phrasing already covered by the description.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (concrete grep patterns, no introductory explanations of SwiftUI/UIKit), but it carries minor trimmable redundancy such as the duplicated Scope section and the largely illustrative Invocation Examples block.

4 / 5

Actionability

Copy-paste-ready Glob/Grep patterns with exact search strings, plus per-category Pattern/Search/Issue/Fix structure and a fully specified output template give executable guidance across the common audit cases.

5 / 5

Workflow Clarity

Five phases are explicitly sequenced (Map → Detect → Reason → Cross-Reference → Score) with validation checkpoints such as "use Read to verify the surrounding context before reporting" and an evidence requirement tying Phase 3 back to the Phase 1 map.

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases, tables, and a Related section pointing to sibling skills, but everything lives inline in one ~290-line file with no bundle files, and the 11 detection categories are a natural candidate for a one-level-deep reference.

4 / 5

Total

18

/

20

Passed

Description

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

A trigger-rich, third-person description that clearly signals when to invoke the skill and names concrete UX defect categories. Its main weakness is leading with "Use when" so the capability ("what") is inferred from the trigger list rather than stated as an explicit action.

Suggestions

Lead with an explicit capability verb phrase before the trigger clause, e.g. "Detects and reports user-journey defects (dead ends, dismiss traps, missing states) in iOS apps. Use when...", so the "what" is stated, not implied.

Add a couple of lay-user synonyms (e.g. "stuck screens", "dead ends in my app") to broaden natural trigger coverage beyond the reviewer-jargon terms.

DimensionReasoningScore

Specificity

Lists several concrete defect categories ("dead-end views", "dismiss traps", "missing empty states", "broken user journeys") rather than vague language, though the actual detecting/auditing action is implied rather than enumerated.

4 / 5

Completeness

An explicit "Use when..." clause answers "when" with concrete triggers, and the defect list implies the "what" (audits UX flow defects), but the "what" is not stated as an explicit action verb phrase, keeping it just below a 5.

4 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms ("UX flow issues", "broken user journeys", "UX audit") plus specific phrases a user would say ("dismiss traps", "dead-end views") and the platform qualifier "iOS app".

5 / 5

Distinctiveness Conflict Risk

The UX-flow/journey niche is clearly distinct from general code review, with only minor overlap risk against closely related auditors (navigation, accessibility) that the body later names.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
CharlesWiltgen/Axiom
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.