ruler-progress-render

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass, no license.

Audit 0.4.1 · source sha b8818ac5e0a0 · 26 Oct 2026Report an issue or request a re-scan

• Publishervibe-motion GitHub organizationOwner of the repository this skill is read from
• Source foldervibe-motion/skills/ruler-progress-renderThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdictb8818ac5e0a0A new audit runs when the source changes
• Repository statusNot archivedLast push 20 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: ruler-progress-render
description: 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.
---

# 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

Excerpt, first 1,631 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/vibe-motion/skills
git -C skills checkout b8818ac5e0a0

Works in

1. 2026-10-26
   ✓SAFE B 89 / 100

   first audit · source b8818ac5e0a0

Questions about ruler-progress-render

• github.com/vibe-motion/skills/tree/main/ruler-progress-render — the audited source at commit b8818ac5e0a0 and every finding aboveObserved · 26 Oct 2026

Spotted something wrong? Report a correction · Methodology