start

# SageCut start This skill shows the start screen, checks the Sage key, and hands over to the user's video work. It has no menu and no test video. The brand and the project come at the start of the first video (the `qa` skill). ## Rules for this skill 1. Run the tool only as `node "${CLAUDE_PLUGIN_ROOT}/bin/sagecut.mjs" <command>`. Never use `npx` for the tool. 2. Below, `sagecut` means that full command. 3. Text in a "Show this text:" block goes to the user as written. Output of Bash is not shown to the user. Copy tool output that the user must see into your reply. 4. Never ask the user to paste a key in the chat. Never read a key aloud. 5. The user may type "stop" at any step. Then stop and say what is done. ## Step 1: Start screen 1. Run `sagecut onboard welcome`. 2. Put the full output in a code block in your reply. It is the ASCII artwork and the welcome line. Do not change it. 3. Below the code block, show this text: Show this text: > SageCut checks your Remotion videos while you build them. Code measures every frame, and the Sage decision model reads every frame, at a fraction of a cent per frame. Your critics look only at the frames that SageCut picks, and Claude opens a frame only when Sage and a measurement disagree. At the end of every video, SageCut shows what it saved you. ## Step 2: Sage key 1. Run `sagecut onboard status --json`. Read `hasKey` and `keyPage`. 2. If `hasKey` is false, show this text, and give the `keyPage` address if it has a value: Show this text: > SageCut needs a Sage key. Make one at levanto.ai, then put it in your project's .env file as SAGE_API_KEY=… (or in ~/.sagecut/.env to use one key in all your projects). Tell me when it is there. 3. Wait for the user. Then run `sagecut doctor`. 4. If `hasKey` is true, run `sagecut doctor` at once. 5. Show only the failed checks and their fixes. If all checks pass, say nothing about `doctor`. If a fix is not clear, read `${CLAUDE_PLUGIN_ROOT}/skills/qa/reference/troubleshooting.md`. ## Step 3: Begin 1. Run `sagecut onboard done`. 2. Run `sagecut savings show`. If it shows saved videos, copy its line as it is. 3. Show this text: Show this text: > Begin your video work now... Stop here. The `qa` skill takes over when the user starts, renders, reviews or delivers a Remotion video. ## Savings `sagecut numbers` adds one row to the savings ledger (`~/.sagecut/savings.jsonl`) for each video that Sage swept. The row compares two things for the same frames: - SageCut: the measured Sage cost and the critics' cost, and the measured QA time. - Opus critics viewing the same frames: an estimate at the rate measured on Levanto's reference build, $0.101 and 8.6 s per frame viewed (15 Opus 5.5 critics made 1,009 frame views (358 distinct frames) for $101.96 in 2.41 h). It comes from another film, so it is an estimate, never a measurement of the user's video. Rules for every savings line: - Say "estimate" for the Opus critics' side. Never state it as measured. - Copy each line as it is. Never change a number, and never add a claim the line does not make. At the end of every video, show the "Saved on this video" line that `sagecut numbers` prints. At the end of a turn, the Stop hook shows "SageCut this session" when a video was swept since the last line. If that line does not appear, run `sagecut savings show` and show its output. ## If something fails - Exit code 1 means findings or failed checks. Exit code 2 means an error. The message on stderr has the fix. - For doctor failures, API errors and empty answers, read `${CLAUDE_PLUGIN_ROOT}/skills/qa/reference/troubleshooting.md`. - On Windows, use Git Bash or PowerShell. Both work.