draft-review
/draft-review
Review-and-learn skill for Tutorial Studio. Use whenever the user reacts to a tutorial story, draft or final video — to route each comment to the right role, apply it, re-render only what's needed, and save lasting preferences to STYLE.md / style.json / FEEDBACK.md so every tutorial gets closer to the user's taste.
- Author
- tohawk89 ↗
- Repository
- clickcast ↗
- Licence
- MIT
- Last repository change
- 02.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review-and-learn skill for Tutorial Studio. Use whenever the user reacts to a tutorial story, draft or final video — to route each comment to the right role, apply it, re-render only what's needed, and save lasting preferences to STYLE.md / style.json / FEEDBACK.md so every tutorial gets closer to the user's taste.
Original author description
Review-and-learn skill for Tutorial Studio. Use whenever the user reacts to a tutorial story, draft or final video — to route each comment to the right role, apply it, re-render only what's needed, and save lasting preferences to STYLE.md / style.json / FEEDBACK.md so every tutorial gets closer to the user's taste.
How it works
- Find what they mean
- Route it
- Remember it
- After delivery
SKILL.md preview
---
name: draft-review
description: Review-and-learn skill for Tutorial Studio. Use whenever the user reacts to a tutorial story, draft or final video — to route each comment to the right role, apply it, re-render only what's needed, and save lasting preferences to STYLE.md / style.json / FEEDBACK.md so every tutorial gets closer to the user's taste.
---
# Draft review — apply feedback, remember taste
## Find what they mean
Most comments arrive through the review page, already tied to a part (`s02`), a step (`s02.1`)
or the whole video (`_general`): `py scripts/review.py <name> --list` prints each open one with
its time and narration, plus which parts are approved. Comments in chat come as times ("at
0:42"), step keys or descriptions ("the zoom on the price"): map them with
`renders/timeline.json`. If you can't tell which moment they mean, ask with the two nearest
candidates.
## Route it
| Comment is about | Who | Typical fix |
|---|---|---|
| what's said, order, scenes, length | Writer | edit `story.md` (bump version) → Director re-syncs `say` lines |
| pronunciation | Director | `voice.lexicon` in shotlist or style.json |
| voice, speed | Director | shotlist `voice` (this video) or style.json (always) |
| wrong click, missing step, flaky screen | Director | shotlist step → `capture.py --check` → `--scene` re-film |
| too fast / slow | Director | `pause`, `act_at`, `voice.speed`, style `pacing.gap` |
| zoom, highlight, callout, chapter label | Director | step fields or style `camera` / `highlight` → `build.py` only |
| cards, colours, fonts, captions look, music level | Director | `style.json` brand/cards/captions/audio → `build.py` only |
Re-run only what's needed (AGENTS.md → "What to re-run") and render a new draft: `build.py`
redraws only the parts that changed (it prints them under "redrawn"). Then mark each handled
comment `py scripts/review.py <name> --done s02.1="zoom removed"` (short reply, the user's
language) and tell the user in one or two lines which parts to look at again. A comment you
didn't act on (a question, or one you need to ask about) stays open: answer it in chat.
## Remember it
1. Decide the scope. A taste statement ("too slow", "I hate zooming on buttons", "always captions")
with nothing video-specific → **house**. About this app or this tutorial → **video**. Unsure →
ask "Always, or just this tutorial?"
2. Save it:
- house → change `style.json` if it's a number/setting, and the matching section of `STYLE.md`
in words (bump "Last updated"). Praise counts too ("love the spotlight") — record what worked.
- video → `projects/<name>/style.json` (same keys, any subset) or `notes.md`.
3. Log it — there are two logs, because the root one is shared (pushed to git) and projects are not:
- house → a row at the **top** of the root `FEEDBACK.md`. In the Project column write the
project's `id` from `project.json` (e.g. `p-7f3a`), **never its name, URL or client**. Describe
the lesson in general terms ("pacing felt rushed", "highlight ring lingers after the tap"),
with nothing that reveals the app's screens, wording or data.
- video / once → a row at the **top** of `projects/<name>/FEEDBACK.md` (local only; create it
from the root table header if missing). Here quote the user's exact words freely.
- Both? (e.g. "too fast here, and always") → one row in each.
4. Say in one line what you saved, e.g. "Saved to house style: zoom only on typing, 1.5×."
If the same kind of feedback appears twice in the root `FEEDBACK.md`, the house style isn't strict enough:
tighten it and say so. Never silently undo a saved preference; if a new request contradicts one,
point it out and ask which wins.
## After delivery
Ask once: "Anything you'd change — story, pacing, voice, look?" When they confirm the final, the
Producer offers the clean-up (see tutorial-pipeline § 6–7).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tohawk89/clickcast | 90 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| tohawk89/clickcast | 90 | MIT |
Database snapshot: 13.11.2026 · package version 7c943f52ba78 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90tutorial-pipeline
Producer playbook for making a narrated video tutorial of a web app with Tutorial Studio. Use when the user asks to make, plan, film, re-cut or finish a tutorial / walkthrough / demo video of a website or web project, or runs /tutorial. Covers intake, running the System Analyst,… - 90tutorial-pipeline
Producer playbook for making a narrated video tutorial of a web app with Tutorial Studio. Use when the user asks to make, plan, film, re-cut or finish a tutorial / walkthrough / demo video of a website or web project, or runs /tutorial. Covers intake, running the System Analyst,… - 86first-video-tutorial
Use when guiding tutorial step 3/4, Create your first video. - 90apply-video-review
Apply a video review made with the AI Video Review Tool (video-review). Use when the user asks to "check my review", "apply my video review", "implement the review notes", or points at a *.review folder, REVIEW.md or notes.json next to a rendered video. - 100skill-improver
Turns the feedback on a finished video into lasting rules in the style or skill that made it. Collects the video's notes (review-page notes, preview fixes, chat corrections), keeps only the ones meant for every future video, finds the style or skill behind the edit, checks for a… - 90video-studio
Edit any video by conversation — the orchestrator for the bundled video pipeline. Use when the user wants to edit, cut, caption, grade, or add motion graphics to footage; drops a folder of clips and says "edit this"; or asks to make a promo/teaser/tutorial/short. Routes to…