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

68%

Does it follow best practices?

Impact

Pending

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

50%

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 excels at specificity and distinctiveness, clearly identifying iOS app development as its domain with concrete capabilities. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The trigger terms are adequate but could include more common user vocabulary like 'Xcode' or 'iPhone'.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about iOS app testing, Xcode builds, iPhone/iPad simulators, or mobile app automation'

Include additional natural trigger terms users would say: 'Xcode', 'iPhone', 'iPad', 'xctest', 'mobile app', '.ipa files'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management'. Also quantifies with '21 production-ready scripts' and specifies the domain clearly as 'iOS app testing, building, and automation'.	3 / 3
Completeness	Describes what the skill does well but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'iOS', 'testing', 'building', 'automation', 'simulator', 'accessibility testing', but missing common user variations like 'Xcode', 'iPhone', 'iPad', 'app store', 'xctest', '.ipa', or 'mobile app'.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on iOS development with distinct triggers like 'iOS app', 'simulator lifecycle', and 'semantic UI navigation'. Unlikely to conflict with general testing or Android skills.	3 / 3
	Total	9 / 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 well-crafted skill document that efficiently catalogs 21 iOS automation scripts with actionable command-line examples. The organization is excellent with clear categorization and progressive disclosure to deeper documentation. The main weakness is the lack of explicit validation steps and error handling guidance in the workflow section, which is important for simulator and build operations that can fail.

Suggestions

Add validation checkpoints to the Typical Workflow section (e.g., 'If screen_mapper shows no elements, verify app launched successfully with --state')

Include a brief troubleshooting pattern or error recovery guidance for common failure scenarios like failed builds or unresponsive simulators

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, listing 21 scripts with their options without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations.	3 / 3
Actionability	Provides fully executable bash/python commands throughout, with specific options documented for each script. The Quick Start section is copy-paste ready and the script descriptions include concrete command-line options.	3 / 3
Workflow Clarity	The 'Typical Workflow' section provides a clear sequence but lacks explicit validation checkpoints or error recovery steps. For operations like app installation or simulator management, there's no feedback loop for handling failures.	2 / 3
Progressive Disclosure	Excellent structure with Quick Start for immediate use, organized script categories, and clear references to additional documentation (README.md, CLAUDE.md, references/, examples/). Navigation is well-signaled and one level deep.	3 / 3
	Total	11 / 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: 355d067

Reviewed: 1 day 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.