Content
81%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, dense procedural skill: the inspection workflow is clearly sequenced with explicit validation gates, quantified thresholds, and worked examples with real measured facts. Main gaps are the redundancy between 'How It Works' and 'Inspection Workflow', and the absence of the actual Blender state-extraction script the workflow depends on.
Suggestions
Provide the actual Blender state exporter (or a reference collect_motion_state.py in scripts/) — the workflow's core extraction step currently tells the agent to write the tool itself instead of supplying it.
Merge 'How It Works' into the 'Inspection Workflow' section (or drop it) — its five steps restate the seven-step workflow and add token cost without new information.
Move the two worked Examples and/or the Report Shape template into a one-level-deep references/ file (e.g. references/examples.md) to slim the main SKILL.md and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative with no filler — lines like 'Ground penetration: compare lowest foot or shoe vertices with floor height per frame' and the quantified 'Practical Thresholds' (1-2 cm, 5%, 30 degrees per frame) earn their tokens, and it never explains basics Claude already knows. It is not 5 because the 'How It Works' section substantially duplicates the 'Inspection Workflow' steps, and 'Core Principle' restates the description — trimmable redundancy. | 4 / 5 |
Actionability | Concrete guidance is strong: a runnable command ('blender --background scene.blend --python collect_motion_state.py'), specific bone names, quantified thresholds, and worked examples with measured facts ('foot.L min_z = 0.004', 'foot.L x = 0.21 -> 0.28'). It is not 5 because the central extraction step — the Blender state exporter / collect_motion_state.py script — is referenced but never provided, so the agent must author the key tooling itself; it is well above 3 because the surrounding guidance is executable and specific rather than pseudocode. | 4 / 5 |
Workflow Clarity | The 7-step 'Inspection Workflow' is clearly sequenced with explicit validation gates: 'Establish the clean scene and asset baseline before judging motion', 'Check model integrity before retargeting blame', 'Report facts before opinions', plus adaptive sampling ('sample more densely around flips, landings, turns') and a report template acting as a checklist. It is not 4 because checkpoints are not merely present — they are explicit ordering principles enforced at every phase with error-recovery guidance in the anti-patterns; the read-only nature of inspection means the destructive-batch cap does not apply. | 5 / 5 |
Progressive Disclosure | The skill is a single self-contained file (no references/, scripts/, or assets/ exist) with well-labeled sections (When to Use, Workflow, Report Shape, Examples, Thresholds, Anti-Patterns, Tooling Notes), so navigation is easy. It is not 5 because at ~156 lines the worked Examples and Report Shape template are natural candidates for one-level-deep reference files that would slim the main file, and no external references are signaled at all; it is well above 3 because the structure is consistent and nothing is buried. | 4 / 5 |
Total | 17 / 20 Passed |