ios-debugger-agent
Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
97
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 a strong skill description that clearly communicates specific capabilities (build, run, debug, UI inspection, log capture) tied to a distinct tool (XcodeBuildMCP) and platform (iOS simulator). It includes an explicit trigger clause with natural user-facing terms and is highly distinguishable from other skills due to its specific tooling and platform focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: build, run, launch, debug, interact with simulator UI, inspect on-screen state, capture logs/console output, diagnose runtime behavior. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (build, run, launch, debug iOS projects on simulator, inspect UI, capture logs) and 'when' with an explicit 'Trigger when...' clause listing specific scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'run an iOS app', 'simulator', 'logs', 'console output', 'debug', 'build', 'runtime behavior'. These cover common variations of how users would phrase requests related to iOS development and testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'XcodeBuildMCP', the iOS/simulator focus, and the combination of build+run+UI inspection+log capture. Unlikely to conflict with generic coding or debugging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%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 skill that provides clear, actionable guidance for using XcodeBuildMCP tools. The workflow is well-sequenced with appropriate validation checkpoints, and the content is concise without sacrificing clarity. Minor improvement could come from linking to external references for advanced scenarios, but the current size doesn't strictly require it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what simulators or Xcode are, assumes Claude knows iOS development concepts, and every section provides only the necessary tool names, parameters, and sequencing without filler. | 3 / 3 |
Actionability | Every step references specific MCP tool names with exact parameters (e.g., `projectPath`, `simulatorId`, `captureConsole: true`). The guidance is concrete and directly executable—Claude knows exactly which tool to call and with what arguments at each step. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced (discover → set defaults → build/run) with explicit validation checkpoints: verifying the app launched via `describe_ui` or `screenshot` before proceeding, checking build errors before UI interaction, and a feedback loop for build failures (retry with `preferXcodebuild: true` or escalate). | 3 / 3 |
Progressive Disclosure | The content is well-organized into logical sections (Core Workflow, UI Interaction, Logs, Troubleshooting) and is appropriately sized for a single file. However, there are no references to external files for deeper topics like advanced debugging scenarios or a full tool reference, which could help if the skill grows. | 2 / 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.
- Repository
- Dimillian/Skills
- Commit
05ba982
- 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.