CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-accessibility

Use when fixing or auditing ANY accessibility issue — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review.

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/plugins/axiom/skills/axiom-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured router skill with clear navigation and honest anti-rationalization guidance, but it suffers from heavy internal redundancy (the same routing repeated four ways) and provides virtually no executable fixing guidance of its own. The referenced detail files are not present in this bundle, so its value depends entirely on an external suite layout.

Suggestions

Collapse the Quick Reference table, dot decision tree, numbered Decision Tree, and Example Invocations into a single routing representation (the table plus numbered list would suffice) — the current four-fold repetition wastes roughly half the body's tokens.

Expand 'Critical Patterns' with a few concrete, copy-paste-ready SwiftUI snippets (e.g., an accessibilityLabel/.accessibilityHint pairing or a Dynamic Type fixed-size detection) so the skill delivers some executable value without chasing external files.

Make the referenced paths self-contained or verify they resolve relative to the skill's install location — 'skills/accessibility-diag.md' and the cross-suite routes (axiom-watchos, axiom-tools) assume a parent layout that a standalone SKILL.md bundle does not provide.

DimensionReasoningScore

Conciseness

The same routing table is stated four times — Quick Reference table, dot decision tree, numbered Decision Tree list, and Example Invocations — which is pure redundancy across ~160 lines. Mostly functional routing content with no concept over-explanation, but clearly could be tightened to one or two representations — anchor 3, not 4 (the duplication is more than 'minor instances').

3 / 5

Actionability

Navigation is concrete (exact file paths, 'Launch accessibility-auditor agent or /axiom:audit accessibility', three real SwiftUI APIs like Image(decorative:) and accessibilityInputLabels()), but the skill contains almost no executable guidance for the actual fixing work — it delegates everything to files not present in this bundle. 'Some concrete guidance but incomplete' fits better than level 4's 'mostly executable guidance'.

3 / 5

Workflow Clarity

As a router, the single action per symptom is unambiguous (symptom → file path), and routing is not a destructive or batch operation requiring validation checkpoints. Held at 4 rather than 5 because some table rows blur scope (UX flow and watchOS routing inside an accessibility skill) and the inline-auditor fallback instructions are only sketched, leaving minor gaps.

4 / 5

Progressive Disclosure

The body is itself a pure progressive-disclosure structure: an overview with clearly signaled, one-level-deep references (skills/accessibility-diag.md, skills/ux-flow-audit.md, skills/watchos-a11y.md). Scored at 4 rather than 5 because no bundle files exist here to verify the referenced paths, and they resolve outside the skill directory (cross-suite layout), so navigation may not resolve as written.

4 / 5

Total

14

/

20

Passed

Description

73%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 strong, trigger-focused description with excellent natural keywords and an explicit 'Use when' clause. Its main weakness is that it describes the problem domain thoroughly but never states what the skill concretely does when invoked.

DimensionReasoningScore

Specificity

The only actions named are "fixing or auditing", both generic, while the six concrete terms (VoiceOver, Dynamic Type, color contrast, touch targets, WCAG, App Store review) describe topics rather than distinct capabilities. This matches 'names domain and 1-2 concrete actions' rather than level 4's 'several specific actions'.

3 / 5

Completeness

An explicit "Use when fixing or auditing ANY accessibility issue" clause answers 'when' clearly, and 'what' is stated (fixing/auditing accessibility issues), but the 'what' is thin — it never says what the skill actually provides (diagnosis reference, auditor agent). Both present with room for explicitness — anchor 4, above 3 because 'when' is explicit, below 5 because 'what' lacks concrete capability detail.

4 / 5

Trigger Term Quality

VoiceOver, Dynamic Type, color contrast, touch targets, and WCAG compliance are exactly the phrases users would naturally say, but common synonyms like "screen reader", "a11y", "Reduce Motion", and "Switch Control" are missing. Good coverage, not yet comprehensive — fits anchor 4, not 5.

4 / 5

Distinctiveness Conflict Risk

The triggers are platform-specific accessibility terms (VoiceOver, Dynamic Type, WCAG) forming a clear niche unlikely to collide with other skills. Re-reading anchor 4 ('minor overlap risk with closely related skills') — the terms here don't overlap with any adjacent domain, so 5 holds.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.