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.

63

Quality

75%

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

50%

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 routing logic and a few concrete patterns, but it is weakened by heavy repetition of the same routing targets and by references that point to files absent from the local bundle. Consolidating redundant sections and ensuring referenced files exist would lift its scores.

Suggestions

Consolidate the redundant routing presentations — the Quick Reference table, .dot decision tree, numbered list, Automated Scanning, and Example Invocations all repeat the same destinations; keep one canonical routing table and a short decision tree.

Bundle or verify the referenced files (skills/accessibility-diag.md, skills/ux-flow-audit.md, skills/watchos-a11y.md) so progressive-disclosure navigation resolves to real content rather than missing cross-suite paths.

Expand the inline actionable guidance (e.g., more concrete code snippets like the three in Critical Patterns) so the body carries executable value rather than deferring nearly everything to external files.

DimensionReasoningScore

Conciseness

Mostly efficient and avoids explaining concepts Claude already knows, but the same routing target ('skills/accessibility-diag.md') is repeated across the Quick Reference table, the .dot decision tree, the numbered list, the Automated Scanning section, and Example Invocations — repetition that could be consolidated.

2 / 3

Actionability

Routing targets are specific (named files, agents, slash commands) and the Critical Patterns section gives three concrete Swift APIs, but the bulk of remediation guidance is deferred to referenced files, leaving the body itself light on executable instruction.

2 / 3

Workflow Clarity

The classify-then-route flow is sequenced via a decision tree and numbered list, but presenting the routing four redundant ways introduces mild ambiguity about the canonical path, and no validation checkpoints are present.

2 / 3

Progressive Disclosure

Sections are well-organized and references are clearly signaled one level deep, but the referenced files (skills/accessibility-diag.md, ux-flow-audit.md, watchos-a11y.md) are not present in this skill's bundle — navigation resolves to missing external paths.

2 / 3

Total

8

/

12

Passed

Description

100%

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, concise description that states concrete capabilities, includes a natural 'Use when...' trigger with domain-specific keywords, and carves out a distinct accessibility niche. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names multiple concrete actions and sub-areas — 'fixing or auditing ANY accessibility issue — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review' — listing several specific capabilities rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' ('fixing or auditing ANY accessibility issue') and 'when' (the 'Use when...' clause), with third-person trigger voice and no over-claims.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say (VoiceOver, Dynamic Type, color contrast, touch targets, WCAG, App Store accessibility review) with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear accessibility niche with distinct triggers (VoiceOver, WCAG, App Store review) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.