Content
68%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 highly actionable and reasonably concise, with strong executable examples. It is undermined by a severe progressive-disclosure failure: every linked reference path is missing and the actual bundle reference files are orphaned, so the overview cannot deliver readers to the detailed material it promises.
Suggestions
Reconcile the body's links with the actual bundle: either add the referenced rules/, examples/, and templates/ files, or relink the existing references/*.md files (equation_transforms, integration_visualization, parallax_starfield, rotating_exponentials, spring_mass_system, three_d_surfaces, transit_animation, vector_fields) so the overview points to material that exists.
Add an explicit verification checkpoint to the interactive workflow (e.g., confirm the scene renders with `manimgl --version` / a dry `-l` low-quality pass before committing to a full `-w` render) so the multi-step process has a feedback loop.
Trim tangential padding — drop or shorten the License & Attribution block and deduplicate the Common Pitfalls list against the Key Differences table — to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly code- and table-forward with tight Quick Reference blocks, but carries minor over-explanation ('ManimGL's killer feature...'), a tangential License & Attribution section, and a Common Pitfalls list that overlaps the ManimCE comparison table. | 4 / 5 |
Actionability | Multiple copy-paste-ready, executable blocks cover the common cases — basic scene structure, render/CLI commands, camera control, LaTeX with t2c, embedding, and installation — supplemented by a concrete ManimGL-vs-ManimCE reference table. | 5 / 5 |
Workflow Clarity | The interactive-development workflow gives a rough two-step sequence (`-se <line>` then `checkpoint_paste()` variants) but lacks explicit validation checkpoints, and the skill is otherwise a pattern catalog rather than a single coherent sequenced process. | 3 / 5 |
Progressive Disclosure | The body signals references clearly (rules/, examples/, templates/, LICENSE.txt) but none of those 25+ paths exist in the bundle, while the 8 real references/*.md files are never linked — navigation to detail is broken and the actual reference material is orphaned. | 2 / 5 |
Total | 14 / 20 Passed |