xcodebuildmcp
Official skill for XcodeBuildMCP. 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 xcodebuildmcp90
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) and includes an explicit 'Use when' clause with relevant platform triggers. The main weakness is that the capability list uses terse keywords rather than fully descriptive actions, which slightly reduces specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists domain (iOS/macOS/watchOS/tvOS/visionOS) and some actions (build, test, run, debug, log, UI automation), but these are brief keywords rather than fully described concrete actions. | 2 / 3 |
Completeness | Explicitly answers both what ('XcodeBuildMCP' for Apple platform development with build/test/run/debug/log/UI automation) and when ('Use when doing iOS/macOS/watchOS/tvOS/visionOS work'). | 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 clear niche targeting Apple platform development with Xcode; the specific platform names and 'XcodeBuildMCP' branding make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 efficiently communicates how to use XcodeBuildMCP tools. It excels at workflow clarity with explicit sequencing and context establishment. The main weakness is the lack of concrete examples showing actual tool calls or expected outputs, which would make the guidance more immediately actionable.
Suggestions
Add a concrete example showing a typical tool call sequence (e.g., session_show_defaults output followed by a build-and-run call)
Include an example of what failure reporting should look like per Step 3 requirements
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude knows what Xcode, simulators, and build tools are. No unnecessary explanations of basic concepts; every section adds actionable value. | 3 / 3 |
Actionability | Provides clear guidance on tool usage patterns and workflow steps, but lacks concrete code examples or specific command syntax. Instructions like 'Call session_show_defaults' are clear but not copy-paste executable. | 2 / 3 |
Workflow Clarity | Clear three-step workflow with explicit sequencing. Step 1 establishes context before actions, Step 2 handles tool availability issues with a clear fix path, and Step 3 defines reporting requirements including failure handling. | 3 / 3 |
Progressive Disclosure | Well-structured overview with capabilities listed upfront, clear external reference to configuration documentation, and appropriately concise for a tool integration skill that delegates to MCP tools. | 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.