CtrlK
BlogDocsLog inGet started
Tessl Logo

macios-xcode-beta-update

Update dotnet/macios to a new Xcode beta and validate it end-to-end. Use this skill when a user asks to bump Xcode beta versions, update macios SDK/version constants, run xtro-sharpie sanitization, and run introspection tests for iOS/tvOS/macOS/Mac Catalyst.

72

Quality

88%

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

85%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 dense, highly actionable body with excellent sequencing and validation feedback loops, and near-zero token waste. Its main weakness is progressive disclosure: a reference file exists but is neither linked nor leveraged, and its content is duplicated inline rather than split out.

Suggestions

Link references/session-pattern-notes.md from the relevant sections (introspection parallelism, desktop output capture) and move the duplicated inline explanations there instead of restating them in SKILL.md.

Move the beta/RC application-naming table and its explanatory prose into a reference file (e.g. references/xcode-naming-conventions.md), keeping only a one-line rule plus the link in SKILL.md.

Merge the redundant prose paragraph about beta/RC ordinals ('Betas drop the dot before the ordinal...') with the table so the rule is stated once.

DimensionReasoningScore

Conciseness

Almost entirely lean, repo-specific knowledge Claude cannot know (naming traps, NETSDK1005 gotcha, desktop output capture), with no padding of known concepts. Minor over-explanation: the beta/RC ordinal rule is stated twice (prose and table), and the table's surrounding explanation could be trimmed.

4 / 5

Actionability

Fully executable throughout: exact variable names and file paths, copy-paste make/xcrun/rm -rf commands, env-var-prefixed direct execution, and the Mac Catalyst substitution pattern spelled out.

5 / 5

Workflow Clarity

Clear sequence (inputs → file updates → make show-versions → make world → XTRO → introspection) with explicit validation checkpoints, two fix-and-rerun recovery loops, an XTRO retry loop, and a completion checklist.

5 / 5

Progressive Disclosure

Well-organized sections, but the body never links the existing references/session-pattern-notes.md and instead inlines substantially the same content (parallelism gotcha, desktop output capture, MetalToolchain fix); the naming-convention table is also reference-grade material inlined in SKILL.md.

3 / 5

Total

17

/

20

Passed

Description

92%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 description that states concrete capabilities and an explicit 'Use this skill when' trigger clause in third person. Its only weakness is jargon-heavy trigger phrasing that may not match how users naturally ask for the task.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Update dotnet/macios to a new Xcode beta and validate it end-to-end', 'bump Xcode beta versions', 'update macios SDK/version constants', 'run xtro-sharpie sanitization', 'run introspection tests for iOS/tvOS/macOS/Mac Catalyst' — with comprehensive coverage in third-person voice.

5 / 5

Completeness

Explicitly answers both: what ('Update dotnet/macios to a new Xcode beta and validate it end-to-end') and when ('Use this skill when a user asks to bump Xcode beta versions...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural coverage ('bump Xcode beta versions', 'introspection tests', platform names) but leans on repo jargon like 'xtro-sharpie sanitization' that users would rarely say verbatim, missing some everyday synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (dotnet/macios Xcode beta bumps) with distinct, product-specific trigger terms; virtually no overlap risk with other skills.

5 / 5

Total

19

/

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
dotnet/macios
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.