Ruler Progress Render

vibe-motion/skills/ruler-progress-render

by vibe-motion4c86c0d016a3ba22ee673428a494f3c44f84111fNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Clone or update https://github.com/sxhzju/ruler-progress-animator and render a ruler progress video with default parameters. Use when users ask for requests like "绘制个尺子进度条", "做个尺子进度动画", "渲染 ruler progress", or ask to export the default demo video from this project.

Includes scriptsDesign & Creative
AI-generated overview

Clones or updates a ruler progress animator repo and renders a default ruler progress video via a shell script.

What it does
The skill runs a bundled shell script that clones or updates the ruler-progress-animator repository, installs npm dependencies, and renders a ruler progress animation video. It accepts an optional workspace directory and output path, defaulting to the current directory and out/scaffold-demo-defaults-transparent.mov. It uses a bunx-based Remotion scaffold flow when available, otherwise falls back to npx remotion render. It returns the final absolute output path printed by the script.
When to use it
Use it when a user asks to draw a ruler progress bar, make a ruler progress animation, render a ruler progress video, or export the default demo video from this project.
Requirements
Requires git, node, npm, and network access for cloning or updating the repository and installing dependencies. Ships an executable shell script at scripts/render_ruler_progress.sh; bunx is optional, with npx as a fallback.

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
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

Source and attribution

Source:vibe-motion/skillsinruler-progress-renderat commit4c86c0d

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal