vibe-motion/skills

ruler-progress-render

Clone or update https://github.com/sxhzju/ruler-progress-animator and render a ruler progress video with default parameters.

First seen Apr 8, 2026

Installation

$ npx skills add vibe-motion/skills --skill ruler-progress-render

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from vibe-motion/skills · top by installs.

npx skills add vibe-motion/skills

Browse all from vibe-motion/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.2K
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,668 B
  • docs SUMMARY.md 1,635 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 847 installs

SKILL.md

Ruler Progress Render

Workflow

  1. Use scripts/renderrulerprogress.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 - REMOTIONOUTPUT=... REMOTIONPROPS_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