ios-simulator-skill
21 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/ios-simulator-skill/SKILL.mdQuality
Discovery
67%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 in specificity and distinctiveness, clearly identifying its niche in iOS app automation with concrete capabilities. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing common trigger terms users would naturally use (e.g., 'Xcode', 'iPhone', 'Swift'). Adding explicit trigger guidance and broader keyword coverage would significantly improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to test, build, or automate iOS apps, manage simulators, or run accessibility checks.'
Include additional natural trigger terms users would say, such as 'Xcode', 'iPhone', 'iPad', 'Swift', 'xctest', 'xcodebuild', '.ipa', or 'app store submission'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management.' Also mentions '21 production-ready scripts' and 'iOS app testing, building, and automation,' which are concrete and specific. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain (iOS app development). Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'iOS', 'testing', 'building', 'automation', 'simulator', 'accessibility testing', and 'UI navigation.' However, it misses common user-facing variations like 'Xcode', 'iPhone', 'iPad', 'xctest', 'xcodebuild', '.ipa', 'app store', or 'Swift' that users would naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche: iOS-specific app testing, building, and automation with simulator management. The combination of iOS + scripts + AI agent optimization makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides actionable, executable commands and good progressive disclosure through external references. Its main weaknesses are verbosity in the script catalog (listing all options for 21 scripts when --help exists) and missing validation/error-recovery steps in workflows. Trimming the per-script details and adding explicit checkpoints would significantly improve it.
Suggestions
Reduce per-script descriptions to 1-line summaries since all scripts support --help; move detailed option lists to a separate REFERENCE.md file to improve conciseness.
Add explicit validation checkpoints and error recovery guidance to the Typical Workflow (e.g., 'If health check fails, install missing dependencies; if app doesn't launch, check bundle ID with --list').
Remove the 'Key Design Principles' section or reduce it to a single line—these are implementation details Claude doesn't need explained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes significant verbosity in listing all 21 scripts with their options and descriptions. The 'Key Design Principles' section explains concepts Claude already understands (what semantic navigation means, what structured data is). The detailed per-script option lists could be replaced with '--help' references since that's already mentioned. | 2 / 3 |
Actionability | The Quick Start section provides fully executable, copy-paste-ready commands with a clear progression. Each script listing includes concrete CLI options and flags. The Typical Workflow section gives specific, runnable commands for a complete end-to-end flow. | 3 / 3 |
Workflow Clarity | The Typical Workflow provides a clear sequence of steps, but lacks explicit validation checkpoints and error recovery. For example, there's no guidance on what to do if sim_health_check fails, if the app doesn't launch, or if screen_mapper shows unexpected results. The build_and_test workflow doesn't include validation/retry loops for build failures. | 2 / 3 |
Progressive Disclosure | The skill has a clear Quick Start overview, organized script categories, and well-signaled references to README.md, CLAUDE.md, references/, and examples/ directories. Content is appropriately split with one-level-deep navigation. Each script's --help is referenced for deeper detail. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.