mcpField
R
ruler-progress-render

ruler-progress-render

github.com/vibe-motionCreative & media1.4k973 installsUpdated 3w ago
Repository

About ruler-progress-render

ruler-progress-render is a skill for rendering the ruler-progress-animator project. It reuses or clones the repository, installs npm dependencies, and returns the output path.

Key features

  1. 01Reuse or clone the project repository
  2. 02Install npm dependencies
  3. 03Render with bunx or npx
  4. 04Choose workspace and output path

Use cases

  1. 01Render the default transparent demo
  2. 02Render the project in a specified workspace

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vibe-motion/skills --skill ruler-progress-render

After installing, type/ruler-progress-renderin Claude Code to confirm it loaded.

Bundled filesscripts/render_ruler_progress.sh

Details

From the project README

Ruler Progress Render

Workflow

  1. Use scripts/render_ruler_progress.sh from this skill.
  2. Pass workspace_dir as the first argument when the user specifies a folder; otherwise use current directory.
  3. Pass output_path as the second argument when the user specifies output; otherwise use out/scaffold-demo-defaults-transparent.mov.
  4. Run the script and wait for completion.
  5. Return the final absolute output path printed by the script.

Command

bash scripts/render_ruler_progress.sh [workspace_dir] [output_path]

Behavior

  • Reuse local repo if workspace_dir/ruler-progress-animator exists; otherwise clone from GitHub.
  • Track remote default branch (origin/HEAD) when updating existing repo.
  • Install npm dependencies.
  • If bunx is available, run the new scaffold flow:
    • npm run remotion:ensure-browser
    • REMOTION_OUTPUT=... REMOTION_PROPS_FILE=shared/project/render-presets/default.json npm run remotion:render
  • This flow reuses shared Chrome Headless Shell cache and avoids repeated browser downloads.
  • If bunx is unavailable, fallback to npx remotion render with equivalent defaults as a compatibility path (without shared browser cache optimization).

Requirements

  • git
  • node
  • npm
  • network access for clone/update and dependency install

Comments

Markdown supported