Skip to content
Back to skills

New Film

ASecurity

Turn a brief (a request plus source documents and/or reference media, e.g. a document like examples/channelrhodopsin/sources/Nobel_Med_2026.md) into a delivered molecular animation with this repo's framework - project scaffold, brief, science checks, Blender shot script, look-dev, preview, final take, encoded MP4/WebM + posters, and a production record. Use when the user hands over a brief, a reference clip or a scientific document and asks for an animation, film, loop or still.

  • 2 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added October 25, 2026
designpythonnodeexpressapi

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned October 25, 2026

npx -y skills add AmadeusBio-ai/Molecular_Animation --skill new-film --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of New Film?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for New Film
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/amadeusbio-ai-new-film/badge)](https://www.skillsdirectory.com/skills/amadeusbio-ai-new-film)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: new-film
description: Turn a brief (a request plus source documents and/or reference media, e.g. a document like examples/channelrhodopsin/sources/Nobel_Med_2026.md) into a delivered molecular animation with this repo's framework - project scaffold, brief, science checks, Blender shot script, look-dev, preview, final take, encoded MP4/WebM + posters, and a production record. Use when the user hands over a brief, a reference clip or a scientific document and asks for an animation, film, loop or still.
argument-hint: <brief, source document or reference>
---

# New film from a brief

Input: $ARGUMENTS

Follow `docs/workflow.md`. It is the authority; the steps below are a checklist. Read `docs/principles.md`, `docs/framework.md`, `docs/motion.md` and the case study `examples/channelrhodopsin/` before planning. Use judgement: adapt the steps to the brief and record your decisions.

1. **Intake.**
   - Read the brief and pick the main structure.
   - Run `python pipeline.py new <name> --pdb <ID> [--highlight RES] [--loop]`.
   - Copy the source document unchanged into `projects/<name>/sources/` and record its provenance. If the user gives one, include the generating tool and its share link.
   - Fill in `brief.md`: the request verbatim, the one idea, the chosen first shot, structures with evidence levels, beats, look and deliverables.
   - Ask the user only about decisions you genuinely can't make. Otherwise state your assumptions in the brief and continue.
2. **Science.**
   - Fetch more structures if needed with `python pipeline.py pdb <IDs>`.
   - Inspect chains, alt-locs, assemblies, ligands and numbering with `molanim.structure`.
   - Measure every claim the film depends on, with code: put it in a pure-numpy module next to the shot, with a test.
   - Where the data and the story disagree, show the data and label the illustrative step.
3. **Plan in the script header.** Set the timeline, camera keys, palette and label text as constants. Add what the brief needs from `molanim`: morph, pathway, membrane, particles, more structures, and thermal motion on one clock (`docs/motion.md`; the template already moves its protein). The case study shows each one.
4. **Build.** Run `python pipeline.py build <name>`, or `runpy` through Blender MCP.
   - Write `bpy` for Blender 5.2, not from memory of older versions: check `docs/blender-5.md` first.
   - `build` lints the shot's folder before Blender starts. An error names the 5.2 form to use.
   - Read `RESULT`, which should report the numerical checks, and the notes after it: deprecations, geometry-node warnings, lint warnings.
5. **Look-dev.**
   - Run `python pipeline.py still <name> <frame> --percent 50` (add `--overlay` for labels) at each key frame, and read the PNGs.
   - Fold every fix back into the script, in the storyboard constants where they can express it.
6. **Preview.** Run `python pipeline.py preview <name>` and read the contact sheet. Run `python pipeline.py motion` on the preview folder. Then check the busiest moves on consecutive frames (`preview <name> --frames A-B --step 1 --percent 50`, then `motion`): stepped previews hide frame-scale jerks. Fix timing and motion before any final render.
7. **Final.**
   - Run `python pipeline.py render <name> --take take-NN` in the background, then `--overlay --take labels-NN`.
   - Point `shots.json` at both takes, then run `python pipeline.py deliver <name>`.
   - Decode a few delivered frames and look at them.
8. **Record.** Complete `record.md` (model: `examples/channelrhodopsin/record.md`). Add general lessons to `docs/principles.md`, and general code to `molanim` with tests. If a Blender API surprised you, add it to `docs/blender-5.md`, `tools/api_probe.py` and `tools/bpy_lint.py` together.

When a step needs hours of rendering, say so and give an estimate (about 19 s per 1080p Cycles frame at 128 samples on an RTX 5060 Ti) before starting it.

Report at the end:
- the delivered files;
- the evidence levels;
- what was checked and how;
- the known limits, including whether the film was watched as playback or only inspected as frames.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.