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).

69

Quality

85%

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

71%Weight 40%Scale 1-5

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

The SKILL.md body is a well-organized reference index with executable quick-reference material and a useful version-comparison table, but its central progressive-disclosure design depends on ~24 referenced rule/example/template files that are absent from the bundle, breaking navigation. Tightening the redundant pitfall/command sections would further improve token efficiency.

Suggestions

Ship the referenced bundle files (rules/*.md, examples/*.py, templates/*.py) or remove the dead links, since progressive disclosure depends on those targets actually existing.

De-duplicate the version-confusion guidance: the 'Key Differences' table already covers it, so trim 'Common Pitfalls' items 1-2 to avoid repetition.

Consolidate the render-flag examples ('Render Command' and 'Useful Commands') into a single CLI quick-reference block to reduce redundancy.

DimensionReasoningScore

Conciseness

Category-based file listings with one-line descriptions and tight code snippets keep it efficient, but 'Common Pitfalls' repeats version-confusion points already in the comparison table and 'Useful Commands' re-lists render flags shown earlier.

4 / 5

Actionability

Inline content is concrete and executable (a complete Scene example, real render commands, the %%manim cell magic, install/checkhealth commands), though most actionable depth is delegated to rule files rather than shown here.

4 / 5

Workflow Clarity

As a single-purpose reference/lookup skill it qualifies for the simple-skill exception; the 'How to use' index and Quick Reference give clear entry points, with only minor gaps in guidance on selecting the right rule file for a task.

4 / 5

Progressive Disclosure

The body is well-structured with clearly signaled one-level-deep references organized by category, but the referenced bundle directories (rules/, examples/, templates/) do not exist, so the navigation links do not resolve and the drill-down promise is broken.

3 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

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, model description: it states concrete capabilities, supplies multiple natural trigger terms, explicitly answers both what and when, and cleanly distinguishes itself from the related ManimGL variant. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas ('Scene structure, animations, LaTeX/MathTex, 3D with ThreeDScene, camera control, styling, and CLI usage') with comprehensive domain coverage.

5 / 5

Completeness

Explicitly answers 'what' ('Best practices for Manim Community Edition... Covers...') and 'when' via a numbered 'Trigger when:' list with four concrete trigger conditions.

5 / 5

Trigger Term Quality

Includes the exact natural terms users say ('manim', 'Manim Community', 'ManimCE', `from manim import *`, 'manim CLI commands', 'Scene', 'MathTex', 'Create()') plus synonyms and import/CLI markers.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (ManimCE) with an explicit boundary ('NOT for ManimGL/3b1b version') and distinct trigger markers, minimizing conflict risk.

5 / 5

Total

20

/

20

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.

Validation — 15 / 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.