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
93%
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 covers all dimensions well. It lists specific concrete actions, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it, and occupies a clearly distinct niche with the iOS Simulator + AXe CLI combination.
| 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 touch gestures, text input, etc.) and when (automating iOS Simulator interactions, writing UI tests, capturing screenshots/video, inspecting accessibility elements) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'iOS Simulator', 'AXe CLI', 'tap/swipe/gesture', 'screenshots', 'video', 'accessibility testing', 'UI tests'. These are terms users would naturally use when seeking this functionality. | 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
87%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, well-structured CLI reference skill that provides highly actionable, copy-paste ready commands organized into clear categories. Its main weakness is the lack of validation/error handling in multi-step automation workflows—the scroll-to-find loop has no failure case, and form filling has no verification that fields were actually populated. The conciseness and actionability are excellent.
Suggestions
Add error handling to the scroll-to-find pattern (e.g., exit with error message if element not found after N attempts)
Add a brief verification step to the form filling pattern (e.g., use describe-ui to confirm field content before submitting)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what iOS Simulators, accessibility APIs, and CLI tools are. No unnecessary explanations of concepts—just commands and examples. The gesture presets table is a compact reference format. | 3 / 3 |
Actionability | Every section provides copy-paste ready bash commands with concrete arguments. Examples cover real use cases (form filling, scroll-to-find, screenshot after action) with specific flags and values. Nothing is pseudocode or abstract. | 3 / 3 |
Workflow Clarity | The automation patterns section shows useful multi-step sequences (scroll to find, form filling), but there are no validation checkpoints or error handling guidance. The scroll-to-find pattern has a loop but no fallback if the element is never found after 5 attempts. For automation involving potentially fragile UI interactions, explicit error recovery would strengthen this. | 2 / 3 |
Progressive Disclosure | For a skill with no bundle files, the content is well-organized into logical sections with clear headers progressing from installation to quick start to detailed commands to automation patterns. The structure is flat and easy to navigate, appropriate for the scope of the content. | 3 / 3 |
Total | 11 / 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.
aa009ea
Table of Contents
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.