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.

75

Quality

92%

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 highly actionable, well-sequenced workflow with strong validation feedback loops and concrete commands throughout. The main weakness is progressive disclosure: a real reference file exists but is unlinked, and its content is duplicated inline in the body rather than pointed to.

Suggestions

Link references/session-pattern-notes.md from the relevant body sections (e.g. introspection parallelism, desktop output capture) and move the duplicated gotcha prose into that file so the body stays an overview.

Trim the anecdotal aside ('Xcode_26.3.0-rc2.app is wrong: it has been written twice and corrected both times') to a one-line 'wrong vs. correct' example to tighten conciseness.

Consider pulling the version-naming table into the reference file and keeping only the 'betas drop the dot, RCs keep it' rule inline, reducing the body's token load.

DimensionReasoningScore

Conciseness

Largely efficient with copy-paste commands and a version-naming table that earns its place, but a few explanatory asides (e.g. 'it has been written twice and corrected both times') and duplicated prose around the table could be trimmed. It is not a 5 because not quite every token earns its place; not a 3 because the body is well above 'mostly efficient with unnecessary explanation'.

4 / 5

Actionability

Fully executable throughout — exact `make` targets, `xcrun xcodebuild -downloadComponent MetalToolchain`, per-platform build/run commands, and a literal executable path for desktop output capture, plus an explicit file/variable update scope. Copy-paste ready and covers the common cases.

5 / 5

Workflow Clarity

Clear sequence (Inputs → file scope → validation → XTRO → introspection → checklist → output) with explicit validation checkpoints (`make show-versions`, `make world`) and feedback loops (missing MetalToolchain → install → rerun; unclassified entries → `unclassified2todo` → rerun) plus a completion checklist, matching the top anchor.

5 / 5

Progressive Disclosure

The body has good section structure but the provided `references/session-pattern-notes.md` is never linked from the body, and substantial content (introspection parallelism gotcha, desktop output capture) is duplicated inline rather than offloaded to that reference. Fits 'references present but not clearly signaled; content that should be separate is inline' better than the anchors above or below.

3 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: third-person, concrete, and explicit about both capability and trigger conditions, with a narrow well-scoped niche that minimizes conflict risk. It does not pad with concepts Claude already knows.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Update dotnet/macios to a new Xcode beta', 'update macios SDK/version constants', 'run xtro-sharpie sanitization', 'run introspection tests for iOS/tvOS/macOS/Mac Catalyst' — giving comprehensive coverage rather than generic verbs.

5 / 5

Completeness

Explicitly states 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, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a macios developer would actually say — 'bump Xcode beta versions', 'xtro-sharpie sanitization', 'introspection tests' — plus all four platform variants, with no jargon-only or generic filler.

5 / 5

Distinctiveness Conflict Risk

The narrow 'dotnet/macios to a new Xcode beta' niche with highly specific triggers (xtro-sharpie, introspection per platform) makes collision with other skills extremely unlikely.

5 / 5

Total

20

/

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.

Validation16 / 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.