CtrlK
BlogDocsLog inGet started
Tessl Logo

manimgl-best-practices

Trigger when: (1) User mentions "manimgl" or "ManimGL" or "3b1b manim", (2) Code contains `from manimlib import *`, (3) User runs `manimgl` CLI commands, (4) Working with InteractiveScene, self.frame, self.embed(), ShowCreation(), or ManimGL-specific patterns. Best practices for ManimGL (Grant Sanderson's 3Blue1Brown version) - OpenGL-based animation engine with interactive development. Covers InteractiveScene, Tex with t2c, camera frame control, interactive mode (-se flag), 3D rendering, and checkpoint_paste() workflow. NOT for Manim Community Edition (which uses `manim` imports and `manim` CLI).

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/manimgl-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews 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 with concrete ManimGL-specific code and commands, but it is somewhat redundant and its progressive disclosure is broken: every referenced path is a dead link and the actual reference files are orphaned. It functions as a self-contained quick reference rather than an overview that delegates to real detail files.

Suggestions

Fix the bundle mismatch: either restore the referenced rules/, examples/, templates/ and LICENSE.txt files, or rewrite the link inventory to point at the files that actually exist in references/ (e.g. three_d_surfaces.md, equation_transforms.md).

Link the 8 existing references/*.md files from the body so they are discoverable; currently they are never referenced and a user following the skill will never find them.

Remove the duplication between the "Key Differences from ManimCE" table and the "Common Pitfalls to Avoid" list, and trim basic-concept comments, to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient and concrete, but the "Common Pitfalls to Avoid" list largely duplicates the "Key Differences from ManimCE" table (ShowCreation vs Create, Tex vs MathTex, self.frame, -se), and basic comments ("# Wait", "# Create mobjects") explain concepts Claude already knows.

2 / 3

Actionability

Fully executable, copy-paste-ready guidance throughout: `from manimlib import *` scene code, `manimgl scene.py MyScene -se 15` commands, `checkpoint_paste(skip=True)`, `frame.reorient(...)`, `Tex(R"...", t2c=...)`, and `pip install manimgl`.

3 / 3

Workflow Clarity

Content is well-organized into clear sections, but as a reference guide it has no explicit sequenced multi-step workflow with validation checkpoints; the interactive-development flow is only a loose implicit two-step with no validation.

2 / 3

Progressive Disclosure

Scored against the actual bundle: the body references rules/*.md, examples/*.py, templates/*.py, and LICENSE.txt — none of which exist — while the 8 real files in references/ are never linked from the body and are thus orphaned. Navigation is broken despite the body's organized appearance, and the large inline Quick Reference duplicates content that should live in the (missing) rule files.

1 / 3

Total

8

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description: concrete capabilities, explicit numbered triggers, third-person voice, and an explicit negative-distinctiveness clause separating it from ManimCE. It closely matches the rubric's good examples.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ("InteractiveScene, Tex with t2c, camera frame control, interactive mode (-se flag), 3D rendering, and checkpoint_paste() workflow") rather than vague language; each is a specific named feature.

3 / 3

Completeness

Explicitly answers both what ("Best practices for ManimGL... Covers...") and when (an explicit "Trigger when: (1)...(2)...(3)...(4)..." clause), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Good coverage of natural terms users say ("manimgl", "ManimGL", "3b1b manim", `from manimlib import *`, `manimgl` CLI, InteractiveScene, self.frame, self.embed(), ShowCreation()) with no major common variations missing.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (3b1b OpenGL ManimGL) and an explicit negative clause ("NOT for Manim Community Edition (which uses `manim` imports and `manim` CLI)") that prevents the most likely conflict.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 28 missing

Warning

Total

15

/

16

Passed

Repository
calesthio/OpenMontage
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.