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.

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/ios-simulator-skill/SKILL.md

Quality

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 iOS automation niche with concrete capabilities. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. Adding more natural user-facing trigger terms (e.g., 'Xcode', 'iPhone simulator') would also improve discoverability.

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', 'xcrun', '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 context (iOS development). Per rubric guidelines, missing 'Use when...' caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'iOS', 'simulator', 'build automation', 'accessibility testing', and 'UI navigation', but misses common user-facing terms like 'Xcode', 'iPhone', 'iPad', 'xcrun', 'xcodebuild', '.ipa', or 'App Store'. Users might say these terms naturally when needing this skill.	2 / 3
Distinctiveness Conflict Risk	The combination of iOS-specific testing, simulator management, and the mention of '21 production-ready scripts' creates a very clear niche. This is unlikely to conflict with general coding, web testing, or Android development skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

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

This skill provides a comprehensive catalog of 21 iOS simulator automation scripts with a useful quick start section and clear workflow. Its main weakness is that it reads more like API documentation than an actionable skill—it lists features and flags exhaustively but lacks concrete usage examples with expected outputs, error handling guidance, and validation checkpoints. The content could be significantly tightened by moving the detailed script catalog to a separate reference file and adding more practical examples and error recovery patterns.

Suggestions

Add concrete examples with expected output (e.g., show what screen_mapper.py actually returns, what navigator.py outputs on success vs failure) to improve actionability.

Add validation checkpoints and error recovery guidance to the Typical Workflow (e.g., 'If screen_mapper shows no elements, the app may not have loaded—wait and retry' or 'If build fails, check errors with --verbose').

Move the detailed 21-script catalog to a separate REFERENCE.md file and keep SKILL.md focused on the quick start, common patterns, workflow, and top-level navigation to the reference.

Remove the 'Key Design Principles' section or reduce it to a single line—Claude doesn't need explanations of why semantic navigation is better than pixel coordinates.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary content. The 'Key Design Principles' section explains concepts Claude already understands (what semantic navigation means, why structured data matters). The exhaustive listing of all 21 scripts with their sub-features is borderline—useful as reference but could be more compact. The final sentence ('Use these scripts directly or let Claude Code invoke them automatically...') is unnecessary filler.	2 / 3
Actionability	The Quick Start provides concrete, executable commands which is good. However, the bulk of the content is a catalog of script descriptions and option flags rather than executable guidance. There are no concrete examples showing expected output, no example JSON responses, and no real usage scenarios beyond the quick start. The script descriptions are more like man page summaries than actionable instructions.	2 / 3
Workflow Clarity	The 'Typical Workflow' section provides a clear 6-step sequence, and the Quick Start is well-ordered. However, there are no validation checkpoints or error recovery steps. For operations like simctl_delete (destructive) or build_and_test (multi-step), there's no guidance on what to do when things fail. The workflow is linear with no feedback loops.	2 / 3
Progressive Disclosure	The Documentation section references README.md, CLAUDE.md, references/, and examples/ directories, which is good structure. However, no bundle files were provided to verify these exist, and the main SKILL.md itself is quite long (~200 lines) with all 21 script descriptions inline. The per-script details could be split into a separate reference file, keeping SKILL.md as a leaner overview with the quick start and workflow.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: 3974caa

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.