Menu

Individual skill

catch-up-video

The catch-up briefing as a short silent slideshow video, with every decision waiting on the user kept as text below it. Use when the user runs /catch-up-video.

plugins/requie/endostack/skills/catch-up-video/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# catch-up-video

Do everything the [catch-up](../catch-up/SKILL.md) skill does, with one change: the narrative and pictures become a short silent slideshow video. The decisions waiting on the user stay as text under the video.

Run only when the user types `/catch-up-video`. The cutoff is the user's last typed message before this command, even if they ran `/catch-up` earlier.

## Differences from catch-up

**One allowed side effect.** You may create and render the video. Do it in a temporary directory outside the repository (for example under the system temp directory or the agent's scratch directory), so nothing lands in the user's working tree.

**Plan privately first.** Write, for yourself only: one sentence on what the user should know after watching, and one line per slide. Cut any slide that would not change what the user understands. Ten slides at most; fewer is better. Do not include this plan in the reply.

**Build from real outputs.** Every slide draws on artifacts the work actually created: screenshots, screen recordings, diffs and data. A description of those things in the chat is a poor substitute and does not go on a slide.