CtrlK
BlogDocsLog inGet started
Tessl Logo

xcodebuildmcp-tool-contract-review

Use when reviewing XcodeBuildMCP tool contract changes across implementation, manifests, workflow membership, output schema metadata, and next-step templates.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 compact, well-structured review skill with concrete guardrails and validation commands that respects the context budget. Adding an explicit ordered review workflow with a validation checkpoint would lift workflow clarity to the top level.

Suggestions

Add a short numbered review sequence (inspect listed files -> verify each guardrail -> run validation -> report findings) so the workflow is explicit rather than implied.

Tie guardrail failures to a feedback step (fix and re-run validation) to close the loop before reporting.

DimensionReasoningScore

Conciseness

The body is lean and efficient: scope, a file list, concrete guardrail checks, and validation commands, with no padding or restating of concepts Claude already knows.

5 / 5

Actionability

Guardrails are specific executable checks ('Manifest id matches filename', 'Tool module exports named schema and handler') and validation gives copy-paste npm/npx commands.

5 / 5

Workflow Clarity

The guardrail list functions as a checklist and validation is concrete, but there is no explicit ordered review sequence or pass/fail feedback loop tying the checks to the validation step.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is cleanly organized into scoped sections (Review scope, Files to inspect, Guardrails, Validation); no bundle files exist to reference.

5 / 5

Total

19

/

20

Passed

Description

78%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 tight, specific review-trigger description that clearly answers what and when with minimal conflict risk. It could broaden its natural-language trigger synonyms to push completeness and trigger quality to the top level.

Suggestions

Add a couple of plainer user-side trigger phrases (e.g., 'or when adding/modifying MCP tools') to widen natural keyword coverage.

Make the 'when' clause slightly more explicit about the change events that trigger it (e.g., 'Use when adding, renaming, or repointing a tool').

DimensionReasoningScore

Specificity

The description names the domain ('XcodeBuildMCP tool contract changes') and enumerates several concrete review surfaces (implementation, manifests, workflow membership, output schema metadata, next-step templates), giving comprehensive coverage with a single governing verb.

4 / 5

Completeness

Both 'what' (reviewing tool contract changes across listed surfaces) and 'when' ('Use when reviewing...') are explicit, but the trigger phrasing is specialized rather than broadly natural.

4 / 5

Trigger Term Quality

It uses natural terms a contributor would say ('reviewing', 'tool contract changes', 'manifests', 'workflow membership', 'next-step templates'); coverage is good though a few plainer synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped to XcodeBuildMCP tool contract review with distinct triggers, giving minimal overlap with other skills.

5 / 5

Total

17

/

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.

Validation — 16 / 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.