Update Remotion Rust Ffmpeg
remotion-dev/remotion
Update Remotion's ffmpeg-next Git revision to a published rust-ffmpeg commit, refresh Cargo.lock, rebuild all supported compositor binaries, validate the monorepo, and open a draft pull request.
Design and record scripted videos of real Runyte features on Linux from a user's demo description.
Install Runyte Demo Videos
$ npx skills add runyte/runyte --skill runyte-demo-videos -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install runyte/runyte runyte-demo-videos --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/runyte-demo-videos .claude/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .claude/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add runyte/runyte --skill runyte-demo-videos -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install runyte/runyte runyte-demo-videos --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/runyte-demo-videos .agents/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .agents/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add runyte/runyte --skill runyte-demo-videos -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install runyte/runyte runyte-demo-videos --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/runyte-demo-videos .cursor/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .cursor/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/runyte/runyte.git --path skills/runyte-demo-videos--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add runyte/runyte --skill runyte-demo-videos -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install runyte/runyte runyte-demo-videos --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/runyte-demo-videos .gemini/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .gemini/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install runyte/runyte runyte-demo-videosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add runyte/runyte --skill runyte-demo-videos -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/runyte-demo-videos .github/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .github/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add runyte/runyte --skill runyte-demo-videos -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install runyte/runyte runyte-demo-videos --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runyte/runyte.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/runyte-demo-videos .opencode/skills/runyte-demo-videos && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "runyte-demo-videos" agent skill from https://github.com/runyte/runyte/tree/main/skills/runyte-demo-videos into .opencode/skills/runyte-demo-videos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runyte-demo-videos", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
runyte-demo-videos- GitHub stars
- 105
- Token cost
- ~1.3k tokens
- SKILL.md length
- 704 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Design and record scripted videos of real Runyte features on Linux from a user's demo description.
- Tasks that involve Video production
- SKILL.md covers Design the demo, Record and review and Deliver
- Runs Python scripts from its folder
What it does
Runyte Demo Videos is an agent skill from runyte/runyte. Design and record scripted videos of real Runyte features on Linux from a user's demo description. Prepare demo fixtures, play timed editor actions in a PTY, and produce a reviewed MP4 with a repeatable action recipe.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/recording.md` and `scripts/record.py`).
It sits in Media & Creative, covering Video production. It works with Linux, Git and Rust. The repository describes itself as: 🚀 The text editor that ate tmux. The licence is MPL-2.0.
When your agent uses it
- Tasks that involve Video production
Example prompts
- “/runyte-demo-videos”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 18ed42d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Runyte Demo Videos loads about 1.3k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 704 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from runyte/runyte at commit 18ed42d, republished under its MPL-2.0 licence (© runyte). 704 words, ~1,289 tokens.
Download SKILL.mdSave it as
.claude/skills/runyte-demo-videos/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- runyte-demo-videos
- description
- Design and record scripted videos of real Runyte features on Linux from a user's demo description. Prepare demo fixtures, play timed editor actions in a PTY, and produce a reviewed MP4 with a repeatable action recipe.
Runyte demo videos
Turn the requested demonstration into a small scene and an action sequence,
then use scripts/record.py to record a real Runyte process. This is a silent
video rendered from terminal output; no desktop, display server, editor API,
or screen recorder is needed. Linux and FFmpeg with libx264 are required.
The recorder shares its PTY, decoder, and font renderer with the adjacent
runyte-screenshots skill. Keep both skill directories together under skills/.
Read references/recording.md for installation,
the recipe format, timing behavior, and validation commands.
Design the demo
Translate the user's description into visible steps: establish the starting state, perform the feature's actions at readable speed, and hold the result. Choose concise, plausible example content that makes each action understandable. Use the target checkout's guide and keymap reference to confirm commands and its UI vocabulary when naming the steps. Do not assume Helix spellings.
Make reasonable choices for pacing, theme, and geometry when unspecified. Use the default 15 fps and 200 columns × 50 rows unless the user requests another terminal size. Match cell dimensions to the chosen monospace font and supply actual bold/italic variants. Prefer short sequences with visible pauses over racing through every related command.
Create isolated temporary project fixtures and initialize a Git repository so
Runyte recognizes the root. Commit a baseline when demonstrating Git changes.
Set up real language servers or terminal programs when they are part of the
feature. Default configuration disables LSP; provide --config when needed.
Use the screenshot skill's isolation and persistent-session guidance for those
scenes. Runtime isolation is not an OS sandbox; commands still have their normal
filesystem/network access, and some programs read home-directory configuration.
Write the recipe as JSON with setup and actions. Use setup for opening files,
arranging panes, and waiting for readiness before recording starts. The actions
are what the viewer sees. Add feature-specific expect or checkpoint markers
to prove the requested state appeared, and reading pauses after meaningful changes.
Use type for visible typing, key for shortcuts, and command for commands
typed into :. In Terminal Insert, send Ctrl-\ (\u001c) before an editor
command; Escape belongs to the child program there.
Show full SKILL.md (355 more words)Show less
Record and review
Run the recorder with the prepared workspace, built binary, fonts, recipe, and requested output path. Live playback records timestamped terminal output while answering terminal queries. Video encoding happens afterward, so slow font rendering cannot change the typing pace or editor response time. Setup output initializes the first frame but is excluded from the visible video.
Inspect the preview contact sheet, final text, and timestamped action/checkpoint metadata. Use FFprobe to verify codec, dimensions, duration, and frame count; extract frames around important transitions and inspect them with an image tool. When a video viewer is available, watch the whole clip to judge pacing. A contact sheet alone does not establish that every intermediate frame is correct.
When the same text appears in multiple panes, verify the intended destination pane. A whole-screen text match does not prove that a copy, paste, or focus change succeeded.
If the demo misses a state, clips text, shows loading/errors unexpectedly, or
moves too quickly, adjust fixtures or actions and record again. Use a new output
name or --overwrite intentionally. Failed playback or encoding exits nonzero
and does not publish its temporary recording as a completed demo.
Deliver
Return the MP4 and keep the action recipe with a minimal fixture setup recipe
where the user can reuse them. The output JSON embeds actions and timing, but
does not recreate demo files, installed programs, or persistent-session hosts.
Preserve those inputs alongside a reusable demo when requested; do not rely on
temporary paths or .runyte/ images surviving.
Record which binary/source revision was used with --label, plus the scene's
theme and font choices. Inspect paths, configuration, terminal contents, and
sidecars before tracking or publishing them. The recorder discards raw PTY traces
after encoding. Keep verification artifacts out of tracked development context.
The shared renderer has the screenshot skill's terminal-text limitations: no terminal graphics, complete extended-attribute emulation, or automatic font fallback. Mouse events reach Runyte, but the video does not draw a desktop mouse pointer. Hardware cursor outlines are optional; real editor selection/caret cells are captured as drawn. Do not invent a missing interface or imply that the video came from a desktop capture.
© runyte, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in skills/runyte-demo-videos of runyte/runyte.
- SKILL.md
- .gitignore
- agents/openai.yaml
- references/recording.md
- scripts/record.py
- scripts/requirements.txt
- scripts/test_record.py
Open the folder on GitHubat commit 18ed42d
Compare with similar skills
Runyte Demo Videos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Runyte Demo Videos this skillrunyte/runyte | 105 | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| Update Remotion Rust Ffmpegremotion-dev/remotion | 63k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Gridbash Panesjasonsuhari/gridbash | 134 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Playwright Tracemellowagain/gitarena | 115 | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| OpenStoryline Install HelperFireRedTeam/FireRed-OpenStoryline | 3.5k | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| K4k4ditano/k4 | 123 | — | ~647 | Automated safety check: Pass | MIT |
Similar skills
- Official
Gridbash Panes
jasonsuhari/gridbash
Coordinate with sibling agent panes from inside a GridBash grid — list panes and their roles, read what a pane is currently doing, prompt one pane or every other pane, and rename pane titles so the…
Playwright Trace
mellowagain/gitarena
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
OpenStoryline Install Helper
FireRedTeam/FireRed-OpenStoryline
Installs, repairs and starts a local source checkout of FireRed-OpenStoryline, from prerequisites and a venv to resources, config and the MCP and web servers.
K4
k4ditano/k4
Use this whenever the user is on a machine running k4 — the Dynamic Island-style bar for Hyprland — and wants to change what the bar does, write a plugin for it, or debug one.
Record Demo
libnativeapi/nativeapi
Record a demo video of a desktop app — launch it, play a scripted scenario with smooth synthetic mouse input, and capture the screen (cursor and click highlights included) straight to an…
More from runyte/runyte
Runyte Screenshots
runyte/runyte
Capture screenshots of Runyte features by driving the real editor in a pseudo-terminal and rendering its terminal output to PNG or WebP.
Related
Categories
Questions about Runyte Demo Videos
What does Runyte Demo Videos do?
Design and record scripted videos of real Runyte features on Linux from a user's demo description. Runyte Demo Videos is an agent skill from runyte/runyte. Design and record scripted videos of real Runyte features on Linux from a user's demo description.
When should I use Runyte Demo Videos?
Runyte Demo Videos fits situations like: tasks that involve Video production.
How do I install Runyte Demo Videos in Claude Code?
Run `npx skills add runyte/runyte --skill runyte-demo-videos -a claude-code`. Or copy the skill folder (skills/runyte-demo-videos in runyte/runyte) into .claude/skills/runyte-demo-videos in your project. Claude Code loads it when a task matches its description.
How do I install Runyte Demo Videos in Codex?
Run `npx skills add runyte/runyte --skill runyte-demo-videos -a codex`. Or copy the skill folder (skills/runyte-demo-videos in runyte/runyte) into .agents/skills/runyte-demo-videos in your project. Codex loads it when a task matches its description.
Can I use Runyte Demo Videos in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add runyte/runyte --skill runyte-demo-videos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/runyte-demo-videos, .gemini/skills/runyte-demo-videos, .github/skills/runyte-demo-videos and .opencode/skills/runyte-demo-videos in your project.
What does Runyte Demo Videos need to run?
Going by SKILL.md and its folder, Runyte Demo Videos needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Runyte Demo Videos access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Runyte Demo Videos safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Runyte Demo Videos use?
Runyte Demo Videos is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Runyte Demo Videos use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Runyte Demo Videos?
Skills that share tags, products or a category with Runyte Demo Videos: Update Remotion Rust Ffmpeg (remotion-dev/remotion, 63k stars), Gridbash Panes (jasonsuhari/gridbash, 134 stars), Playwright Trace (mellowagain/gitarena, 115 stars) and OpenStoryline Install Helper (FireRedTeam/FireRed-OpenStoryline, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Runyte Demo Videos?
runyte (a GitHub organization) maintains it in runyte/runyte, which has 105 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: runyte/runyte on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.