CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/mobile-a11y-test-author

Authors native mobile accessibility tests covering iOS (Accessibility Inspector, XCUITest `performAccessibilityAudit()` introduced in iOS 17, VoiceOver label/trait/hint verification) and Android (Espresso `AccessibilityChecks.enable()`, Accessibility Scanner, TalkBack traversal, `contentDescription` labelling) with WCAG-aligned checks for element labels, 44pt/48dp touch targets, contrast ratios, and focus order. Use when an iOS or Android app needs automated and manual accessibility test coverage beyond what `xcuitest-suite` or `espresso-suite` provide.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable skill body with executable code and excellent progressive disclosure. The only gap is the absence of an explicit validation/retry workflow for guiding test authoring end-to-end.

Suggestions

Add a short 'Authoring workflow' section with an explicit sequence — e.g. 1) run the audit/checks, 2) triage failures against anti-patterns, 3) suppress known false positives narrowly, 4) re-run until clean — so the test-writing process has clear validation checkpoints.

Include a 'verify locally before CI' checkpoint (Accessibility Inspector / Accessibility Scanner) with a fix-then-retry loop so failures are caught before pushing to the emulator/CI runner.

Tie the CI integration section into the workflow as a final gating step (build must pass a11y-audit and a11y-checks jobs) to make the end-to-end sequence explicit.

DimensionReasoningScore

Conciseness

Lean and efficient with no condescending explanations of concepts Claude already knows; every section (overview, core audits, CI, anti-patterns, limitations, references) earns its place and defers detail to reference files.

3 / 3

Actionability

Provides fully executable Swift (performAccessibilityAudit), Kotlin (AccessibilityChecks.enable with root-view mode), and GitHub Actions YAML for both platforms — copy-paste ready with real API calls and concrete destinations.

3 / 3

Workflow Clarity

Content is well organized by platform/section, but there is no explicit multi-step workflow with validation checkpoints or a fix-then-retry feedback loop for the test-authoring process; sequence is present but checkpoints are implicit.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with clearly signaled, one-level-deep references to references/ios-audit.md and references/android-checks.md, both of which exist and appropriately extend the core examples; navigation is easy.

3 / 3

Total

11

/

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, specific description that clearly states concrete capabilities, includes an explicit 'Use when' trigger, and disambiguates from sibling skills. No notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across both platforms — 'Authors native mobile accessibility tests', 'performAccessibilityAudit()', 'AccessibilityChecks.enable()', VoiceOver label/trait/hint verification, WCAG checks for labels, 44pt/48dp touch targets, contrast ratios, and focus order — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (authors a11y tests across iOS/Android with WCAG-aligned checks) and when via the 'Use when an iOS or Android app needs automated and manual accessibility test coverage beyond what xcuitest-suite or espresso-suite provide' clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'accessibility', 'iOS', 'Android', 'VoiceOver', 'TalkBack', 'WCAG', 'app needs accessibility test coverage' — alongside the explicit 'Use when' trigger, giving good coverage of natural phrasing.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (native mobile a11y testing) and explicitly differentiates from the nearest neighbors xcuitest-suite and espresso-suite, making misfires unlikely.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents