CtrlK
BlogDocsLog inGet started
Tessl Logo

xcode-sync

Xcode fleet sync: signed archives, compatibility, install, selection, first launch.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 strong, lean workflow: executable commands, explicit validation/rollback checkpoints for destructive fleet operations, and a well-signaled single bundle script reference. It respects Claude's competence while remaining concrete and copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense but every token earns its place — it assumes competence with rsync/ssh/xcodebuild/plutil and never explains concepts Claude already knows, with no padding or boilerplate.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (pkgutil --check-signature, shasum -a 256, xip --expand, rsync, xcodebuild -version/-checkFirstLaunchStatus, codesign --verify) with concrete flags and quoting guidance rather than pseudocode.

3 / 3

Workflow Clarity

Clearly sequenced multi-step process (Inventory -> Inspect -> Compatibility -> Transfer/install -> First launch) with explicit validation checkpoints (verify SHA-256/signature before expansion, validate staged app, recheck first-launch until status 0) and transactional rollback feedback loops for destructive app replacements.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections with a single one-level-deep bundle reference (scripts/xcode-host-inventory.sh) that exists and is invoked inline; inline content is the core workflow that belongs in SKILL.md rather than material that should be split out.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinctive, clearly scoping an Xcode fleet synchronization niche, but it omits an explicit "Use when..." trigger clause and leans on compact jargon over natural user phrasings. Adding trigger guidance and common phrasings would lift completeness and trigger_term_quality.

Suggestions

Add an explicit trigger clause, e.g. ". Use when synchronizing Xcode across multiple Macs, installing or selecting Xcode builds, or rolling Xcode versions forward on a fleet."

Replace terse colon-list jargon with concrete verbs a user would say: "Verify signed Xcode archives, check macOS/Xcode compatibility, install, select, and complete first-launch across a fleet of Macs."

Include natural user phrasings as implicit triggers: "install Xcode", "sync Xcode versions", "switch Xcode", "Xcode-beta", "keep Macs on the same Xcode build".

DimensionReasoningScore

Specificity

Lists several concrete actions/phases — "signed archives, compatibility, install, selection, first launch" — naming a clear domain and multiple specific operations rather than vague language.

3 / 3

Completeness

It answers "what" (Xcode fleet sync and its phases) but provides no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

"Xcode" is a natural user keyword, but the colon-list phrasing ("fleet sync", "signed archives", "selection") reads as terse internal jargon and omits common variations users would say ("install Xcode", "sync Xcode versions", "switch Xcode").

2 / 3

Distinctiveness Conflict Risk

"Xcode fleet sync" is a distinct niche tied to a specific Apple toolchain, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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
steipete/agent-scripts
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.