agentleFS
Sign inStart free
murathany7murathany7/reel-studio/.agents/skills/setup/SKILL.md

setup

Skill5 starsChanged 10 days agoMITView on GitHub

Set up Reel Studio in the current project - copy the renderer, engines, scripts and templates into it, install dependencies and check Chrome, ffmpeg and the optional tools. Use right after installing the plugin, when asked to "set up reel studio", or when another skill needs core/render.mjs and it is missing. Also updates the kit with --update.

  • Installs packages

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run, from the project root:

    line 15
  2. Distinctive:

    Check the machine with one frame (no Blender needed):

    line 26
  3. Very specific:

    Look at the PNG: a toon donut with "Three.js" above it means rendering works.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 170 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

Setting up Reel Studio in a project

Compositions load /core/..., /engines/... and /brands/... from the project root, so the kit lives in the project, not only in the plugin. This copies it in once.

  1. Kit root: ${CLAUDE_PLUGIN_ROOT} (set only when this runs from the Claude Code plugin). If that text is shown literally (not a path), or you are Codex, Copilot or another agent, the kit is already in this project (a clone of the repo, or npx reel-studio init). Skip to step 3; to update the kit there, run npx reel-studio@latest init --update.
  2. Run, from the project root:
    bash "${CLAUDE_PLUGIN_ROOT}/scripts/init-project.sh" "${CLAUDE_PLUGIN_ROOT}" .
    It copies core/, engines/, scripts/, examples/engines-demo/, brands/_template/ and productions/_TEMPLATE/, adds AGENTS.md, CLAUDE.md (which imports it), STATUS.md and .gitignore if missing, adds a desk entry to .claude/launch.json (so "open the desk" works in the Claude desktop app), never overwrites existing files, runs npm install in core/ and prints which tools are found. To refresh core/, engines/ and scripts/ after a plugin update, add --update as the third argument.
  3. Fix any ❌ the script prints. Fix what you can yourself; for the rest, tell the person in plain words what is missing and what it is for, with the one command to paste (e.g. "Video export needs ffmpeg: brew install ffmpeg"). Chrome elsewhere → CHROME_PATH=/path/to/chrome. Don't paste the script's whole output.
  4. Check the machine with one frame (no Blender needed):
    node core/render.mjs still examples/engines-demo/index.html /tmp/reel-studio-check.png --t 3
    Look at the PNG: a toon donut with "Three.js" above it means rendering works.
  5. Optional, for a free AI voice: pip install kokoro-onnx soundfile (the voice model downloads on first use).
  6. Hand over like a person, not a log. The person is usually a marketer: one short message, no paths or tool names. For example: "All set, I can make videos here now. What are we promoting? Tell me about the product (a website link is perfect) and I'll take it from there." No brand in brands/ yet → new-brand; otherwise → make-video. Both start as a conversation.

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