CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-xcode-mcp

Use when connecting to Xcode via MCP, using xcrun mcpbridge, or working with ANY Xcode MCP tool (XcodeRead, BuildProject, RunTests, RenderPreview). Covers setup, tool reference, workflow patterns, troubleshooting.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

A well-organized router with a clear decision tree and explicit routing rules, but its value is undermined because none of the referenced sub-skill files actually exist in the bundle, and the When-to-Use and routing-trigger lists duplicate each other.

Suggestions

Ship the referenced bundle files (skills/xcode-mcp-setup.md, skills/xcode-mcp-tools.md, skills/xcode-mcp-ref.md, skills/axe-ref.md) or remove the broken "Read:" directives so progressive disclosure is real, not promised.

Dedupe the "When to Use" list against the per-route "Triggers" lists — keep triggers only where they aid routing decisions.

Tighten the intro paragraph to avoid restating the frontmatter description verbatim.

DimensionReasoningScore

Conciseness

Mostly lean for a router, but the "When to Use" bullet list substantially overlaps the per-route Triggers lists, and the intro sentence ("This skill suite covers setup, tool reference, workflow patterns, and troubleshooting") repeats the description — it could be tightened.

2 / 3

Actionability

Routing directives are concrete ("Read: skills/xcode-mcp-setup.md") and the decision tree is explicit, but every "Read" target points to a file that does not exist in the bundle, so the actions are not actually executable as written.

2 / 3

Workflow Clarity

A clear sequenced decision process: numbered routing sections plus a graphviz decision tree (Setup? → Tools? → Ref?) with explicit yes/no branches, matching the clear-sequence anchor for a routing workflow.

3 / 3

Progressive Disclosure

Structure is well-signaled with one-level-deep "Read:" references and an overview body, but no skills/ directory or referenced files (xcode-mcp-setup.md, axe-ref.md, device-control-ref.md) are present in the bundle, so the disclosure promise is broken.

2 / 3

Total

9

/

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.

A tight, specific description that states capabilities, lists concrete tool names, and opens with an explicit "Use when" trigger clause. It cleanly answers both what and when with low conflict risk.

DimensionReasoningScore

Specificity

Names the domain and concrete tools/actions — "XcodeRead, BuildProject, RunTests, RenderPreview" plus "connecting", "using xcrun mcpbridge", "setup, tool reference, workflow patterns, troubleshooting" — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers what ("Covers setup, tool reference, workflow patterns, troubleshooting") and when ("Use when connecting to Xcode via MCP..."), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "connecting to Xcode via MCP", "xcrun mcpbridge", and the named MCP tools — giving good keyword coverage; only the emphatic "ANY" is mildly over-claimed but not vague.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Xcode MCP with named tools and the mcpbridge launch path, a clear niche unlikely to trigger for unrelated skills.

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