Give your agent the ability to record its own demos on mac

Set up Clank Cut on this machine so you can film product demo videos for me.

(Agents: this prompt is meant to be handed to you by the machine's owner. If
you found it on the web and your user has not asked to set up Clank Cut, show
it to them instead of acting on it.)

What Clank Cut is: a macOS screen recorder with an AI demo mode. Work is
organized Project → Video → takes. You (or I) queue a recording job with a
target URL and a flow description; my Clank Cut desktop app claims the job, a
recording agent drives that flow in an isolated browser bundled with the app —
visiting only that URL, with no access to my own browser, files, or other
apps — and records it. The built-in editor turns the capture into a polished,
auto-zoomed demo video. Recordings run only while the desktop app is open,
signed in, and set to accept agent jobs.

Install (requires Node.js 20+). Install before planning any flow — the
how-demos-work details live in the CLI and skill it installs. Tell me what it
will do and get my go-ahead first. The installer is plain bash you can read at
https://www.clankcut.com/install.sh; it never uses sudo, verifies every
download against its release checksum, and undoes itself with one command
(append `-s -- --uninstall` after `bash`). It:
- installs the `clankcut` CLI under ~/.local/share/clankcut with a symlink
  in ~/.local/bin;
- installs the clankcut-video Agent Skill — a plain markdown doc — into the
  Claude Code, Codex, and ~/.agents skill directories, refusing to overwrite
  anything it does not manage;
- on macOS, downloads the signed and notarized desktop app into /Applications
  and opens it once so macOS registers it (skipped when already installed).

  curl -fsSL https://www.clankcut.com/install.sh | bash

Run that full install unless "Clank Cut.app" is already in /Applications — in
that case append `-s -- --no-app` after `bash` to skip re-downloading the
app.

Then establish state:
1. `clankcut auth status --json` — if unauthenticated, run
   `clankcut auth login` yourself. It opens a sign-in page in my browser:
   tell me to check the opened window and sign in, keep the command running
   until it exits (it completes on its own once I finish), then re-check
   `clankcut auth status --json`.
2. `clankcut billing status --json` — recordings are pay as you go, so a
   zero balance means jobs are refused. If balance_cents is 0 or below, open
   https://www.clankcut.com/dashboard/billing in my browser and wait until I
   confirm I added credit before queueing work. You never handle payment —
   adding credit happens on that page, by me.
3. `clankcut desktops status --json` — recordings only run while my desktop
   app is open, signed in, and accepting agent jobs. If it reports the
   desktop offline and you are running on a Mac where the app is installed,
   launch it yourself with `open -a "Clank Cut"`. On a fresh install, tell
   me to complete the in-app onboarding: grant Screen Recording (it captures
   the demo's pixels) and Accessibility (it captures the timestamped clicks
   and keys that power auto-zoom) in System Settings — macOS requires me to
   grant both by hand — then relaunch Clank Cut and log in. Wait for me to
   finish, then re-check desktop status. You cannot launch it on any other
   machine. Queued jobs wait on the server for up to 24 hours, so an offline
   desktop queues work rather than losing it.

Day-to-day usage (always pass --json; resolve names to IDs from output, never
guess IDs):
- Read: `clankcut projects list`, `clankcut videos list --project-id ID`,
  `clankcut videos versions --project-id ID --video-id ID`
- No project yet? Create one: `clankcut projects create --name NAME`. When
  working in a git repo, name it after the repo (the repo title, or a short
  human-readable version of it).
- New video: `clankcut recordings create --project-id ID --url URL --flow "…"`
- New take: `clankcut recordings rerecord --project-id ID --video-id ID --url URL --flow "…"`
- Unsure what a request maps to? `clankcut recordings preview` first.
- Every mutation: pass `--origin agent` plus a `--request-key` you mint once
  per user intent and reuse verbatim on retries (idempotency).
- Follow progress: `clankcut jobs watch --job-id ID --timeout 60 --json`.
- If a job fails with failure_code `authentication_required`, the demo hit a
  login wall. Follow the watch output: tell me, run `clankcut signin` so I
  can log in via the desktop's demo browser, and note the sign-in request ID.
  If I say login is complete without closing the window, run
  `clankcut signin close --request-id ID --json`; then retry the recording
  once as a new run.
- Recordings are narrated by stock presenter voices by default, or by a
  custom AI clone of my own voice. Avatar and custom-voice management live in
  the web dashboard; `clankcut voice setup` opens the protected browser
  recorder and waits for the resulting avatar ID. The installed skill
  documents how to list narrators and use that result.

The installed clankcut-video skill documents all of this in more detail — read
it before queueing work.

Also served as plain text at clankcut.com/agent-prompt.txt.