CtrlK
BlogDocsLog inGet started
Tessl Logo

manimce-best-practices

Trigger when: (1) User mentions "manim" or "Manim Community" or "ManimCE", (2) Code contains `from manim import *`, (3) User runs `manim` CLI commands, (4) Working with Scene, MathTex, Create(), or ManimCE-specific classes. Best practices for Manim Community Edition - the community-maintained Python animation engine. Covers Scene structure, animations, LaTeX/MathTex, 3D with ThreeDScene, camera control, styling, and CLI usage. NOT for ManimGL/3b1b version (which uses `manimlib` imports and `manimgl` CLI).

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and offers genuinely executable inline quick-reference material, but it is fundamentally a catalog pointing to rule/example/template files that do not exist in the bundle. The missing bundle breaks progressive disclosure and limits the skill's actual usefulness.

Suggestions

Ship the referenced bundle files (rules/*.md, examples/*.py, templates/*.py) or remove the dead links so navigation resolves to real content.

De-duplicate the render-command examples between the "Render Command" and "Useful Commands" sections to tighten conciseness.

Add a brief explicit workflow (e.g., identify task category -> open the matching rule file -> adapt a template -> render with `manim -pql`) so the navigation becomes a sequenced process rather than an implicit catalog.

DimensionReasoningScore

Conciseness

The body is mostly a lean one-line-per-file link catalog plus tight quick-reference code, but render commands are repeated across "Render Command" and "Useful Commands" (e.g. `manim -pql`/`-pqh`), so it could be tightened. It is not padded with concepts Claude already knows.

2 / 3

Actionability

Provides copy-paste-ready, executable guidance: a complete basic Scene construct example, render commands with quality flags, `%%manim` cell magic, install/checkhealth commands, and a ManimCE-vs-ManimGL comparison table.

3 / 3

Workflow Clarity

The "How to use" section organizes rule files into clear categories, but there is no sequenced multi-step workflow or validation checkpoint; for a best-practices reference skill the navigation is clear yet the workflow is implicit rather than enumerated.

2 / 3

Progressive Disclosure

The structure is well-organized with one-level-deep, clearly signaled references grouped by category, but every referenced bundle path (rules/, examples/, templates/) is absent from the actual bundle, so the disclosure chain is broken and navigation leads nowhere.

2 / 3

Total

9

/

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 strong, well-targeted description: it states concrete capabilities, provides explicit numbered triggers, and disambiguates ManimCE from ManimGL. Voice stays third person and there is no fluff.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capability areas — "Scene structure, animations, LaTeX/MathTex, 3D with ThreeDScene, camera control, styling, and CLI usage" — naming the domain and concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Best practices for Manim Community Edition ... Covers ...") and when via a numbered "Trigger when: (1)...(4)" clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "manim", "Manim Community", "ManimCE", `from manim import *`, `manim` CLI, "Scene, MathTex, Create()" — with good breadth of common variations.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (ManimCE) with an explicit "NOT for ManimGL/3b1b version" disambiguator and distinct import/CLI triggers, making conflict with sibling skills unlikely.

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: 31 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.