axiom-accessibility

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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

67%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, concrete routing decisions, and genuinely executable pattern guidance, weakened by four-fold restatement of the same routing and references to bundle files that are absent from the provided skill directory.

Suggestions

Collapse the redundant routing: keep the Quick Reference table and one decision representation, and drop the near-duplicate numbered list or Example Invocations section to recover tokens.

Add the referenced bundle files (skills/accessibility-diag.md, skills/ux-flow-audit.md, skills/watchos-a11y.md) to the skill directory, or rewrite the body so it is self-contained instead of pointing at missing files.

Expand the single Critical Patterns section — the only part with executable code-level guidance — to cover a few more of the enumerated accessibility areas, so the overview itself carries actionable value rather than only routing.

Dimension	Reasoning	Score
Conciseness	The body is a router that avoids over-explaining concepts, but the same routing is restated four times — Quick Reference table, dot decision tree, numbered list, and Example Invocations — which is redundant padding. It is not a 4 because the redundancy is more than minor trimming, and not a 2 because each section is individually lean with no concept-teaching bloat.	3 / 5
Actionability	Concrete routing decisions (table, decision tree, example utterances) plus executable Swift guidance in Critical Patterns ('Image(decorative:)', 'accessibilityInputLabels()', 'accessibilityDifferentiateWithoutColor') give mostly actionable direction. It is not a 5 because the bulk of 'action' is deferred to referenced files that are not present in the bundle, leaving gaps.	4 / 5
Workflow Clarity	The decision tree and numbered routing list sequence 'what type? -> which reference' clearly, and no destructive/batch operation is involved so the validation cap does not apply. It is not a 5 because the skill is a routing hub over 50 lines without explicit feedback-loop checkpoints, though none are strictly required here.	4 / 5
Progressive Disclosure	References are clearly signaled and one level deep (table rows, 'See ...'), and the body is organized into navigable sections. It is not a 5 because the referenced files (skills/accessibility-diag.md, ux-flow-audit.md, watchos-a11y.md) do not exist in the bundle, and the overview repeats routing rather than being a lean pointer.	4 / 5
	Total	15 / 20 Passed

Description

100%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, third-person description with an explicit 'Use when ...' trigger and a comprehensive list of concrete accessibility sub-areas users would naturally name. It clearly answers both what the skill does and when to invoke it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capability areas — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review — under the concrete verbs 'fixing or auditing', giving comprehensive coverage. It is not a 4 because the coverage is broad and specific rather than having only minor gaps.	5 / 5
Completeness	It explicitly answers both 'what' ('fixing or auditing ANY accessibility issue') and 'when' via a 'Use when ...' clause with concrete enumerated trigger phrases. It is not a 4 because both halves are explicit and concrete rather than merely present.	5 / 5
Trigger Term Quality	It includes the exact natural terms users say ('VoiceOver', 'Dynamic Type', 'color contrast', 'touch targets', 'WCAG', 'App Store accessibility review') with synonym coverage. It is not a 4 because virtually no common natural variation is missing.	5 / 5
Distinctiveness Conflict Risk	It carves a clear accessibility niche with distinct enumerated triggers and minimal overlap risk. It is not a 4 because the scoped 'ANY accessibility issue' phrasing plus specific terms make conflict with other skills unlikely.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CharlesWiltgen/Axiom
Path: axiom-codex/skills/axiom-accessibility/SKILL.md
Commit: 28c2f56

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.