How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/codengamer/vibe-motion-skills --skill ruler-progress-renderBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Ruler Progress Render
Workflow
- Use
scripts/render_ruler_progress.shfrom this skill. - Pass
workspace_diras the first argument when the user specifies a folder; otherwise use current directory. - Pass
output_pathas the second argument when the user specifies output; otherwise useout/scaffold-demo-defaults-transparent.mov. - Run the script and wait for completion.
- 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-animatorexists; otherwise clone from GitHub. - Track remote default branch (
origin/HEAD) when updating existing repo. - Install npm dependencies.
- If
bunxis available, run the new scaffold flow: npm run remotion:ensure-browserREMOTION_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
bunxis unavailable, fallback tonpx remotion renderwith equivalent defaults as a compatibility path (without shared browser cache optimization).
Requirements
gitnodenpm- network access for clone/update and dependency install