cueframe 0.3.0 → 0.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cueframe",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Agent-native CLI for CueFrame \u2014 author compositions and render video from the terminal (early-access preview).",
   "keywords": [
     "cueframe",

package/skills/_connect.md

@@ -0,0 +1,30 @@
+<!--
+SSOT for the "how do I connect to CueFrame" block that every task skill states.
+
+Not a skill: both readers skip non-directories (generate-skills.mjs checks
+`entry.isDirectory()`, install.ts checks for `<name>/SKILL.md`), so a bare file
+here is inert.
+
+Edit THIS file, then run:
+
+  node services/scripts/generate-skill-connect.mjs
+
+WHY THIS EXISTS. The block lived in 7 hand-maintained copies. On 2026-08-04 the
+landing page was corrected to stop telling non-Claude agents to paste
+`set up https://cueframe.ai/skill.md` (a Claude Code convention — ChatGPT replies
+that it does not support skills files), and all 7 skills kept saying it, because
+that sweep searched landing/ and docs/ and never searched packages/cli/skills/.
+Worse, the untouched lines had already drifted into FIVE different phrasings of
+the Claude Code step. One fact, seven copies, five versions.
+
+`skill-connect.drift.test.ts` fails if any copy diverges from this file.
+-->
+- **Claude Code:** offer to run
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
+- **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
+  `https://api.cueframe.ai/v1/mcp`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.

package/skills/add-music-bed/SKILL.md

@@ -22,13 +22,17 @@ cuts moved onto its beat grid. Attribution included, levels disciplined, one re-
 Listen first — identify what audio the composition already has before proposing anything. When
 the first tool call approaches and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — browser OAuth,
-  one **Allow**.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Then back to the soundtrack — this is usually a one-sitting job.
 

package/skills/brand-reel/SKILL.md

@@ -14,13 +14,17 @@ beat, tagline lockup — where every graphic could belong to this brand and no o
 Talk brand first — palette, type, the one line they'd put on a poster — before any setup. When
 the first tool call approaches and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` (browser OAuth, one
-  **Allow** click).
-- **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector pointing at
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
+- **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Then pick the brand conversation back up where it paused — connection is the smallest step in
 this job.

package/skills/clip-a-talking-head/SKILL.md

@@ -14,13 +14,17 @@ dead air, and caption every word from the real transcript.
 Get the source URL and what "best moment" means to the user before any setup ceremony. When the
 first tool call is close and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — browser opens,
-  user clicks **Allow**.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Then straight back to hunting the moment — setup is a footnote, not a phase.
 

package/skills/every-format-from-one-edit/SKILL.md

@@ -15,13 +15,17 @@ are made once; the formats are a job, not a re-edit.
 Confirm which master and which target platforms before setup. When the first tool call
 approaches and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — browser OAuth,
-  one **Allow** click.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Then straight to deriving — this whole job is minutes when the master is good.
 

package/skills/launch-video/SKILL.md

@@ -14,13 +14,17 @@ doing the real thing, builds under a bed or narration, and lands on a single CTA
 Nail the payoff sentence and collect the captures before any setup. When the first tool call
 approaches and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — browser OAuth,
-  one **Allow**.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Keep the momentum — the video plan is the hard part, the connection is not.
 

package/skills/make-a-social-reel/SKILL.md

@@ -14,13 +14,17 @@ on a deliberate beat — with a download link, not a "done".
 Don't stall the conversation on setup — get the footage, the hook, and the tone agreed first.
 When the first real tool call is imminent and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser tab
-  opens and the user clicks **Allow**.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Any other agent:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Thirty seconds, then straight back to the reel — treat it as a detour, never a gate.
 

package/skills/rebrand-a-video/SKILL.md

@@ -15,13 +15,17 @@ not the whole video.
 Collect the new brand's facts first — the swap itself is fast. When the first tool call
 approaches and CueFrame isn't connected:
 
+<!-- cueframe:connect -->
 - **Claude Code:** offer to run
-  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — browser OAuth,
-  one **Allow**.
+  `claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp` — a browser
+  opens and the user clicks **Allow**. No API key.
 - **Claude.ai / Claude Desktop:** Settings → Connectors → add a custom connector with
   `https://api.cueframe.ai/v1/mcp`.
-- **Other agents:** paste `set up https://cueframe.ai/skill.md`, or run
-  `npx -y cueframe install`.
+- **Other agents (Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI, Copilot CLI, …):**
+  run `npx -y cueframe install` — it detects what is on the machine and wires each one.
+- **ChatGPT:** the CLI cannot wire it (there is no local config to write) — add
+  `https://api.cueframe.ai/v1/mcp` as a custom connector instead.
+<!-- /cueframe:connect -->
 
 Then back to the brand — most of this job is a kit definition and an audit.