agentleFS
Sign inStart free
instavarinstavar/remotion-templates/.agents/skills/make-video/SKILL.md

make-video

Skill3 starsChanged 3 months agoMITView on GitHub

Create, validate, preview, and render a local video with the Instavar Remotion templates and VideoSpec.

7 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions7 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 7

    1. av/skills★ 28same name
    2. GoldLegendW80/llm-video-maker★ 22same name
    3. murathany7/reel-studio★ 5same name
    4. imtamiliniyan/claude-video-skills★ 4same name
    5. jutsuhq/content-factory★ 4same name
    6. 87oo/ai-video-crew★ 1same name
    7. jayden-dang/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the instavar-remotion MCP server is connected, call get_capabilities, list_templates, and get_template.

    line 8
  2. Distinctive:

    Ask for any missing brief details that materially affect the result: audience, goal, platform, aspect ratio, duration, source media, call …

    line 9
  3. Very specific:

    Create or scaffold a *.video.json VideoSpec.

    line 10
  4. Very specific:

    Run npm run video:validate -- <spec> and fix every blocking error.

    line 12
  5. Very specific:

    Run npm run video:preview -- <spec>.

    line 13
  6. Very specific:

    Run npm run video:render -- <spec> only after validation and every-scene preview are satisfactory.

    line 14
  7. Distinctive:

    Keep all creative assets local unless the user explicitly approves an upload.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Make a video

  1. If the instavar-remotion MCP server is connected, call get_capabilities, list_templates, and get_template. Otherwise use the template list in the README.
  2. Ask for any missing brief details that materially affect the result: audience, goal, platform, aspect ratio, duration, source media, call to action, and audio intent. Audio intent must be narration, music, or explicitly silent.
  3. Create or scaffold a *.video.json VideoSpec. Use only published template and scene identifiers. Write the creative copy from the user's brief. Do not treat placeholder copy as finished content. Never show scene.kind as audience copy. Avoid all-caps headings and decorative labels above headings.
  4. If narration is approved, preserve the exact script in audio.narrationText. For private Supertonic narration, write one paragraph per scene at https://instavar.com/voice, download the WAV and timing manifest, then run npm run video:timing -- <spec> --audio <wav> --manifest <timing.json>. The beat count must equal the scene count. Otherwise add an existing local audio.narrationSrc, or run npm run video:narrate -- <spec> for no-key system TTS. Never leave approved narration only in the conversation.
  5. Run npm run video:validate -- <spec> and fix every blocking error. Treat hierarchy, scene differentiation, text density, and audio diagnostics as product requirements.
  6. Run npm run video:preview -- <spec>. It renders a midpoint frame for every scene. Inspect every output in out/previews/<id>/, not only the opening, middle, and ending. Correct clipping, weak hierarchy, unreadable copy, repeated layouts, poor visual balance, or timing problems. Use --studio only when an interactive review is useful.
  7. Run npm run video:render -- <spec> only after validation and every-scene preview are satisfactory. The render command performs post-render audio QA and fails if expected audio is absent or effectively silent.
  8. Report the exact spec, preview directory, MP4 path, audio mode, and unresolved warnings. Do not claim a render succeeded unless the output exists and the expected-audio QA passes.

Keep all creative assets local unless the user explicitly approves an upload. Ask before using paid services or publishing to an external platform.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free