Content
71%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-organized expert skill with a clear decision tree, concrete API-level rules, and exemplary progressive disclosure to 14 real one-level-deep reference files. The main weakness is token cost: Core Guidelines and the Review Checklist restate many of the same rules, roughly doubling sections that could be merged or delegated to the references.
Suggestions
Merge the Review Checklist into the Core Guidelines (or vice versa) — items like '@State is private', 'ForEach stable identity', and 'Button over onTapGesture' appear in both; a single checklist section with per-topic reference pointers would cut significant tokens.
Delegate the per-topic bullet rules that duplicate reference content (e.g., the full Animations and Liquid Glass guideline lists) to their reference files, keeping only the top 2-3 non-negotiable rules inline.
Add one short executable snippet for the most common non-Liquid-Glass cases (e.g., a correct @Observable + @Bindable data-flow example or a stable-identity ForEach), so the most frequent workflows have copy-paste patterns too.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and never explains concepts Claude already knows, but the Core Guidelines and Review Checklist sections substantially duplicate each other — e.g., '@State must be private', 'ForEach uses stable identity (not .indices)', '.animation(_:value:) with value parameter', and 'Button over onTapGesture' each appear two to three times across sections. This matches 'mostly efficient... could be tightened' rather than the minor-trim profile of anchor 4. | 3 / 5 |
Actionability | Guidance is highly concrete with exact API names ('@Bindable', '.phaseAnimator', 'glassEffectID', 'Self._printChanges()'), a property-wrapper selection table, and a copy-paste-ready Swift code block for Liquid Glass. It falls short of anchor 5 only because the single code example covers just one topic — the other workflows (state management, ForEach identity) are told as rules without a short executable example. | 4 / 5 |
Workflow Clarity | The Workflow Decision Tree clearly sequences three workflows, each gated by an explicit first step ('First, consult references/latest-apis.md'), and the Review Checklist provides per-topic checkpoints. It sits at anchor 4 rather than 5 because there are no feedback-loop steps (e.g., re-check after fixes); acceptable here since the skill is advisory, not destructive/batch. | 4 / 5 |
Progressive Disclosure | The body is a true overview: every checklist and workflow section points to its reference file by path, all 14 referenced files exist in references/, references are exactly one level deep, and the one required-reading file (latest-apis.md) is explicitly flagged. This matches 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'. | 5 / 5 |
Total | 16 / 20 Passed |