@autoaiai/aicut 0.1.11 → 0.1.13

package/skills/video-explainer/SKILL.md

@@ -1,163 +0,0 @@
----
-name: video-explainer
-description: "Turn a research brief, finished script, or generated MP4 into a reviewed and verified vertical explainer video. Use when an agent should choose the simplest current production strategy, preserve strict final-artifact quality gates, run the deterministic AICUT fallback, diagnose the local toolchain, or verify an existing MP4 before any manual publication step. Runs in AICUT: the film is film.html, a page per shot, drawn by `aicut look` and `aicut render`."
-license: MIT
-source: "runesleo/claude-video-kit"
----
-
-# Video Explainer
-
-## Running it in AICUT
-
-AICUT's film is `film.html`: it cuts pages, footage, pictures and sound together on tracks. A page is a web page that
-sets `window.film = { frame(t) }` and draws that moment — no framework, no build step, no composition object, no
-`registerRoot`. Five shots are five pages cut together, not one page that changes scene, so each shot stays trimmable
-and replaceable in Studio.
-
-```sh
-npx -y @autoaiai/aicut@latest          # the manual: the format and the commands, always current
-npx -y @autoaiai/aicut@latest open .   # make this folder a film and print Studio's address
-npx -y @autoaiai/aicut@latest look     # a contact sheet of the whole film, its sound, and a determinism check
-npx -y @autoaiai/aicut@latest look 4.5 # one frame, full size — look at the PNG, not at the code
-npx -y @autoaiai/aicut@latest render   # the MP4, beside film.html
-```
-
-Run the manual before the first film: it is authoritative for the format, and this skill is about the method above it.
-
-Where the words below name another program's part, it becomes this:
-
-| elsewhere | in AICUT |
-|---|---|
-| composition, timeline, project file | `film.html`; tracks and clips inside it |
-| a scene, a sequence, a slide | a page (`pages/<name>.html`) cut onto a track |
-| `useCurrentFrame()`, `interpolate()` | `frame(t)` — the picture depends only on `t`, never on state or `Date.now()` |
-| a still, a screengrab | `aicut look <t>` |
-| `render` / `build` / `export` | `aicut render` (the person can also export from Studio) |
-| a dev server, a preview window | `aicut open` and the Studio address it prints |
-
-Hard rules that hold whatever the method says: the picture depends only on `t`; every value in the person's prompt is
-binding; look at the frames `look` writes before saying a film is done.
-
-
-Version note: v0.3.0-rc.1 / 2026-09-27 / Make production strategy adaptive while keeping the deterministic Remotion recipe as a strict fallback. Final-artifact acceptance is strategy-independent and bound to the exact MP4 bytes. Keep upload, account access, credentials, private voice assets, hosted rendering, and publication out of scope.
-
-Produce a local video and evidence packet. Never upload or publish from this skill.
-
-## Core contract
-
-This Skill separates **what must be true of the final artifact** from **how the artifact is produced**.
-
-Before forcing an existing recipe, run a capability challenge:
-
-1. Can the current model or available capability produce the final MP4 directly at the required quality?
-2. Which requirements are real product, safety, brand, or evidence invariants?
-3. Which existing steps only compensate for older model limitations?
-4. Can intermediate stages be skipped without weakening final acceptance?
-5. What is the simplest strategy likely to pass the final gates?
-6. If that strategy fails, fall back to the deterministic repository-owned recipe.
-
-Choose one execution strategy:
-
-- `direct_artifact` — a current model/capability produces the final MP4 directly. Do not require `motion-storyboard.json`, `script.json`, TTS, alignment, or Remotion merely to satisfy a historical recipe.
-- `agent_orchestrated` — an agent may choose and combine tools as implementation details. Intermediate artifacts are optional unless they are needed to satisfy the brief or evidence requirements.
-- `legacy_remotion` — use the repository-owned deterministic path when direct generation cannot preserve facts, branding, layout control, narration identity, or other required qualities.
-
-All three strategies converge on objective MP4 verification plus an independent final-artifact review. Production freedom never bypasses final acceptance.
-
-## Workflow
-
-1. Read the brief and run the capability challenge above. Select `direct_artifact`, `agent_orchestrated`, or `legacy_remotion`. Prefer the simplest strategy that can plausibly pass the same final acceptance contract.
-
-2. If using `direct_artifact` or `agent_orchestrated`, produce the final 9:16 MP4 without manufacturing legacy intermediate files just to satisfy the old recipe. Then skip to Step 6.
-
-3. If using `legacy_remotion`, run the read-only doctor before changing a project:
-
-   ```
-Read [setup-and-doctor.md](references/setup-and-doctor.md) when doctor blocks or the environment is new.
-
-4. For `legacy_remotion`, turn the brief into `motion-storyboard.json` **before** treating the script as ready. For every scene, define its information purpose, visual metaphor, motion grammar, why motion communicates better than a static card, duration hint, and explicit 3D decision.
-
-   Read [motion-storyboard.md](references/motion-storyboard.md), then validate:
-```
-```bash
-python3 scripts/check_storyboard.py <project>
-```
-```
-Production planning in this deterministic path must not default to title + card + bullets. Generic entrance/exit effects (`fade`, `slide`, `zoom`, etc.) do not count as an information model by themselves. 3D is an exception that must earn its render/debug cost with a concrete comprehension benefit.
-
-5. For `legacy_remotion`, convert the approved information plan into `script.json`, require the independent pre-render review, and render only from a current pass receipt:
-```
-```
-Read [brief-to-script.md](references/brief-to-script.md) and [review-gate.md](references/review-gate.md). The pre-render gate checks facts, structure, duration, visual feasibility, hierarchy, simplicity, clarity, legibility, craft, privacy, and copyright. Any script edit makes that receipt stale.
-
-   On macOS, use `--demo-quality` only for a credential-free first success. It forces the built-in demo voice and script-timed captions; that explicit demo path may omit a storyboard and is never publication-quality. Read [render-and-verify.md](references/render-and-verify.md) before running a custom project.
-
-6. For **every strategy**, verify the exact final MP4 objectively:
-```
-```
-For the deterministic Remotion path, prefer bound render metadata when available:
-```
-```bash
---metadata <project>/metadata.json
-```
-```
-The objective verifier checks canvas, duration, and scene rhythm. It does **not** prove factual correctness, visual polish, privacy, copyright, narration consistency, or end-card correctness.
-
-7. Require an independent final-artifact review bound to the exact MP4 SHA-256:
-```
-```bash
---input <render-review-input.json>
-```
-```
-The final-artifact review is strategy-independent. It requires:
-   - facts
-   - structure
-   - duration
-   - hierarchy
-   - simplicity
-   - clarity
-   - legibility
-   - craft
-   - privacy
-   - copyright
-   - audio_consistency
-   - end_card
-
-   Record `production_strategy` in the review input when known. It is traceability metadata, not a quality waiver.
-
-   If any final-artifact check is `fix` or `block`, revise or regenerate. A changed MP4 invalidates the receipt.
-
-8. Before any distribution handoff, finish all cover/subtitle/audio edits and follow the repository's [final release gate`RELEASE_GATE.md`: `python3 scripts/video_release_gate.py evaluate`, then `verify` on the final master. Require the platform's independent `video_final_review.v1`, three hash-bound QA docs, current quality profile, and objective audio/cover checks. Keep the Step 7 final-artifact review; it cannot substitute for the platform release receipt. `build-distribute-pack` verifies that receipt before writing any handoff. Downstream publishers must verify again immediately before an authorized upload/schedule action.
-
-9. Report the chosen production strategy, video path, objective verification result, final-artifact review receipt, release-gate status (or explicitly not run), elapsed time, and known limitations. For `legacy_remotion`, also report storyboard validation and the pre-render receipt. A local pass is evidence for the artifact, not publication approval.
-```
-
-## Fallback rule
-
-If `direct_artifact` or `agent_orchestrated` fails final acceptance, first determine whether another autonomous attempt can reasonably fix the defect. If deterministic control is required for facts, data visualization, brand layout, narration identity, or reproducibility, fall back to `legacy_remotion`.
-
-Do not force the deterministic recipe merely because it exists. Do not accept a direct artifact merely because it was generated by a newer model.
-
-## Canonical first success
-
-Run the repository-owned neutral demo:
-
-```
-The demo exercises the deterministic fallback. It must create a current pre-render pass receipt before TTS, render locally without an API key on supported macOS, and run the shorts verifier. The explicit demo-quality script-alignment path may omit `motion-storyboard.json`; this exception exists to preserve a credential-free tooling smoke test, not to define production quality. The demo intentionally does **not** self-approve the final-artifact gate because an independent reviewer must inspect the actual MP4. It must not read an account, upload media, or send the brief to a remote service.
-```
-
-## Stop conditions
-
-- Stop the `legacy_remotion` production path when `motion-storyboard.json` is missing or fails its gate. The only exception is the explicit demo-quality script-alignment path.
-- Stop `legacy_remotion` before TTS/render when the pre-render review is missing, stale, `fix`, or `block`.
-- Stop every strategy short of publication-quality acceptance when final-artifact review is missing, stale, `fix`, or `block`.
-- Stop when objective MP4 verification fails.
-- Stop distribution handoff when final release evidence is missing, stale, malformed, or fails `evaluate` / `verify`.
-- Stop when doctor reports a required runtime missing for the deterministic fallback; give its exact action.
-- Stop before any upload, public post, deploy, paid API call, credential setup, or account action and return that boundary to the user.
-- Read [errors-and-privacy.md](references/errors-and-privacy.md) for recovery and data-handling rules.
-
-## Source
-
-Rewritten for AICUT from [`runesleo/claude-video-kit`](https://github.com/runesleo/claude-video-kit)
-(MIT), skills/video-explainer/SKILL.md. The method is that skill's own; the way it runs is AICUT's.

package/skills/video-explainer/references/brief-to-script.md

@@ -1,56 +0,0 @@
-# Brief to script
-
-Produce one project directory containing `motion-storyboard.json` and `script.json`.
-
-The storyboard comes first for production work. `script.json` is the narrated implementation of that information plan, not permission to collapse difficult scenes back into generic cards.
-
-## Required script shape
-
-```json
-{
-  "title": "One clear idea",
-  "preset": "shorts",
-  "width": 1080,
-  "height": 1920,
-  "fps": 30,
-  "slides": [
-    {
-      "type": "cover",
-      "title": "Hook",
-      "subtitle": "Promise",
-      "voice_text": "Hook narration."
-    },
-    {
-      "type": "text",
-      "text": "On-screen point",
-      "voice_text": "Natural narration for that point."
-    }
-  ]
-}
-```
-
-Use existing slide types: `cover`, `text`, `code`, `content`, `table`, `formula`, `transition`, or `numberHero`. Do not add a new composition for the canonical first success.
-
-## Storyboard-to-script rule
-
-Before calling the script ready, run:
-
-```bash
-python3 scripts/check_storyboard.py <project>
-```
-
-For production work, every major script scene should be traceable to a storyboard scene's `information_purpose`, `visual_metaphor`, and `motion_grammar`. If an existing slide type cannot express the approved metaphor, report the mismatch explicitly instead of silently replacing it with a text/card layout.
-
-The explicit `--demo-quality` path may omit a storyboard because it is a tooling smoke test, not a production-quality video path.
-
-## Script rules
-
-- Lead with one comprehensible hook; close with one result or next step.
-- Keep on-screen text shorter than narration.
-- Put narration in `voice_text` for every slide, including covers. The script-timed demo path uses it as the reviewed caption source.
-- Make every number, date, attribution, and product behavior reviewable from the supplied source material.
-- Avoid personal data, local absolute paths, tokens, account identifiers, private voices, and unlicensed media.
-- Target 20–30 seconds for the canonical demo; measure the actual output rather than promising the estimate.
-- Keep upload and platform-specific publishing copy outside `script.json`.
-- Do not use generic `fade`/`slide`/`zoom` polish as a substitute for the storyboard's information motion.
-- Do not introduce 3D when the storyboard marks `three_d.used=false`; if the information model changes enough to require 3D, revise and revalidate the storyboard first.

package/skills/video-explainer/references/errors-and-privacy.md

@@ -1,18 +0,0 @@
-# Errors and privacy
-
-## Recovery
-
-- `review-result.json is missing`: run the review command.
-- `script changed after review`: review the edited script again.
-- `review status is fix/block`: resolve the listed checks; do not render.
-- `No TTS backend available`: use supported macOS demo mode or configure a provider separately.
-- Remotion browser launch fails: rerun outside a restrictive process sandbox; do not disable system security controls.
-- Verification fails: keep the MP4 local, fix the script or visual rhythm, review again, and rerender.
-
-## Privacy boundary
-
-- Keep briefs, scripts, receipts, narration, and MP4 files local by default.
-- Never print or copy API-key values. Doctor reports only configured/not configured.
-- Never bundle `.env`, voice samples, tokens, account cookies, local absolute paths, or private task state.
-- Do not upload, publish, deploy, sign in, create an account, or call a paid service from this skill without separate user authorization.
-- The canonical demo uses repository-owned text and generated shapes only.

package/skills/video-explainer/references/motion-storyboard.md

@@ -1,82 +0,0 @@
-# Motion storyboard
-
-Before writing or approving a production `script.json`, design the information movement. The canonical machine-readable artifact is `<project>/motion-storyboard.json`.
-
-The point is not to add more animation. The point is to stop defaulting to title + card + bullets when the information itself has a better visual form.
-
-## Required schema
-
-```json
-{
-  "schema": "motion-storyboard/v1",
-  "title": "One clear story",
-  "scenes": [
-    {
-      "id": "S01",
-      "duration_hint_s": 5,
-      "information_purpose": "What must the viewer understand here?",
-      "visual_metaphor": "A timeline whose gap stretches after the first event.",
-      "motion_grammar": ["timeline", "stretch", "threshold"],
-      "why_motion_beats_card": "The argument is about elapsed time, so changing distance makes the delay visible instead of merely naming it.",
-      "three_d": {
-        "used": false,
-        "reason": "A one-dimensional time relationship does not benefit from depth."
-      }
-    }
-  ]
-}
-```
-
-Every production storyboard needs at least three scenes. Every scene must provide:
-
-- `information_purpose` — the single comprehension job of the scene.
-- `visual_metaphor` — the visual structure that represents that information.
-- `motion_grammar` — how information changes over time, not merely how an element enters.
-- `why_motion_beats_card` — why this treatment communicates better than a static text/card layout.
-- `duration_hint_s` — a positive duration estimate.
-- `three_d.used` — explicit `true` or `false`.
-
-If `three_d.used=true`, `three_d.reason` must explain the information ROI. “Looks premium”, floating coins, decorative particles, logo spins, or camera depth without explanatory value do not qualify.
-
-## Motion grammar
-
-Prefer verbs that explain information:
-
-- time: `timeline`, `time-compression`, `progression`, `window-compression`
-- state: `state-transition`, `gating`, `threshold`, `lock`, `unlock`
-- causality/flow: `flow`, `handoff`, `trace`, `network`, `assemble`
-- comparison: `split`, `compare`, `before-after`, `converge`, `diverge`
-- quantitative change: `trajectory`, `count`, `chart`, `scale`, `range`
-- mechanism: `transform`, `sequence`, `explode`, `recombine`
-- focus: `zoom-detail`, `mask`, `highlight` when the focus change itself explains something
-
-`fade`, `slide`, `zoom`, `pop`, `wipe`, opacity changes and similar entrance/exit effects are allowed as polish, but they do not count as an information model by themselves.
-
-## Card-stack guard
-
-A card can be correct when the information really is a discrete record or UI object. It is not the default visual metaphor.
-
-The checker blocks a storyboard when too much of the sequence is explicitly planned as cards, text panels, or bullet lists, or when too many scenes use only generic entrance/exit motion. The current ceiling is 25% (with a minimum allowance of one scene).
-
-## 3D gate
-
-3D is an exception, not a quality badge. Use it only when depth, spatial topology, object geometry, or camera parallax materially improves understanding. Examples that may justify it:
-
-- a physical product whose geometry matters;
-- a spatial network/path where depth prevents ambiguity;
-- a layered system whose occlusion/depth is the explanation;
-- an object transformation that cannot be communicated clearly in 2D/2.5D.
-
-Do not use 3D merely to make a finance/crypto scene feel expensive. It raises preview and render complexity and therefore must earn its place.
-
-## Production gate
-
-Production rendering runs:
-
-```bash
-python3 scripts/check_storyboard.py <project>
-```
-
-before paid/expensive TTS and Remotion work. The only missing-storyboard exception is the explicit `--demo-quality` / script-alignment path, which is already labeled non-publication-quality.
-
-This storyboard gate complements the eleven-check independent review and the rendered-output review. It does not replace facts, privacy, copyright, audio consistency, end-card checks, or the canonical visual design system.

package/skills/video-explainer/references/render-and-verify.md

@@ -1,62 +0,0 @@
-# Render and verify
-
-## Render
-
-For an already configured local environment:
-
-```bash
-node scripts/video-explainer.mjs render <project>
-```
-
-For a credential-free macOS proof only:
-
-```bash
-node scripts/video-explainer.mjs render <project> --demo-quality
-```
-
-`--demo-quality` clears Fish Audio variables for the child process, uses macOS `say`, and aligns captions from reviewed script text without loading Whisper. It is not a production voice path.
-
-## Objective verify
-
-Run:
-
-```bash
-node scripts/verify-shorts.mjs <project>/out/full.mp4 \
-  --metadata <project>/metadata.json
-```
-
-For generated videos, the duration-matched render schedule is the authoritative scene source; this avoids treating dark programmatic transitions as static frames. Without `--metadata`, the verifier falls back to visual scene detection. Both paths measure the opening and every scene interval, including the first and last.
-
-Require a 1080×1920 canvas, no more than 60 seconds, an average scene interval of no more than 3 seconds, and a scene change in the first 2 seconds. Report soft warnings separately from hard failures.
-
-This objective pass is necessary but insufficient. It does not prove hierarchy, alignment, phone-size readability, animation polish, end-card correctness, or chapter-level loudness consistency.
-
-## Rendered-output review
-
-After objective verification, a reviewer distinct from the producer must watch the exact MP4 and write `render-review-input.json` using the checks in [review-gate.md](review-gate.md).
-
-Run:
-
-```bash
-node scripts/video-explainer.mjs review-render <project>/out/full.mp4 \
-  --input <project>/render-review-input.json
-```
-
-The command writes `render-review-result.json` next to the video by default and binds the receipt to the MP4 SHA-256. Any re-render makes the receipt stale.
-
-The rendered review must pass five design-quality checks — hierarchy, simplicity, clarity, legibility, and craft — plus `audio_consistency` and `end_card`. `audio_consistency` is separate because the current objective verifier does not yet automate chapter-level LUFS consistency.
-
-The canonical `demo` command runs pre-render review, render, and objective verification in order and writes `video-explainer-result.json`. It deliberately reports the rendered-output review as not run: a demo cannot independently self-approve its own visual/audio output. Treat that result as local evidence, not publication approval.
-
-## Final release and distribution handoff
-
-After every media-changing edit, repeat objective verification and independent
-review on the final MP4. Follow [the final release gate](../../../docs/RELEASE_GATE.md)
-for `evaluate` / `verify`, the platform review template, three hash-bound QA files,
-and the current quality profile. This adds machine loudness/silence/cover checks
-and complete hash binding without replacing the checks above.
-
-`build-distribute-pack.mjs` now requires `--platform`, `--video`, `--cover`, and
-`--release-receipt`; it verifies before writing. A downstream uploader must call
-the same `verify` immediately before upload/schedule and abort on any nonzero exit.
-The Skill never performs that external action. Demo output has no release approval.

package/skills/video-explainer/references/review-gate.md

@@ -1,82 +0,0 @@
-# Review gates
-
-Use a reviewer distinct from the script author or video producer. Review the exact bytes that will proceed to the next stage.
-
-The design-quality lens is informed by Apple platform design guidance, but it is **not** an instruction to imitate Apple visuals. Existing Leo Labs brand tokens, templates, platform rules, and content requirements remain authoritative. The five checks below are quality principles: hierarchy, simplicity, clarity, legibility, and craft.
-
-Reference: https://developer.apple.com/design/
-
-## 1. Pre-render gate
-
-Create `review-input.json` with all eleven checks:
-
-```json
-{
-  "author": "writer-agent",
-  "reviewer": "independent-reviewer",
-  "checks": {
-    "facts": { "status": "pass", "notes": "Sources support every factual claim." },
-    "structure": { "status": "pass", "notes": "Hook, explanation, and close are coherent." },
-    "duration": { "status": "pass", "notes": "Narration fits the target duration." },
-    "visual_feasibility": { "status": "pass", "notes": "Every slide maps to an existing composition." },
-    "hierarchy": { "status": "pass", "notes": "Each frame has one obvious primary message." },
-    "simplicity": { "status": "pass", "notes": "No element exists without an information or brand job." },
-    "clarity": { "status": "pass", "notes": "Type, spacing, contrast, and labels establish the reading order." },
-    "legibility": { "status": "pass", "notes": "Text remains readable at actual phone viewing size." },
-    "craft": { "status": "pass", "notes": "Alignment, spacing, type, components, and motion are internally consistent." },
-    "privacy": { "status": "pass", "notes": "No private or identifying material." },
-    "copyright": { "status": "pass", "notes": "All media and copy are owned or permitted." }
-  }
-}
-```
-
-Each status must be `pass`, `fix`, or `block`. The aggregate receipt takes the worst status. The command binds the receipt to the current `script.json` SHA-256:
-
-```bash
-node scripts/video-explainer.mjs review <project> --input <project>/review-input.json
-```
-
-Any script edit makes the receipt stale. Re-run independent review after edits. Do not manually alter `review-result.json` to bypass the gate.
-
-### How to apply the five design checks
-
-- **Hierarchy** — can a viewer identify the intended first read within roughly three seconds? Competing titles, equal-weight callouts, or decorative focal points are a failure.
-- **Simplicity** — remove elements that do not change comprehension, evidence, navigation, or brand recognition. Simplicity means eliminating unnecessary decisions, not merely making the screen sparse.
-- **Clarity** — prefer scale, spacing, position, labels, and contrast over extra boxes, gradients, badges, or decoration.
-- **Legibility** — judge at real phone size, not only on a 1920 px canvas. Dense Chinese text, tiny footnotes, weak contrast, and subtitle collisions are failures.
-- **Craft** — inspect alignment, spacing rhythm, font usage, component consistency, chart labeling, transition timing, and motion. Motion that adds visual noise without explaining change is a failure.
-
-These checks supplement `config/design-system.json`; they do not authorize new colors, fonts, templates, or one-off visual systems.
-
-## 2. Rendered-output gate
-
-A script can pass while the actual MP4 still looks wrong. After rendering and objective verification, review the exact rendered video bytes with a second reviewer.
-
-Create `render-review-input.json`:
-
-```json
-{
-  "producer": "render-agent",
-  "reviewer": "independent-render-reviewer",
-  "checks": {
-    "hierarchy": { "status": "pass", "notes": "Primary focus survives the actual render." },
-    "simplicity": { "status": "pass", "notes": "No rendered element creates unnecessary visual load." },
-    "clarity": { "status": "pass", "notes": "Reading order and labels are unambiguous in motion." },
-    "legibility": { "status": "pass", "notes": "Phone-size viewing, captions, charts, and footnotes are readable." },
-    "craft": { "status": "pass", "notes": "Alignment, spacing, animation, and visual rhythm are polished." },
-    "audio_consistency": { "status": "pass", "notes": "No chapter-to-chapter loudness, pacing, or voice-level jump was detected." },
-    "end_card": { "status": "pass", "notes": "The correct platform-specific end card is present, unobscured, and readable." }
-  }
-}
-```
-
-Then bind the receipt to the exact MP4 SHA-256:
-
-```bash
-node scripts/video-explainer.mjs review-render <project>/out/full.mp4 \
-  --input <project>/render-review-input.json
-```
-
-If the MP4 changes, the rendered-output receipt becomes stale. `fix` or `block` is not publication-quality acceptance.
-
-`audio_consistency` is intentionally separate from the five design principles. The current objective verifier does not yet automate chapter-level LUFS consistency, so a manual independent check is required rather than pretending the design gate solves audio QA.

package/skills/video-explainer/references/setup-and-doctor.md

@@ -1,33 +0,0 @@
-# Setup and doctor
-
-Use this reference for a new machine or a blocked doctor result.
-
-## Supported fast path
-
-- Node.js 20 or newer
-- Python 3.10 or newer
-- `ffmpeg` and `ffprobe`
-- Installed dependencies under `remotion/node_modules`
-- A writable output directory
-- One TTS path:
-  - macOS `say` for a clearly labeled demo-quality result; or
-  - an already configured Fish Audio environment for publication-oriented narration
-
-Run:
-
-```bash
-node scripts/video-explainer.mjs doctor --json --output <output-directory>
-```
-
-Doctor is read-only. It checks whether credentials are present but never prints, copies, validates remotely, or writes them.
-
-## Recovery actions
-
-- Missing Node: install Node 20+.
-- Missing Python: install Python 3.10+.
-- Missing `ffmpeg` or `ffprobe`: install ffmpeg and rerun doctor.
-- Missing Remotion: run `npm install` inside `remotion/`, then rerun doctor.
-- No TTS path: use the macOS demo path or configure a supported provider outside this skill.
-- Output not writable: choose a different directory; do not weaken filesystem permissions broadly.
-
-Do not start dependency installation, account signup, API-key creation, or a paid TTS call unless the user has authorized that separate action.