CtrlK
BlogDocsLog inGet started
Tessl Logo

manim-video

Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.

74

Quality

93%

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

86%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.

A well-engineered body: executable code and commands for every pipeline stage, concrete creative standards (palettes, timing, typography scales), and exemplary progressive disclosure with 14 verified, well-signaled reference files. Weaknesses are minor — some editorial rhetoric in the Creative Standard section and a validation step that could specify the fix-and-retry loop more explicitly.

Suggestions

Trim rhetorical flourishes in the Creative Standard section (e.g., "This is educational cinema. Every frame teaches. Every animation reveals structure.") to pure directives — the specific opacity, timing, and palette rules already carry the guidance.

Strengthen the REVIEW step into an explicit feedback loop: on failed verification against plan.md, state what to re-render at -ql and when to re-check, rather than just "adjust".

Link references/production-quality.md's pre-code/pre-render/post-render checklists into the Pipeline steps so the validation checkpoints are part of the workflow, not just an indexed file.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific (timing tables, font rules, pitfalls like raw strings and buff>=0.5) with almost no explanation of concepts Claude already knows, but rhetorical padding like "This is educational cinema. Every frame teaches." and "A 2-second pause after a key reveal is never wasted" could be trimmed. Not 5: a few editorial sentences earn no instructional value; not 3: the padding is minor relative to the volume of concrete guidance.

4 / 5

Actionability

Copy-paste-ready content throughout: a complete Scene1 class, render commands ("manim -ql script.py Scene1_Introduction"), an ffmpeg concat block, and a worked WRONG/RIGHT raw-string example. Covers the common cases (draft vs production quality, preview stills, stitching). Not 4: the examples are executable end-to-end with no gaps.

5 / 5

Workflow Clarity

The PLAN --> CODE --> RENDER --> STITCH --> AUDIO --> REVIEW pipeline is clearly sequenced with commands per step and a REVIEW step ("Render preview stills, verify against plan, adjust") plus "Always iterate at -ql" as a checkpoint. Not 5: the review loop is thin — no explicit fix-and-re-render cycle at point of failure, and the checklists in references/production-quality.md are not wired into the workflow steps.

4 / 5

Progressive Disclosure

SKILL.md is a true overview: the Modes table routes each task type to a reference file, and the References table indexes all 14 one-level-deep bundle files (all verified to exist in references/) with content descriptions. No detail bloat that belongs in the bundle is inlined. Not 4: navigation is clear, complete, and every reference resolves to a real file.

5 / 5

Total

18

/

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.

The description is a model example: it states the tool and pipeline, enumerates five concrete output types in third person, and gives an explicit, comprehensive 'Use when users request:' trigger list including the natural '3Blue1Brown style' synonym. Both what and when are explicit with minimal conflict risk against other skills.

DimensionReasoningScore

Specificity

"Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories" lists five concrete, distinct outputs in third person ("Creates"). Not 4: coverage is comprehensive across the skill's stated modes with no discernible gaps.

5 / 5

Completeness

Explicitly answers both: what ("Production pipeline for mathematical and technical animations using Manim Community Edition") and when ("Use when users request: animated explanations, math animations, ..."). Mirrors the anchor-5 example structure; not 4 because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

"animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos" covers natural phrasings users would actually say, including the colloquial "3Blue1Brown style" synonym, plus a catch-all "any programmatic animation with geometric/mathematical content". Not 4: no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (programmatic math/technical animation via Manim) with distinct triggers like "3Blue1Brown style videos" that no generic video or document skill would claim. Minor breadth from "any programmatic animation with geometric/mathematical content", but it is still scoped to this skill's domain, so not 4.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
browser-use/video-use
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.