CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-xcode-mcp

Use when connecting to Xcode via MCP, using xcrun mcpbridge or the headless mcp-server, or working with ANY Xcode MCP tool (XcodeRead, BuildProject, RunSomeTests, RenderPreview). Covers setup, tool reference, workflows, troubleshooting.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/plugins/axiom/skills/axiom-xcode-mcp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured router body with concrete commands, a clear decision tree, and clean progressive disclosure. It loses points mainly on repeated CLI tool listings and time-sensitive version detail that should sit in a deprecated section, plus unverifiable sub-skill references.

Suggestions

Consolidate the devicectl/simctl/Axiom CLI tool list so it appears once; reference it from the other locations instead of repeating it three times.

Move version-specific statements (Xcode 26.3, Xcode 27) into a clearly labeled version/deprecated section so time-sensitive detail does not clutter the main guidance.

Verify the referenced skills/xcode-mcp-setup.md, xcode-mcp-tools.md, xcode-mcp-ref.md, and axe-ref.md files exist in the bundle, or note that they are sibling-suite skills rather than local bundle files.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining basics, but it repeats the devicectl/simctl/Axiom CLI tool list three times and carries time-sensitive version statements (Xcode 26.3, Xcode 27) outside any deprecated/old-patterns section, which could be tightened.

3 / 5

Actionability

Provides concrete executable commands (sudo xcrun mcp-server enable, xcrun mcpbridge run-agent, xcrun agent skills export) and clear Read-routing directives, with only minor gaps since detailed tool usage is delegated to sub-skills.

4 / 5

Workflow Clarity

A clear routing workflow is laid out via When-to-Use, Routing Logic, and a graphviz decision tree, but there are no error-recovery feedback loops, which keeps it just short of the top anchor.

4 / 5

Progressive Disclosure

Structure is good: an overview with well-signaled, one-level-deep Read references to sub-skills, but the referenced skills/*.md paths are not present in the bundle, leaving a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tightly written router description that names concrete tools and an explicit use-when trigger, with a clear niche and low conflict risk. Only slight weakness is trigger-term breadth (missing synonyms and extensions).

DimensionReasoningScore

Specificity

Names the Xcode MCP domain plus multiple concrete tools (XcodeRead, BuildProject, RunSomeTests, RenderPreview) and operation categories (setup, tool reference, workflows, troubleshooting), giving comprehensive coverage rather than a single action.

5 / 5

Completeness

Explicitly states what the skill covers and opens with a concrete 'Use when connecting... or working with ANY Xcode MCP tool' trigger clause answering both what and when.

5 / 5

Trigger Term Quality

Strong natural keywords users would say (xcrun mcpbridge, BuildProject, RenderPreview, setup, troubleshooting), but missing common synonyms and file extensions, so not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Xcode MCP niche is narrow and the triggers (mcpbridge, mcp-server, specific MCP tool names) are distinct, giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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
CharlesWiltgen/Axiom
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.