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.

95

6.85x
Quality

Does it follow best practices?

Impact

96%

6.85x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is lean and highly actionable, with well-organized sections and executable examples throughout. The only gap is workflow clarity: automation patterns lack explicit validation/verification checkpoints and error-recovery feedback loops.

Suggestions

Add explicit verification after risky or batch operations — e.g., after form filling, check the result with 'axe describe-ui' or 'axe screenshot' before declaring success.

Add a validate->fix->retry feedback loop to the scroll-to-find pattern, clarifying what to do if the element is never found (e.g., max retries, then surface the failure).

For video recording, note how to verify the recording succeeded (e.g., confirm the MP4 path is printed to stdout) before relying on the output.

DimensionReasoningScore

Conciseness

The body is almost entirely lean, executable command examples with minimal prose and no explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Commands are fully executable with concrete flags and copy-paste-ready examples, plus concrete patterns like form filling and scroll-to-find.

3 / 3

Workflow Clarity

Multi-step patterns are sequenced (scroll-to-find loop, form filling), but batch/automated operations lack explicit validation checkpoints and validate->fix->retry feedback loops, capping this at 2.

2 / 3

Progressive Disclosure

No bundle files exist; the single ~167-line body is well-organized into clear sections, which meets the bar for a simple single-file skill scoring 3 without external references.

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.

The description is strong: it enumerates concrete capabilities, provides explicit 'Use when' trigger guidance with natural keywords, and occupies a distinct niche unlikely to conflict with other skills. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'touch gestures, text input, hardware buttons, screenshots, video recording, and accessibility inspection' — matching the anchor for naming several specific capabilities.

3 / 3

Completeness

Explicitly answers both 'what' (the listed capabilities) and 'when' via 'Use when automating iOS Simulator interactions, writing UI tests, capturing screenshots/video, or inspecting accessibility elements' plus a second triggers clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'iOS Simulator automation', 'AXe CLI usage', 'simulator tap/swipe/gesture commands', 'accessibility testing', 'writing UI tests' — giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (iOS Simulator via AXe CLI) with triggers specific to that domain, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.