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.

75

1.25x
Quality

79%

Does it follow best practices?

Impact

69%

1.25x

Average score across 2 eval scenarios

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

63%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 router with excellent progressive disclosure and a clear routing workflow, but it is hampered by triple repetition of the same routing information and limited inline executable guidance. Consolidating the redundant routing presentations would meaningfully improve token efficiency.

Suggestions

Collapse the Example Invocations section into the Quick Reference table or Decision Tree — having all three repeat "→ See skills/accessibility-diag.md" is the main source of padding.

Pull one or two of the most common fixes (e.g. a VoiceOver label snippet, a Dynamic Type scaling example) inline from accessibility-diag.md so the skill is actionable without always jumping to another file.

Prune the Decision Tree edges that all terminate at the same node, or group them under a single labeled branch, to reduce graph verbosity.

DimensionReasoningScore

Conciseness

Mostly efficient as a router, but the same routing is restated three ways — a 24-row Quick Reference table, a ~16-edge Decision Tree, and 15 Example Invocations nearly all pointing to skills/accessibility-diag.md — which is noticeable padding that could be tightened.

3 / 5

Actionability

Gives concrete routing targets (specific file paths and named agents) plus a few concrete APIs in Critical Patterns (e.g. `Image(decorative:)`, `accessibilityInputLabels()`), but the bulk of executable guidance lives in referenced files rather than inline, leaving it incomplete.

3 / 5

Workflow Clarity

The Decision Tree and numbered routing list (1–7) give a clear, unambiguous sequence for matching an issue type to a destination, with no destructive or batch operations requiring validation checkpoints.

4 / 5

Progressive Disclosure

References are one level deep and well-signaled across the Quick Reference table and Decision Tree, with content appropriately split into skills/accessibility-diag.md, skills/ux-flow-audit.md, and skills/watchos-a11y.md, making navigation easy.

5 / 5

Total

15

/

20

Passed

Description

95%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 a strong, trigger-rich activation hook that clearly states both purpose and use conditions with natural user keywords. Its only weak spot is relying on two generic verbs (fixing/auditing) rather than naming more distinct actions.

DimensionReasoningScore

Specificity

Enumerates concrete domains ("VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review") but relies on only two action verbs ("fixing or auditing"), leaving minor gaps in action specificity rather than fully comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ("fixing or auditing ANY accessibility issue") and when ("Use when fixing or auditing ANY accessibility issue") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural keywords users would actually say — "VoiceOver", "Dynamic Type", "color contrast", "touch targets", "WCAG", "App Store accessibility review" — covering the domain with its common synonyms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear accessibility niche with distinct triggers (VoiceOver, WCAG, Dynamic Type, App Store review) and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation15 / 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.