xcodebuildmcp-cli
Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
Install with Tessl CLI
npx tessl i github:getsentry/XcodeBuildMCP --skill xcodebuildmcp-cli90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 solid skill description that clearly identifies its niche (Apple platform development via XcodeBuildMCP CLI) and includes an explicit 'Use when' clause with good trigger terms. The main weakness is that the capabilities are listed parenthetically rather than as fully elaborated concrete actions, making it slightly less specific than ideal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists domain (iOS/macOS/watchOS/tvOS/visionOS) and some actions (build, test, run, debug, log, UI automation) but these are parenthetical and not fully elaborated as concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both what (XcodeBuildMCP CLI for Apple platform development) and when (explicit 'Use when' clause with specific triggers for iOS/macOS/watchOS/tvOS/visionOS work and development actions). | 3 / 3 |
Trigger Term Quality | Includes natural platform names users would say (iOS, macOS, watchOS, tvOS, visionOS) plus common development actions (build, test, run, debug) that developers naturally use when requesting help. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Apple platform development with XcodeBuildMCP CLI; the specific platform names and tool reference make it unlikely to conflict with generic coding or other platform skills. | 3 / 3 |
Total | 11 / 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 that efficiently teaches Claude to use the XcodeBuildMCP CLI through self-discovery rather than static documentation. The help-first approach is elegant and maintainable. The main weakness is the lack of explicit error handling or validation steps when installation or commands fail.
Suggestions
Add error recovery guidance for Step 1 (e.g., 'If brew install fails, check Homebrew is installed and updated')
Include a validation checkpoint after running commands (e.g., 'Verify build succeeded by checking exit code or output before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with CLI tools. No unnecessary explanations of what Xcode or simulators are; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete, executable commands for installation, verification, and discovery. The help-first discovery pattern gives Claude a clear, actionable approach rather than static documentation. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints or error recovery guidance. The 'Exit Criteria' section helps but doesn't include feedback loops for when commands fail. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines, the structure is appropriate. Clear sections with a capability overview, and the help-first discovery pattern naturally delegates detailed documentation to the CLI itself. | 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.
- 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.