CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobilebuildmcp-test-boundary-review

Use when reviewing MobileBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.

68

Quality

85%

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

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.

A tight, well-organized review checklist: lean bullets, concrete commands, explicit validation steps, and appropriately scoped sections with no unnecessary references. Its only soft spot is a slightly underspecified validation entry point ('Run targeted Vitest command for touched tests') and no guidance for handling validation failures.

DimensionReasoningScore

Conciseness

The body is pure lean bullets — file globs, guardrail rules, and exact commands — with zero padding and no explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete commands ('npm test', 'npm run typecheck', 'npm run test:snapshots', 'npx skill-check ...') and specific rules ('do not call real xcodebuild, xcrun, AXe, devices, or simulators') make the guidance mostly executable; the minor gap is 'Run targeted Vitest command for touched tests', which leaves the exact invocation unspecified, placing it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The section structure implies a clear sequence (review scope -> files to inspect -> guardrails -> validation) with explicit validation commands and a conditional checkpoint ('If fixtures/schemas changed'), matching anchor 4; it is not 5 because there is no feedback loop describing what to do when a validation step fails, and not 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is cleanly organized into well-labeled sections, which the rubric's simple-skill guideline scores as anchor 5.

5 / 5

Total

18

/

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 strong, niche-specific description with an explicit 'Use when ...' trigger and concrete enumerated boundary types. Its main limitation is that the 'what' is folded into the 'when' clause and a few natural synonyms (test isolation, mocks, vitest, CI) are absent.

DimensionReasoningScore

Specificity

Names the domain ("MobileBuildMCP tests") and enumerates concrete boundary types ("unit, snapshot, schema, smoke, and external process boundaries"), giving several specific items; it falls short of a 5 because 'reviewing ... for correct boundaries' is a single action rather than a comprehensive list of distinct capabilities.

4 / 5

Completeness

The 'when' is explicit ("Use when reviewing MobileBuildMCP tests for ..."), and the 'what' (perform a boundary review) is embedded in that clause; because the what is not stated separately and explicitly, it matches anchor 4 rather than 5, and clearly exceeds anchor 3 since the trigger is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("reviewing", "tests", "unit", "snapshot", "schema", "smoke"), but common variations such as 'test isolation', 'mocks', 'vitest', or 'CI' are missing, matching the 'good coverage with a few natural terms missing' anchor rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The product name 'MobileBuildMCP' combined with specific test-type boundaries carves a clear niche with distinct triggers, giving minimal conflict risk beyond generic test/code-review skills, which matches anchor 5.

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

Path

.agents/skills/mobilebuildmcp-test-boundary-review/SKILL.md

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.