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
89%
Does it follow best practices?
Impact
96%
6.85xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly addresses both what the skill does and when to use it, and occupies a clearly distinct niche. The description is concise yet comprehensive without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: touch gestures, text input, hardware buttons, screenshots, video recording, and accessibility inspection. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (iOS Simulator automation using AXe CLI for specific actions) and 'when' (explicit 'Use when...' clause plus a 'Triggers on...' clause listing specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'iOS Simulator', 'AXe CLI', 'tap/swipe/gesture', 'screenshots', 'video recording', 'accessibility testing', 'UI tests'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: iOS Simulator automation via AXe CLI. The combination of the specific tool (AXe CLI) and platform (iOS Simulator) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable reference skill with excellent conciseness and concrete executable examples throughout. Its main weaknesses are the lack of error handling/validation guidance in automation workflows and the fact that all content is inline rather than using progressive disclosure for the more detailed sections. The content would benefit from adding error checking patterns and splitting detailed reference material into separate files.
Suggestions
Add error handling guidance for common failure modes (e.g., element not found, simulator not booted, tap on wrong coordinates) with validation patterns like checking axe exit codes or verifying UI state after actions.
Consider splitting the gesture presets table, video recording details, and key code references into a separate REFERENCE.md, keeping SKILL.md as a concise overview with links to detailed material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. No unnecessary explanations of what iOS Simulator is, what accessibility APIs are, or how CLI tools work. Every section delivers commands directly with minimal prose. | 3 / 3 |
Actionability | Every section provides fully executable, copy-paste ready bash commands with concrete examples. The commands include specific flags, values, and realistic usage patterns like form filling and scroll-to-find workflows. | 3 / 3 |
Workflow Clarity | The automation patterns section shows clear multi-step sequences (form filling, scroll-to-find), but there are no validation checkpoints or error handling guidance. For automation tasks that can fail silently (e.g., tap on non-existent element, failed screenshot), missing feedback loops and error recovery is a gap. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from installation to advanced patterns. However, at ~120 lines it's getting long for a SKILL.md; the gesture presets table, detailed video options, and automation patterns could be split into referenced files to keep the overview leaner. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- 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.