Content
61%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's inline content is high quality — lean, executable ManimGL code with a genuinely useful ManimGL-vs-ManimCE differences table and pitfalls list. However, its progressive disclosure is broken in practice: the entire link index points to files absent from the bundle while the actual references/ files are orphaned, leaving an agent unable to navigate to the detailed material the skill promises.
Suggestions
Fix the bundle mismatch: either add the referenced rules/, examples/, templates/, and LICENSE.txt files, or repoint SKILL.md's link index at the 8 existing references/*.md files (e.g. three_d_surfaces.md, equation_transforms.md) so the actual bundle is discoverable.
Deduplicate 'Common Pitfalls' against the 'Key Differences from ManimCE' table — both cover ShowCreation vs Create, self.frame vs self.camera.frame, and fix_in_frame(); keep one.
Remove the Installation section (`pip install manimgl`, `manimgl --version`) — it explains steps Claude already knows and adds tokens without new information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, executable code with terse comments and no padding essays about what Manim is — matching 'efficient; minor instances of over-explanation that could be trimmed'. It is not a 5 because the 'Common Pitfalls' section repeats content already in the 'Key Differences from ManimCE' table (ShowCreation vs Create, self.frame, fix_in_frame), and the Installation section (`pip install manimgl`, `manimgl --version`) explains something Claude already knows. | 4 / 5 |
Actionability | The Quick Reference provides copy-paste-ready, executable code covering the common cases (scene structure, render commands, camera control, Tex/t2c, embed, checkpoint_paste), which meets the 5 anchor's inline standard. It drops to 4 because the top-level instruction 'Read individual rule files for detailed explanations' and every example/template link points to files that do not exist in the bundle, so that concrete guidance cannot be executed. | 4 / 5 |
Workflow Clarity | The body is a pattern catalog rather than a sequenced workflow: the Interactive Development Workflow section sketches a mini-sequence (-se then checkpoint_paste) but there is no explicit path through the material, and the primary 'How to use' instruction is unusable because the referenced rule files are missing. This sits at 'sequence present but implicit' rather than 4's 'clear sequence with most checkpoints present'; no validation cap applies since no destructive or batch operations are involved. | 3 / 5 |
Progressive Disclosure | Scored against the actual bundle: every referenced path in the body (17 rules/*.md, 5 examples/*.py, 4 templates/*.py, LICENSE.txt) is a dead link to nonexistent files, while the 8 real bundle files under references/ (equation_transforms.md, three_d_surfaces.md, etc.) are never mentioned in SKILL.md at all — and each of those in turn points to missing examples/*.py files. The links are clearly signaled and one level deep (keeping this above a 1), but navigation is fundamentally broken, matching 'references are buried' at the 2 anchor. | 2 / 5 |
Total | 13 / 20 Passed |