CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

96

6.85x
Quality

95%

Does it follow best practices?

Impact

96%

6.85x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

90%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, executable CLI reference that is lean and highly actionable, with useful automation patterns; it loses a little on workflow validation and on progressive disclosure since everything lives in one file with no external references.

Suggestions

Add an explicit validation/verification checkpoint to the form-filling and screenshot-after-action patterns (e.g. assert the expected element appears via describe-ui before proceeding) to lift workflow clarity.

Since the file exceeds 50 lines, consider moving the full Gesture Presets table and/or per-flag reference into a references/ file and signaling it from SKILL.md to demonstrate one-level-deep progressive disclosure.

De-duplicate the Quick Start tap/type/gesture examples against the dedicated sections, or trim Quick Start to a single end-to-end example, to remove minor token redundancy.

DimensionReasoningScore

Conciseness

The body is lean and almost entirely executable code with terse section intros; it assumes Claude's competence and avoids explaining what a simulator or HID is, though the Quick Start slightly duplicates commands detailed later.

5 / 5

Actionability

Commands are copy-paste ready with real flags and values (e.g. 'axe swipe --start-x 100 --start-y 300 --end-x 300 --end-y 100 --udid $UDID') and cover the common cases comprehensively.

5 / 5

Workflow Clarity

The Automation Patterns section sequences multi-step recipes and the scroll-to-find loop has a checkpoint, but most patterns (form filling, screenshot-after-action) lack explicit validation/error-recovery steps, so it sits below the 5-anchor.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections in a single file with no bundle files present; it exceeds the simple-skill (<50 line) exception yet has no references to signal, placing it just below the well-signaled-references 5-anchor.

4 / 5

Total

18

/

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 that names concrete capabilities, gives explicit 'Use when' and 'Triggers on' guidance, and occupies a clearly distinct niche with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists six concrete capabilities ('touch gestures, text input, hardware buttons, screenshots, video recording, and accessibility inspection'), matching the comprehensive-coverage anchor rather than the 4-anchor which expects minor gaps.

5 / 5

Completeness

Explicitly states what it does and when to use it via 'Use when automating iOS Simulator interactions...' and 'Triggers on...', matching the anchor requiring concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Includes natural user phrases with synonyms ('iOS Simulator automation, AXe CLI usage, simulator tap/swipe/gesture commands, or accessibility testing tasks'); file extensions are not applicable to a CLI tool, so coverage is comprehensive.

5 / 5

Distinctiveness Conflict Risk

The iOS Simulator + AXe CLI niche is narrow with distinct triggers, giving minimal overlap with other skills; not the 4-anchor since triggers are unmistakably specific.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.