CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobilebuildmcp-docs-release-review

Use when reviewing MobileBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.

66

Quality

83%

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-structured review checklist with concrete file scopes and executable validation commands, and appropriately no bundle files for its size. The main gaps are guardrails whose verification details (expected manifest fields, CLI catalog source) are unspecified, and no guidance on handling failed validations.

Suggestions

Specify the 'expected normalized fields' the website manifest generation must preserve, or point to where they are defined.

Reference how to obtain or regenerate the CLI catalog/commands that CLI examples must match (e.g. a script or the sibling command-review skill's location).

Add a short error-recovery note for validation (e.g. what to do when 'npm run build' or the release notes check fails).

DimensionReasoningScore

Conciseness

The body is lean with zero padding: no concept explanations, and every line is an instruction, file path, or command. It matches anchor 5 (every token earns its place) rather than 4, which expects some over-explanation to trim.

5 / 5

Actionability

Concrete file paths and copy-paste validation commands ('npm run build', 'node scripts/generate-github-release-notes.mjs --version <version> --changelog CHANGELOG.md') are present, but some guardrails leave execution details unspecified ('preserves expected normalized fields' names no fields; 'match generated CLI catalog/commands' gives no pointer to the catalog source), fitting anchor 4 rather than 5.

4 / 5

Workflow Clarity

The sequence (scope, files to inspect, guardrails, validation) is clear and validation checkpoints are present, including a conditional ('Release notes check when touched'), but there is no error-recovery guidance for when a check fails, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and no bundle files; the body's file paths are review targets in the target repo, not skill references, and the single cross-skill delegation to mobilebuildmcp-docs-command-review is appropriate. Per the rubric's simple-skill note this earns 5.

5 / 5

Total

18

/

20

Passed

Description

75%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 concise, domain-specific description with an explicit 'Use when' trigger and a broad list of concrete review targets. It clearly answers what and when, though the action vocabulary is limited to 'reviewing' and trigger coverage lacks synonyms and user-side intent phrasing.

Suggestions

Add a second concrete action verb (e.g. 'Verifies ... and reviews ...') so the what is more than a single action applied to a list of artifacts.

Include a user-intent trigger phrase such as 'Use when the user asks to review a PR or diff affecting docs, changelog, or release scripts' to sharpen the when-clause.

Add natural synonyms users would say, e.g. 'docs review', 'CHANGELOG.md', 'version bump', or 'release notes generation'.

DimensionReasoningScore

Specificity

The description lists six concrete review targets ("CLI command references", "website manifest generation", "changelog", "release notes", "release script changes") but uses only a single action verb ("reviewing"), so it matches anchor 4 (several specific items, minor gaps) rather than anchor 5's multiple concrete actions.

4 / 5

Completeness

Both what (reviewing the listed MobileBuildMCP artifacts) and when (explicit "Use when reviewing...") are present, but the when merges into the what and offers no separate user-intent triggers (e.g. "when the user asks to review a PR touching docs"), fitting anchor 4 rather than the fully split what+when of anchor 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("reviewing", "documentation", "changelog", "release notes", "release script"), but common variations and synonyms (e.g. "docs review", "CHANGELOG.md", "version bump", "publish/release cut") are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The MobileBuildMCP-specific scope gives it a clear niche with minimal conflict risk, but "CLI command references" overlaps with the closely related sibling skill mobilebuildmcp-docs-command-review, matching anchor 4 (mostly distinct, minor overlap risk) rather than 5.

4 / 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: 4 missing

Warning

Total

15

/

16

Passed

Repository

getsentry/XcodeBuildMCP

Path

.agents/skills/mobilebuildmcp-docs-release-review/SKILL.md

Revision

d13ff0c

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill