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.
The body is an exemplary lean router: it makes the one decision it owns (which technique fits the shot) and defers everything else. Its weaknesses are that the referenced TECHNIQUE.md files are missing from the bundle and the body offers no fallback guidance, leaving the routing promise unfulfilled as delivered.
Suggestions
Ship the referenced techniques/static-map, mapbox, maplibre, maptiler, and cesium TECHNIQUE.md files alongside SKILL.md so the router's links resolve.
Add one line of fallback guidance for shots that match no technique (e.g., which technique is the safest default).
Drop subjective filler words ("Nicer", "nice") from the technique bullets in favor of concrete differentiators (e.g., default style quality, 3D terrain support).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~30 lines of pure decision-relevant facts with zero concept explanations or padding — every technique bullet informs the choice. Minor subjective words ("Nicer styles", "nice 3D buildings") are trivial and don't earn token waste. It fully assumes Claude's competence, matching the lean anchor. | 5 / 5 |
Actionability | The routing instruction is concrete ("Choose exactly one technique from the intended shot, then load only that technique's TECHNIQUE.md") with per-technique selection criteria, but the body itself contains no executable steps and the referenced technique files are absent from the bundle, so the guidance cannot be executed as delivered. Not 4, because the key executable content is missing. | 3 / 5 |
Workflow Clarity | The single action — pick one technique based on the shot, load its TECHNIQUE.md — is unambiguous, and no destructive or batch operations require validation. Not 5, because there is no guidance for an ambiguous shot or a fallback when no technique matches. | 4 / 5 |
Progressive Disclosure | The structure is well-designed: a thin index with one-level-deep, clearly-signaled links to per-technique files. But scored against the actual bundle, the referenced techniques/*/TECHNIQUE.md files do not exist (only assets/remotion-icon.png is present), so the navigation leads nowhere as delivered. Not 4 given the broken references; not 2 since signaling and organization are genuinely clear. | 3 / 5 |
Total | 15 / 20 Passed |