Content
78%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-structured maintenance skill: an lean overview with real, clearly scoped one-level-deep reference bundles, executable DON'T/DO Swift examples, and an unusually specific review checklist. The recurring gaps are duplicated reference pointers across sections, descriptive rather than executable workflow steps, and the absence of an explicit validate-fix-retry feedback loop.
Suggestions
Consolidate the reference pointers: merge "Route by Task" and "References" (or keep one section) so each of references/core-implementation.md and references/scenekit-patterns.md is described once with a single authoritative scope list, removing the 2-3 duplicated links.
Add an explicit feedback loop to the Workflow, e.g. after step 5: "If rendering, memory, or frame-time checks fail, re-inspect the node hierarchy and physics ownership from step 2 before proceeding" — this would lift workflow_clarity to the 5 anchor.
Make Workflow steps 2-4 executable by pointing each step at the concrete recipe in the references (e.g. step 2 → coordinate-conversion and hierarchy inspection snippets in references/core-implementation.md) instead of descriptive phrasing like "explicit lifecycle ownership".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence with no conceptual padding (the WWDC 2025 deprecation note is load-bearing routing guidance, not gratuitous version trivia), but references/core-implementation.md and references/scenekit-patterns.md are each described and linked 2-3 times across "Route by Task" and "References" with overlapping scope lists — trimmable duplication that keeps it below "every token earns its place". | 4 / 5 |
Actionability | Common Mistakes contains complete, executable Swift (SCNCamera setup with pointOfView, SCNPhysicsShape with a simplified SCNBox, applyForce(_, asImpulse:)) and the checklist items are concretely verifiable ("Lights limited to 8 per node; attenuationEndDistance set on point/spot lights"), but Workflow steps 2-4 ("Inspect scene ownership, node hierarchy...", "with explicit lifecycle ownership") describe rather than instruct, leaving minor gaps relative to fully copy-paste-ready coverage. | 4 / 5 |
Workflow Clarity | The 5-step Workflow has a clear sequence with an explicit verification step ("Verify model loading, device rendering, memory, frame time, and SwiftUI/UIKit teardown") plus a ~20-item Review Checklist, but there is no error-recovery feedback loop (no "if verification fails, fix and re-check" guidance), which the 5 anchor requires; this is not a destructive/batch skill, so no cap applies. | 4 / 5 |
Progressive Disclosure | The entrypoint is a lean ~110-line overview with a TOC, and both referenced files (references/core-implementation.md, references/scenekit-patterns.md) exist as real one-level-deep bundles with clearly signaled scope descriptions ("custom geometry, shader modifiers, constraints, morph targets, serialization, hit testing, LOD, and renderer delegates"); the ~1088 lines of implementation detail are appropriately split out, matching the clear-overview anchor. | 5 / 5 |
Total | 17 / 20 Passed |