docent-explainlisted

One-shot — turn any subject (a repo, a PR, a file, a URL, an essay) into a rendered, narrated, animated explainer film. The flagship docent skill. Use when the user says "/docent-explain <subject>", or asks to "make a film about X", "explain X as a video", "review X as a docent film", or just hands over a subject and expects an artifact at the end.
benelser/docent · ★ 3 · AI & Automation · score 71

Install: claude install-skill benelser/docent

# docent-explain — the end-to-end docent skill You are running the entire docent cascade against a subject the user just named: survey → treatment → spec → tts → clips → render → open. This is the flagship skill; the other docent skills are sub-steps of this one. Reach for those only when the user explicitly wants to pause between stages. ## Arguments `/docent-explain <subject> [--mode pr|ar|ex] [--subsystem X] [--pr N] [--id X] [--scale S] [--no-open]` - `<subject>` — a repo path, a github URL, a single file, a wiki directory, a blog URL, or an essay. The first positional is the subject. - `--mode` — `pr` (PR review), `ar` (architecture review), `ex` (explainer). Inferred from the subject when omitted. - `--subsystem X` — for `ar`, scope to one subsystem. - `--pr N` — for `pr`, the pull-request number. - `--id X` — override the auto-derived film id. - `--scale S` — render scale. Default `1`. Pass `0.5` for fast turnarounds. - `--no-open` — render without opening the result in the system player. ## What to do 1. **Pre-flight.** Confirm the environment is ready by checking that the agent CLI (`claude` or `codex`), `bun`, and `ffmpeg` are on PATH. If anything obvious is missing, suggest `/docent-doctor` and stop. Do not run `doctor` here implicitly — it has its own skill. 2. **Find the right surface, then survey.** The fetcher behind `docent survey` does one thing — fetch the URL you give it and report what came back. It does **not** know that arXiv's