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).

99

3.42x
Quality

Does it follow best practices?

Impact

96%

3.42x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured skill: executable commands, a clear multi-step workflow with re-check checkpoints, and an exit-criteria checklist, all without unnecessary explanation. It satisfies conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — "Use XcodeBuildMCP tools via the `xcodebuildmcp` executable instead of raw `xcodebuild`, `xcrun`, or `simctl`" — with no padding explaining concepts Claude already knows, matching the score-3 anchor.

3 / 3

Actionability

It provides fully executable, copy-paste-ready commands ("xcodebuildmcp --help", "brew tap getsentry/xcodebuildmcp", "npm install -g xcodebuildmcp@latest", "xcodebuildmcp tools") rather than pseudocode, matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear Step 1 → Step 2 → Step 3 sequence is paired with validation checkpoints ("Re-check after install") and an explicit Exit Criteria checklist; the operations are non-destructive so the destructive-operation cap does not apply, matching the score-3 anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no external bundle files and is organized into well-labeled sections (Step 1/2/3, Capability Overview, Exit Criteria), so it qualifies for score 3 per the simple-skills scoring note without needing file references.

3 / 3

Total

12

/

12

Passed

Description

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.

The description is concise, concrete, and well-targeted: it names the tool, lists six specific actions, and provides an explicit "Use when" trigger tied to Apple platforms. It cleanly satisfies all four dimensions with no padding or over-claims.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "build, test, run, debug, log, UI automation" — rather than vague language, matching the score-3 anchor for listing several specific actions.

3 / 3

Completeness

It explicitly answers both what ("Official skill for the XcodeBuildMCP CLI" with the action list) and when ("Use when doing iOS/macOS/watchOS/tvOS/visionOS work"), satisfying the score-3 anchor including the explicit "Use when..." trigger.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would say ("iOS/macOS/watchOS/tvOS/visionOS work", "build, test, run, debug, log, UI automation") with broad coverage across platforms and verbs, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (XcodeBuildMCP CLI for Apple-platform work) with distinct platform triggers unlikely to collide with other skills, matching the score-3 anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 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.