One package: the install line is npm i -D @vosjs/cli

README.md

@@ -21,20 +21,20 @@ add the repo as a plugin marketplace: `/plugin marketplace add vosjs/skills`.
 
 | Skill | What it does | Needs |
 | --- | --- | --- |
-| [`product-video`](skills/product-video/SKILL.md) | Record and produce a shippable product demo video of a website, app, or feature: the agent drives the browser from a JSON script, the recording auto-plans zooms, and every edit is a JSON patch on `doc.json`. One take also yields exact-size store screenshots, tiles, and social stills. | `npm i -D @vosjs/cli @vosso/vos-plugin`, a Chromium, network |
+| [`product-video`](skills/product-video/SKILL.md) | Record and produce a shippable product demo video of a website, app, or feature: the agent drives the browser from a JSON script, the recording auto-plans zooms, and every edit is a JSON patch on `doc.json`. One take also yields exact-size store screenshots, tiles, and social stills. | `npm i -D @vosjs/cli`, a Chromium, network |
 | [`vos-authoring`](skills/vos-authoring/SKILL.md) | Author vos animation programs (VosConfigJson) from scratch: schema, dialect rules, params/presets knobs, local validation with `@vosjs/core`. | `npm i @vosjs/core` (validation), `@vosjs/cli` (render) |
-| [`vos-remix`](skills/vos-remix/SKILL.md) | Remix a program from the vos.so gallery: fetch its config, edit knobs or code, validate locally, push a private copy back with lineage — then iterate it as versions. Ships the params/Looks doctrine (2–4 intent-named knobs, every knob verified to act). | `npm i -D @vosjs/cli @vosso/vos-plugin`, a content key or remix grant |
-| [`vos-create`](skills/vos-create/SKILL.md) | Create vos programs in the user's own style: pull their vos.so folder, read every recipe (`.md`) and exemplar in it, find the declared seed, author work that follows them, check and render and judge locally, and push into that folder as attributed private versions. Recipes carry the style; the user's ask decides what gets made. | `npm i -D @vosjs/cli @vosso/vos-plugin`, a content key, a folder on vos.so |
-| [`vos-cut`](skills/vos-cut/SKILL.md) | Cut a screen recording somebody made into a product video, from its evidence: `vos digest` lists the moments the cursor track says mattered with a footage frame and a crop each, the agent narrates them into beats, edits `doc.json` by exception over the planners, verifies with stills, pushes an attributed version, and iterates with the human through the version chain. A signed-off take becomes a series' seed: its folder's `CUT.md` carries the judgment, `vos plan --style` carries the numbers. | `npm i -D @vosjs/cli @vosso/vos-plugin`, a Chromium, a content key for hosted takes |
-| [`launch-kit`](skills/launch-kit/SKILL.md) | One take → the full launch asset kit: YouTube demo + thumbnail, X/LinkedIn cuts, Chrome Web Store screenshots + tiles, Product Hunt gallery, GitHub README loop, OG cards. Per-channel specs ship as data and every asset is verified against them in a `kit.json` manifest. | `npm i -D @vosjs/cli @vosso/vos-plugin`, ffmpeg, a finished take |
-| [`vos-migrate`](skills/vos-migrate/SKILL.md) | Turn an existing Loom, Screen Studio, Cap, or plain mp4/webm screen demo into an editable vosso take, so the next version is a re-render instead of a re-recording. | `npm i -D @vosjs/cli @vosso/vos-plugin`, the file |
-| [`vos-footage`](skills/vos-footage/SKILL.md) | Hand a Remotion, HyperFrames, or any video composition a clean full-bleed clip of the real product, recorded and auto-zoomed with vos, always backed by an editable take on the maker's shelf. | `npm i -D @vosjs/cli @vosso/vos-plugin`, a Chromium, a content key |
+| [`vos-remix`](skills/vos-remix/SKILL.md) | Remix a program from the vos.so gallery: fetch its config, edit knobs or code, validate locally, push a private copy back with lineage — then iterate it as versions. Ships the params/Looks doctrine (2–4 intent-named knobs, every knob verified to act). | `npm i -D @vosjs/cli`, a content key or remix grant |
+| [`vos-create`](skills/vos-create/SKILL.md) | Create vos programs in the user's own style: pull their vos.so folder, read every recipe (`.md`) and exemplar in it, find the declared seed, author work that follows them, check and render and judge locally, and push into that folder as attributed private versions. Recipes carry the style; the user's ask decides what gets made. | `npm i -D @vosjs/cli`, a content key, a folder on vos.so |
+| [`vos-cut`](skills/vos-cut/SKILL.md) | Cut a screen recording somebody made into a product video, from its evidence: `vos digest` lists the moments the cursor track says mattered with a footage frame and a crop each, the agent narrates them into beats, edits `doc.json` by exception over the planners, verifies with stills, pushes an attributed version, and iterates with the human through the version chain. A signed-off take becomes a series' seed: its folder's `CUT.md` carries the judgment, `vos plan --style` carries the numbers. | `npm i -D @vosjs/cli`, a Chromium, a content key for hosted takes |
+| [`launch-kit`](skills/launch-kit/SKILL.md) | One take → the full launch asset kit: YouTube demo + thumbnail, X/LinkedIn cuts, Chrome Web Store screenshots + tiles, Product Hunt gallery, GitHub README loop, OG cards. Per-channel specs ship as data and every asset is verified against them in a `kit.json` manifest. | `npm i -D @vosjs/cli`, ffmpeg, a finished take |
+| [`vos-migrate`](skills/vos-migrate/SKILL.md) | Turn an existing Loom, Screen Studio, Cap, or plain mp4/webm screen demo into an editable vosso take, so the next version is a re-render instead of a re-recording. | `npm i -D @vosjs/cli`, the file |
+| [`vos-footage`](skills/vos-footage/SKILL.md) | Hand a Remotion, HyperFrames, or any video composition a clean full-bleed clip of the real product, recorded and auto-zoomed with vos, always backed by an editable take on the maker's shelf. | `npm i -D @vosjs/cli`, a Chromium, a content key |
 
-One CLI, two packages: `@vosjs/cli` is the MIT `vos` binary and the engine
-verbs (local, no account); `@vosso/vos-plugin` adds everything else — the
-take pipeline (record, plan, frames, render on screen recordings) and the
-vos.so platform verbs (fetch, push, pull, login). Both are MIT: everything
-that runs on your machine is open source, and vos.so, the hosted platform,
+One CLI, one package: `@vosjs/cli` is the MIT `vos` binary with the engine
+verbs (local, no account), the take pipeline (record, plan, frames, render
+on screen recordings) and the vos.so platform verbs (fetch, push, pull,
+login). Everything that runs on your machine is open source, and vos.so,
+the hosted platform,
 is the product. (The plugin was previously published as `@vosso/cli`; that
 name keeps working as a forwarding shim.)
 

evals/launch-kit/RUN.md

@@ -17,7 +17,7 @@ one; what changes is the skill, the CLI and the model.
 - A vos.so project the pushes land in, holding a `BRAND.md`, or none:
   S0 requires the agent to witness the brand from the product's site
   (`vos brand <url>`), and whether it did is a finding either way.
-- In the run directory: `npm i -D @vosjs/cli @vosso/vos-plugin`
+- In the run directory: `npm i -D @vosjs/cli`
   (plugin ≥ 0.20.0, the version `vos validate <kit.json>` arrived in),
   ffmpeg on PATH, system Chrome, a content key in `VOS_API_KEY`. Record
   the two package versions in the results file.

evals/launch-kit/scenarios.md

@@ -4,7 +4,7 @@ Run before each release tag, on ≥2 model tiers. Environment: a directory
 containing a finished take (provide a fixture take with a tuned doc.json,
 recorded at 2560×1440 — the skill's own viewport rule), a vos.so project
 folder holding a `BRAND.md`, the skill installed via
-`npx skills add vosjs/skills`, `npm i -D @vosjs/cli @vosso/vos-plugin`,
+`npx skills add vosjs/skills`, `npm i -D @vosjs/cli`,
 ffmpeg on PATH, system Chrome, a content key in `VOS_API_KEY`. Record runs
 in `results/` plus a no-skill baseline note.
 

evals/product-video/scenarios.md

@@ -2,7 +2,7 @@
 
 Run before each release tag, on ≥2 model tiers. Environment for every
 scenario: a clean directory outside any vos checkout, the skill installed via
-`npx skills add vosjs/skills`, the CLI via `npm i -D @vosjs/cli @vosso/vos-plugin`,
+`npx skills add vosjs/skills`, the CLI via `npm i -D @vosjs/cli`,
 network available, a Chromium present. Record each run in `results/` (model,
 date, pass/fail, notes). Also run each prompt once WITHOUT the skill and note
 the baseline delta.

evals/vos-create/scenarios.md

@@ -2,7 +2,7 @@
 
 Run before each release tag, on ≥2 model tiers. Environment: clean
 directory, skill installed via `npx skills add vosjs/skills`,
-`npm i -D @vosjs/cli @vosso/vos-plugin`, a content key in `VOS_API_KEY`
+`npm i -D @vosjs/cli`, a content key in `VOS_API_KEY`
 (scoped test account) whose shelf holds one folder with a `DESIGN.md`, a
 `TASTE.md` and one signed-off member. Record runs in `results/` plus a
 no-skill baseline note.

evals/vos-cut/scenarios.md

@@ -2,7 +2,7 @@
 
 Run before each release tag, on ≥2 model tiers. Environment: clean
 directory, skill installed via `npx skills add vosjs/skills`,
-`npm i -D @vosjs/cli @vosso/vos-plugin`, a Chromium, a content key in
+`npm i -D @vosjs/cli`, a Chromium, a content key in
 `VOS_API_KEY` (scoped test account) whose shelf holds one hosted take
 (60-120s, recorded with the extension, a cursor track) and one folder with
 a signed-off take, a `CUT.md` and a `BRAND.md`. Record runs in `results/`

evals/vos-footage/scenarios.md

@@ -2,7 +2,7 @@
 
 Run before each release tag, on ≥2 model tiers. Environment: clean
 directory, the skill installed via `npx skills add vosjs/skills`,
-`npm i -D @vosjs/cli @vosso/vos-plugin`, a content key, network, a Chromium.
+`npm i -D @vosjs/cli`, a content key, network, a Chromium.
 Record runs in `results/` plus a no-skill baseline note.
 
 ## S1 — footage for a composition

evals/vos-migrate/scenarios.md

@@ -4,7 +4,7 @@ Run before each release tag, on ≥2 model tiers. Environment: a clean
 directory holding one foreign screen-demo file (a 1080p H.264 mp4 with no
 vosso lineage — a real Loom/Screen Studio export when available), the skill
 installed via `npx skills add vosjs/skills`,
-`npm i -D @vosjs/cli @vosso/vos-plugin`, ffmpeg on PATH, a content key.
+`npm i -D @vosjs/cli`, ffmpeg on PATH, a content key.
 Record runs in `results/` plus a no-skill baseline note.
 
 ## S1 — the full migration

evals/vos-remix/scenarios.md

@@ -2,7 +2,7 @@
 
 Run before each release tag, on ≥2 model tiers. Environment: clean
 directory, skill installed via `npx skills add vosjs/skills`,
-`npm i -D @vosjs/cli @vosso/vos-plugin`, a content key in `VOS_API_KEY` (scoped test
+`npm i -D @vosjs/cli`, a content key in `VOS_API_KEY` (scoped test
 account). Record runs in `results/` plus a no-skill baseline note.
 
 ## S1 — the full loop against production

skills/launch-kit/SKILL.md

@@ -15,7 +15,7 @@ at every resolution up to 4K, no watermark; the engine is MIT.
 ## Setup
 
 ```bash
-npm i -D @vosjs/cli @vosso/vos-plugin    # the vos CLI (take pipeline included)
+npm i -D @vosjs/cli    # the vos CLI (take pipeline included)
 ```
 
 `ffmpeg` on PATH covers what the CLI does not emit (the PH hover-GIF,
@@ -175,7 +175,7 @@ video), never from intent:
 
 ```bash
 node -e '
-const specs = require("@vosso/vos-plugin/schema/channel-specs.json").specs
+const specs = require("./node_modules/@vosjs/cli/schema/channel-specs.json").specs
 const kit = require("./kit/kit.json")
 let bad = 0
 for (const a of kit.assets) {

skills/launch-kit/references/channel-specs.md

@@ -1,6 +1,6 @@
 # Channel specs — readable mirror
 
-Source of truth: `schema/channel-specs.json` in the `@vosso/vos-plugin` npm
+Source of truth: `schema/channel-specs.json` in the `@vosjs/cli` npm
 package (loop over the JSON, don't hand-type from this table). Verified
 against official platform docs 2026-08-04 — platform specs drift, so
 re-verify quarterly against the channels' current docs.

skills/product-video/SKILL.md

@@ -16,13 +16,14 @@ its quality loop and judge stills multimodally.
 ## Setup
 
 ```bash
-npm i -D @vosjs/cli @vosso/vos-plugin
+npm i -D @vosjs/cli
 ```
 
-One command, two packages: `@vosjs/cli` is the open source (MIT) `vos`
-binary and engine verbs; `@vosso/vos-plugin` adds the take pipeline used
-here (record / plan / frames / render on screen recordings) plus the vos.so
-platform verbs, MIT as well. Requirements:
+One command, one package: `@vosjs/cli` is the open source (MIT) `vos`
+binary with the engine verbs, the take pipeline used here (record / plan /
+frames / render on screen recordings) and the vos.so platform verbs. (Until
+0.9 the take pipeline shipped separately as `@vosso/vos-plugin`; a project
+that still lists it can drop it.) Requirements:
 
 - **A Chromium**: system Chrome is found automatically; otherwise
   `npx playwright install chromium` or point `VOS_BROWSER_PATH` at one.
@@ -103,7 +104,7 @@ Per-channel dimensions and byte budgets: `references/destinations.md`.
    record+render verb — fine for a quick first pass, but THIS skill's loop
    reviews frames before rendering, so prefer the separate verbs here.)
 
-4. **Tune `doc.json`** (JSON Schema ships in the `@vosso/vos-plugin` npm package:
+4. **Tune `doc.json`** (JSON Schema ships in the `@vosjs/cli` npm package:
    `schema/doc.schema.json`):
    - `zoom`: `[{in, out, level, cx, cy, source}]`, SOURCE seconds; levels
      1.4–2.8; `cx/cy` NORMALIZED [0..1] (0.5,0.5 = center) — NOT pixels; set

skills/product-video/references/destinations.md

@@ -8,7 +8,7 @@ lands. All assets come from ONE take — pick apex moments with
 
 **Producing a full launch kit?** Use the `launch-kit` skill from this
 repo — it drives the whole per-channel loop against the machine-readable
-spec sheet (`schema/channel-specs.json` in `@vosso/vos-plugin`) and verifies
+spec sheet (`schema/channel-specs.json` in `@vosjs/cli`) and verifies
 every asset in a manifest. The tables below are the quick reference for
 one-off cuts.
 

skills/vos-create/SKILL.md

@@ -21,7 +21,7 @@ contents; the shelf is the record.
 ## Setup
 
 ```bash
-npm i -D @vosjs/cli @vosso/vos-plugin   # folder, fetch, check, still, render, push
+npm i -D @vosjs/cli   # folder, fetch, check, still, render, push
 ```
 
 Credentials, in this order, never printed: `VOS_API_KEY`, then the first

skills/vos-cut/SKILL.md

@@ -20,7 +20,7 @@ in the note and stop.
 ## Setup
 
 ```bash
-npm i -D @vosjs/cli @vosso/vos-plugin   # fetch, digest, plan, frames, render, push, pull
+npm i -D @vosjs/cli   # fetch, digest, plan, frames, render, push, pull
 ```
 
 Credentials, in this order, never printed: `VOS_API_KEY`, then the first

skills/vos-remix/SKILL.md

@@ -15,7 +15,7 @@ compiles, and renders a preview.
 ## Setup
 
 ```bash
-npm i -D @vosjs/cli @vosso/vos-plugin   # the fetch/check/push/pull loop
+npm i -D @vosjs/cli   # the fetch/check/push/pull loop
 ```
 
 No browser needed for this loop (rendering previews happens on the