CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

axe-ios-simulator

iOS Simulator automation using AXe CLI for touch gestures, text input, hardware buttons, screenshots, video recording, and accessibility inspection. Use when automating iOS Simulator interactions, writing UI tests, capturing screenshots/video, or inspecting accessibility elements. Triggers on iOS Simulator automation, AXe CLI usage, simulator tap/swipe/gesture commands, or accessibility testing tasks.

92

6.85x
Quality

91%

Does it follow best practices?

Impact

96%

6.85x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-organized command reference with essentially no padding. The main improvement opportunities are removing duplicate examples between Quick Start and later sections, adding state verification to the fixed-delay patterns, and offloading exhaustive flag/keycode reference material to a separate file.

Suggestions

Trim duplicate examples: the tap and gesture examples in Quick Start repeat verbatim in Touch & Gestures and Gesture Presets — keep Quick Start to one command per capability.

Add verification to the timing-based patterns: replace fixed --pre-delay waits in wait-then-tap and form-filling with a describe-ui check confirming the target element is present before tapping/typing.

Move exhaustive reference material (HID keycode table, full flag documentation for swipe/record-video) into a references/ file and link it from SKILL.md to keep the main file a lean overview.

DimensionReasoningScore

Conciseness

The body is almost entirely executable commands with terse comments and no concept explanations Claude already knows. Minor duplication (e.g., "axe tap -x 100 -y 200" and "gesture scroll-down" appear in both Quick Start and their dedicated sections) keeps it just below the lean 5 anchor.

4 / 5

Actionability

Every example is copy-paste-ready bash with real flags (e.g., "echo \"Complex text\" | axe type --stdin --udid $UDID", the keycode sequences, the ffmpeg pipe), and the Automation Patterns section covers the common multi-step cases. Fully executable guidance.

5 / 5

Workflow Clarity

Sequences are clear and the scroll-to-find pattern includes an explicit validation checkpoint ("grep -q \"targetElement\" && break"), but the form-filling and wait-then-tap patterns rely on fixed delays without verifying UI state first — minor validation gaps fitting anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with eight logical sections and a preset table, appropriate for a single-binary CLI with no bundle files. At ~170 lines, exhaustive reference material (HID keycode tables, full flag documentation) could be split into a references/ file, so it fits anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

96%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 description: concrete capability list, explicit use-when and trigger clauses, and natural keywords. The only weakness is two moderately broad trigger phrases that could collide with general UI-testing skills.

DimensionReasoningScore

Specificity

Lists six concrete capability areas ("touch gestures, text input, hardware buttons, screenshots, video recording, and accessibility inspection") that comprehensively cover the CLI's command groups. Matches the 5 anchor rather than 4 because there are no gaps in capability coverage.

5 / 5

Completeness

Explicitly answers both what (first sentence enumerating capabilities) and when ("Use when automating iOS Simulator interactions..." plus an explicit "Triggers on..." clause with concrete trigger phrases). Matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Covers natural user phrasing with synonyms: "iOS Simulator automation", "AXe CLI usage", "simulator tap/swipe/gesture commands", "writing UI tests", "capturing screenshots/video", "accessibility testing". These are the phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The AXe CLI / iOS Simulator core is a clear niche with distinct triggers, but "writing UI tests" and "accessibility testing tasks" are moderately broad and could overlap with general UI-testing or accessibility-audit skills. Fits anchor 4 (mostly distinct, minor overlap risk) better than 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NeverSight/learn-skills.dev

Path

data/skills-md/0xbigboss/claude-code/axe-ios-simulator/SKILL.md

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.