Skip to content
Skills Library
Marketing & content · Automation

directing

/directing

Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.

Repository
clickcast ↗
Licence
MIT
Last repository change
02.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.

Original author description

Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.

How it works

  1. 1. Write shotlist.json
  2. 2. Check, voice, film
  3. 3. Draft
  4. 4. Changes after review
  5. 5. Final (only after the Producer confirms the user approved the draft)
  6. Optional: animated cards with HyperFrames
Original SKILL.md headings · 72 lines, 624 words
SKILL.md preview
---
name: directing
description: Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.
---

# Directing — from approved story to draft video

Input: the **approved** `story.md` (status `APPROVED`; if not, stop and tell the Producer),
`analysis/analysis.md` (+ `pages.json`) for selectors, `notes.md` intake, `style.json`.
Output: `shotlist.json`, then `renders/draft.mp4` + `renders/storyboard.html`.
The full shotlist format is in `reference.md` next to this file — read it before writing one.

## 1. Write shotlist.json

- One scene per story scene, same ids (`s01`…), `chapter` = the story's chapter name,
  `mode` = the story's look. One step per narration line: `say` = the line **word for word**,
  `do` + `target` = the action. Extra silent steps (`wait`, `scroll`) are fine.
- Selectors from the analysis, most stable first (`[data-testid]`, `#id`, `[name]`,
  `role=…`, `text=…`). Never nth-child chains.
- Sign-in and any preparation the viewer shouldn't watch go in `setup` (not filmed). Credentials
  only as `${DEMO_EMAIL}` / `${DEMO_PASSWORD}` from the project's `.env`; password steps get
  `"secret": true`.
- Emphasis from the story: `zoom`, `callout`, `spotlight`, `focus` (highlight something other than
  what's clicked, e.g. the total after saving). House default zooms on typing (style.json
  `camera.auto_zoom`) — don't add `zoom` to every step; constant zooming is tiring.
- A click that should land as the line ends ("…then click **Save**.") gets `"act_at": 0.8`.
- `intro.say` / `outro.say` from the title/end card narration; `title`, `subtitle`, `outro.title`,
  `outro.text` from the story.

## 2. Check, voice, film

```
py scripts/capture.py <name> --check     # plays every step fast, no filming: fixes selectors cheaply
py scripts/voice.py <name>               # narration clips (cached; only changed lines are redone)
py scripts/capture.py <name>             # films; each step lasts as long as its line
```
- A failing step prints its key (`s02.3`) and saves `capture/<scene>/error.png`. Look at the
  image, fix the selector or add a `wait`/`setup` step, and `--check` again.
- Make the take repeatable: each run starts in a fresh browser profile (empty cookies and
  storage). If the app keeps data server-side, make sure re-running doesn't fail (e.g. unique
  names), or ask the Producer to have the user reset the demo data.
- `voice.py` engine/voice come from the intake (`shotlist.voice` or `style.json`). `recorded`
  writes `voice/script.md` for the user to record; it exits listing what's missing.

## 3. Draft

`py scripts/build.py <name> --draft` (720p, "DRAFT" badge, ~real time). Then **look at it**:
extract frames at each zoom, callout, chapter label and card
(`ffmpeg -ss <t> -i renders/draft.mp4 -frames:v 1 -vf scale=960:-1 check.png`; step times are in
`renders/timeline.json`) and check:
- the cursor lands on the right control and the click ripple is on it;
- zoomed views keep the important thing inside the frame; callouts don't cover what they label;
- nothing private is on screen (real names, emails, tokens, notifications);
- the narration matches what's on screen at that moment (open storyboard.html to skim);
- `build.py` printed `ok loudness` and no `!!` lines (overlapping narration means a line is
  longer than its step: shorten the line, or add `pause`).
Fix and rebuild before handing back. Report to the Producer in ≤10 lines: draft path, length,
what you checked, any compromise (e.g. "s03 is screenshots because the chart animates slowly").

## 4. Changes after review

Use the "What to re-run" table in `AGENTS.md`. Re-film only affected scenes with
`capture.py --scene <id>` (earlier scenes are replayed unfilmed to reach the right state).

## 5. Final (only after the Producer confirms the user approved the draft)

`py scripts/build.py <name> --final [--music library/music/<file>] [--captions]` → check frames
and loudness again → hand back `renders/final.mp4`.

## Optional: animated cards with HyperFrames

Built-in cards are drawn by `build.py` in the brand colours. For a richer look, make a full-frame
card with the `/hyperframes` skills (if your agent has them; `npx hyperframes` otherwise) at
the video's resolution, render it to `projects/<name>/assets/title.mp4`, and set
`"intro": {"card": "assets/title.mp4", "say": "…"}` (same for `outro`).
Files in this package (2)
  • SKILL.md 5 KB
  • reference.md 7 KB

Versions

RepositoryScoreLicence
This page · tohawk89/clickcast100MIT
tohawk89/clickcast100MIT

Database snapshot: 13.11.2026 · package version 0a1083a69d40 (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

  • 100higgsfield-shotlist-director
    Turns a brief, script, scene breakdown, treatment, or story idea into ONE connected director's shotlist for Seedance 2.0 — a single editable HTML artifact with a global Style Prefix, an @-asset glossary, and named per-scene prompts (1a, 1b, 2a…) each in Style → Characters →…
  • 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,…
  • 90shotlist-builder
    Use when a script, treatment, scene list or multi-shot brief has to be planned as a multi-shot VIDEO piece — 剧本拆镜、分场拆镜头、多镜规划、镜头清单、拍摄计划、 逐镜视频提示词总表、分镜表、shotlist、shot breakdown — landing as one searchable HTML table with per-shot durations and 4–15s Seedance groupings. 素材要和剧本…
  • 90video-brief-to-shotlist
    Use when the task is to convert a video brief into a shot list with duration, framing, and purpose.
  • 91wan3-emotion-shotlist
    30 秒单人、双人或三人文戏情绪表演提示词生成系统(对齐 wan3.0 提示词公式:总体描述、时间戳分镜、美学控制、声音三层)。保留 50 种完整情绪库、肌肉到视觉结果、全身姿态、呼吸控制、主角连续情绪弧线、对手回声、第三角色推动和核心道具连续性;最终交付改为一段总体描述 + 约 16–20 个带时间戳、有叙事作用的编号镜头。完整台词必须在同一个镜头内自然说完,默认使用正反打与过肩镜头,不输出秒级碎拍、不用微动作凑镜头数。当用户需要基于参考图生成约 30 秒、多角色互动、情绪递进、带或不带台词的 AI 视频分镜提示词时使用。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.