CtrlK
BlogDocsLog inGet started
Tessl Logo

xcodebuildmcp-cli

Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

87

3.42x
Quality

81%

Does it follow best practices?

Impact

96%

3.42x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

72%Scale 1-3

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, concise skill that effectively teaches a help-first discovery pattern for the XcodeBuildMCP CLI. Its main weakness is that it leans too heavily on self-discovery without providing concrete examples of common workflows (e.g., building an iOS app, running tests on a simulator), which limits immediate actionability. Adding even one or two concrete end-to-end examples and error-handling guidance would significantly improve it.

Suggestions

Add 1-2 concrete, executable examples of common workflows (e.g., building and running an iOS app on a simulator) so Claude has copy-paste-ready patterns rather than relying entirely on --help discovery.

Add validation/error-handling guidance for build and test operations (e.g., how to check for build failures, what to do when a simulator isn't booted, retry patterns).

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what Xcode, simulators, or build systems are. Every section serves a clear purpose and there's no padding or unnecessary context.

3 / 3

Actionability

Installation commands and help discovery commands are concrete and executable. However, the skill relies heavily on self-discovery via `--help` rather than providing concrete examples of actual build/test/run commands with real arguments. The 'Capability Overview' section is a vague list rather than actionable guidance.

2 / 3

Workflow Clarity

The three-step sequence (verify CLI → discover commands → execute minimally) is clear, and the exit criteria section is a nice touch. However, there are no validation checkpoints for actual build/test/run workflows—no guidance on checking build success, handling failures, or retry loops for the core operations the skill enables.

2 / 3

Progressive Disclosure

For a skill with no bundle files and under 50 lines, the content is well-organized into clear sections with logical progression. The approach of delegating detailed command discovery to the CLI's own `--help` system is an appropriate form of progressive disclosure for a CLI wrapper skill.

3 / 3

Total

10

/

12

Passed

Description

89%Scale 1-3

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, concise description that clearly identifies its niche (Apple platform development via XcodeBuildMCP) and includes an explicit 'Use when' clause with good trigger terms. The main weakness is that the specific capabilities are listed as a brief parenthetical rather than described as concrete actions, which slightly reduces specificity. Overall it would perform well in skill selection among a large set of skills.

DimensionReasoningScore

Specificity

Lists several actions (build, test, run, debug, log, UI automation) but they are parenthetical and terse rather than described as concrete capabilities. It names the domain (iOS/macOS development) and some actions but lacks detail on what each action entails.

2 / 3

Completeness

Explicitly answers both what ('XcodeBuildMCP CLI' for build, test, run, debug, log, UI automation) and when ('Use when doing iOS/macOS/watchOS/tvOS/visionOS work'). The 'Use when...' clause is present and clear.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'iOS', 'macOS', 'watchOS', 'tvOS', 'visionOS', 'build', 'test', 'run', 'debug', 'log', 'UI automation', and 'Xcode'. These cover the main variations a user would naturally use when requesting Apple platform development tasks.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a very specific niche (Apple platform development via XcodeBuildMCP CLI) with platform-specific triggers (iOS, macOS, watchOS, tvOS, visionOS) that are unlikely to conflict with other skills.

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.

Repository
getsentry/XcodeBuildMCP
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.