# Make a product video with vosso

You are a coding agent, and a person handed you this address. Do the steps
in order and tell them what happened after each one. Nothing here needs an
account until step 5. Here to bring a video made in Remotion or HyperFrames
instead? That is the vos-port skill: https://vos.so/llms.txt routes to it.

1. Install, in this repo: `npm i -D @vosjs/cli` (the vos CLI: records and
   renders on this machine, no account), then `npx vos setup`. It puts
   the vos skills into your own skill directories (`npx skills add vosjs/skills`;
   the product-video skill carries the whole loop below), finds a browser
   or installs one, writes one block into AGENTS.md, and ends with
   `vos doctor`, which says in words what is ready and what to do next.
2. Find the product: the repo's dev server (its package.json scripts, its
   README), else ask for a URL. Start it if it is not running, and check
   the page answers before you script anything.
3. Record it, the product-video skill's way. Write actions.json (the click
   path: wait, hover, click, type, scroll), rehearse it with
   `npx vos record --actions actions.json --out take --dry-run`, then
   record with `--strict`. The take plans its own zooms from the cursor
   track; `npx vos frames take --at-zooms` gives you stills to judge
   before any render. If the page is behind a login, walk the "Sessions"
   ladder in https://vos.so/llms-full.txt; never type a real password.
4. Open it for the person: `npx vos open take` serves the take into the
   studio at https://vos.so with doc.json intact, where every zoom can be
   dragged. Say where it opened, and tell them that the first time Chrome
   asks to let vos.so reach their local
   network, they allow it. Edits are patches to take/doc.json and a
   re-render, never a re-recording.
5. Only when the person asks for a link, a watch page, their shelf or a
   cloud render: `npx vos push take`. A credential resolves in this order:
   the VOS_API_KEY environment variable, then ~/.config/vos/credentials,
   then `npx vos login`, which prints a code and https://vos.so/cli/auth;
   relay both to the person and keep it running. Never print a credential.
6. Local by default: never upload a recording or push a vos unless asked
   for sharing, hosting or cloud rendering. A take comes first; a
   credential comes last.

Reference: https://vos.so/llms.txt routes by ask, https://vos.so/llms-full.txt
is the complete CLI contract, and https://vos.so/agents.md says what this site
offers an agent. Something broke on you? POST https://vos.so/api/product-feedback
with { "kind": "problem", "message": "<what happened>", "surface": "cli" }.