CtrlK
BlogDocsLog inGet started
Tessl Logo

xcodebuildmcp-packaging-resource-review

Use when reviewing XcodeBuildMCP packaging, resource-root, build artifact, bundled AXe, schema, manifest, and portable macOS distribution changes.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/xcodebuildmcp-packaging-resource-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, well-structured review checklist that assumes Claude's competence and provides concrete validation commands. The only minor gap is that guardrails are phrased as assertions to verify rather than executable checks.

DimensionReasoningScore

Conciseness

The body is a lean set of short bullet lists with no padding, no over-explanation of concepts Claude already knows, and every line earning its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

It gives concrete, copy-paste-ready validation commands ('npm run build', 'npm run verify:portable', 'npx skill-check ...') and a specific file list, but the guardrails are check statements rather than executable commands, leaving a minor gap versus fully-executable anchor 5.

4 / 5

Workflow Clarity

The sections follow a clear logical review flow (scope -> files to inspect -> guardrails -> validation) with explicit validation checkpoints; just short of 5 because the sequence is topical rather than a numbered, error-recovery procedure.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present, the well-organized section headers satisfy the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

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

The description is a focused, third-person trigger clause that clearly scopes when to use the skill and names a concrete, distinctive domain. Its main weakness is that it relies on one generic verb ('reviewing') rather than enumerating the concrete review actions it performs.

Suggestions

Replace the single verb 'reviewing' with 2-3 concrete actions, e.g. 'Verify package files, check resource-root/env propagation, and validate portable macOS distribution layouts. Use when reviewing XcodeBuildMCP packaging, build artifacts, bundled AXe, schema, manifest, or portable distribution changes.'

Add common synonyms or file/path extensions users might mention (e.g. '.pkg', 'npm package', 'npm run package:macos') to broaden natural trigger coverage.

Make the 'what' explicit alongside the 'when' so the description answers both questions with concrete capabilities rather than only the review trigger.

DimensionReasoningScore

Specificity

The description names a rich, concrete domain ('packaging, resource-root, build artifact, bundled AXe, schema, manifest, and portable macOS distribution') but offers only a single generic action ('reviewing ... changes') rather than several distinct concrete actions, matching the anchor for domain-plus-1-2-actions.

3 / 5

Completeness

Both 'what' (review packaging/resource/distribution integrity) and 'when' ('Use when reviewing ... changes') are present and explicit, but the 'what' is a single review action rather than a list of concrete capabilities, so it does not reach the fully-specified anchor 5.

4 / 5

Trigger Term Quality

It surfaces the natural terms a reviewer of this project would say ('packaging', 'build artifact', 'manifest', 'schema', 'portable macOS distribution') with good coverage; just below 5 because no synonyms or file extensions are included.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (XcodeBuildMCP packaging, resource-root, and portable macOS distribution) with distinct triggers and minimal realistic overlap with unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

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.