Skip to content
TrustedSkillsbeta
Back to all skills

Manimgl Best Practices

Checked
adithya-s-k·vlatest·backend·MIT

Generates ManimGL code adhering to best practices, optimizing clarity, efficiency, and maintainability for visualizations.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add adithya-s-k/manim_skill --skill manimgl-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

adithya-s-k

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned adithya-s-k/manim_skill at cef0450117.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
cef0450117
Manifest
skills/manimgl-best-practices/SKILL.md
Scanned
60 files, 14,481 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for using manimgl, a Python library used to create mathematical animations. It includes guidance on optimizing performance, structuring scenes, and leveraging features like scene configuration and rendering settings.

When to use it

  • When creating complex mathematical animations that require high performance or visual clarity
  • When setting up a new project with manimgl and looking for structured development practices
  • When troubleshooting common issues related to rendering or animation flow

Key capabilities

  • Optimization techniques for rendering efficiency
  • Scene structuring and organization best practices
  • Configuration tips for customizing animations and visuals

Example prompts

  • "How can I optimize my manimgl scene for faster rendering?"
  • "What are the recommended practices for organizing multiple scenes in a manimgl project?"
  • "Can you explain how to configure camera settings in manimgl for better visual results?"

Tips & gotchas

  • Ensure your system meets the hardware requirements for smooth rendering, especially with complex animations.
  • Use version control (e.g., Git) to manage changes and experiment with different configurations safely.