gooseworks 0.5.7 → 0.5.9-dev.53.c1bd6be2

package/dist/skills/server-entry-skills.js

@@ -2,7 +2,7 @@
 // The entry skill text our server builds, copied here because the CLI
 // cannot import gooseworks-app. Do not edit by hand.
 //
-// Source: gooseworks-app dev @ 810c496ee
+// Source: gooseworks-app akhil/goose-4027-custom-video-source-recipe (on dev @ 538cb6243)
 //   apps/api/src/services/playbooks/entry-skill.ts      buildVideoEntrySkill(slug)
 //   apps/api/src/app-mcp-server/lib/video-policy.ts     renderEntrySkillRules(product)
 //
@@ -15,35 +15,45 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SERVER_ENTRY_SKILL_RULES = exports.SERVER_VIDEO_ENTRY_SKILLS = exports.SERVER_RULEBOOK_VERSION = void 0;
 /** The rulebook version this text was built from. */
-exports.SERVER_RULEBOOK_VERSION = '1.0.2';
+exports.SERVER_RULEBOOK_VERSION = '1.3.1';
 exports.SERVER_VIDEO_ENTRY_SKILLS = {
     'goose-video': `---
 name: goose-video
-description: "Make a video ad with GooseWorks in this chat: the product first, then the brand read, then video_formats; follow the next_step in every answer."
-version: 4.1.0
+description: "Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer."
+version: 4.4.3
 ---
 
 # GooseWorks video
 
-Use GooseWorks to make the customer's video, here in this chat. For a video already started (named, or sent by a card), call video_read and follow its next_step.
+From an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.
 
-For a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.
+For a video already started, call video_read and follow its next_step.
+
+Explicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.
+
+For other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.
 
 1. The request. If they haven't said what the video is about, ask in one short question.
 2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Unless they named one or want none, ask which product, offering the brand's products by name from brand_read (sections: products). Use the only one if there is one; with none, go on without.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids): photos, specs, creative notes. Then knowledge_search for them. Keep a few plain lines of what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids: [] for none or a style without products. The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, list the fitting styles, each with its name, one line and price as written, and ask which one.
-6. The plan. Call video_create with the picked style and the products; its next_step says how to write the scenes with video_change and what follows.
+3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.
+4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.
+5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.
+6. The plan. Call video_create with the picked style and the products; its next_step says what follows.
+
+## A supplied video reference comes first
+
+Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
+When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
+If no available style fits, or they explicitly want custom, catalog_fetch type skill make-custom-video on this connection before a project write. Require its complete production-harness dependency and current custom schemas. Follow its separate authenticated script and ingredient approvals, cumulative budgets and verified execution capability. If anything is unavailable, say so and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. Fetching a skill alone proves no execution capability.
 
 ## Rules
 
-- Talk to marketers: what they get and what they decide, never how it is made.
+- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
 - A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
 - Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.
@@ -52,67 +62,86 @@ For a new video, in this order. Suggest nothing before step 5 and write no plan
 `,
     'make-custom-video': `---
 name: make-custom-video
-description: "Make an original video from a brief or a reference video with GooseWorks in this chat: the product first, then the brand read, then video_formats; follow the next_step in every answer."
-version: 3.1.0
+description: "Make a custom video from its brief and studied reference, with authenticated script and ingredient reviews."
+version: 3.5.0
+requires_skills: [video-production-harness]
+harness_binding: gooseworks/video-actions/v1
 ---
 
-# GooseWorks video
+# Human version
 
-Use GooseWorks to make the customer's video, here in this chat. For a video already started (named, or sent by a card), call video_read and follow its next_step.
+The owner approves the script, then actual storyboard/ingredients and budget. Both authenticated reviews must pass before production.
 
-For a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.
+---
 
-1. The request. If they haven't said what the video is about, ask in one short question.
-2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Unless they named one or want none, ask which product, offering the brand's products by name from brand_read (sections: products). Use the only one if there is one; with none, go on without.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids): photos, specs, creative notes. Then knowledge_search for them. Keep a few plain lines of what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids: [] for none or a style without products. The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, list the fitting styles, each with its name, one line and price as written, and ask which one.
-6. The plan. Call video_create with the picked style and the products; its next_step says how to write the scenes with video_change and what follows.
+# Agent version
 
-## Rules
+Installed entry: catalog_fetch type skill make-custom-video here once. Check live custom schemas before writes. Keep this environment; no retired actions, template fallback or reference-as-final import.
 
-- Talk to marketers: what they get and what they decide, never how it is made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
-- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.
-- Never invent an offer, a claim or proof.
-- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.
+## Load the production harness
+
+Require complete video-production-harness content/scripts/files/version/contentHash. Read its orchestrator, phases and editorial/specialist guides. Save safe paths separately with hashes/dependencies. Incomplete/mixed packages block work. Resume recorded packages, inputs and jobs.
+
+## Keep the brief and study the reference
+
+Explicit custom skips video_formats and the picker. Keep requested mechanics/assets; animated text and product photos must not become a creator montage. Implicit references use goose-video to watch and compare template constraints; custom follows no match or their choice.
+Read brand_read (kit, products, rules), then knowledge_search. Use supported claims, real photos/logo. Watch playback, or timed frames spanning the video plus audio/transcript. Record hook, scene order, pace, framing, dialogue, text, product interactions and ending with times/gaps. URLs/thumbnails are not viewing. Missing access needs an accessible source or explicit brief-only choice.
+
+## Create or resume
+
+New: video_create with brand_id, style custom, request and a required agent-generated UUID idempotency_key; retain products, name, reference_url and campaign. Reuse that key on retries. Resume with video_read the same project: retain plan_revision, custom_review, brand_context, production_manifest and execution; never create a replacement.
+Reference resolve accepts direct files; social links cause no automatic paid lookup. If GooseWorks can't download it, upload the file you watched into this project (media_upload scope video_project, media_confirm), wait for media_analyze read to show its duration, then video_change custom reference attach with asset_id and its current_revision as analysis_revision; each refusal names the condition to fix. Skip needs explicit brief-only user_quote. Pending/failed reference blocks approval; a URL is not viewing.
+A resolved reference also needs draft.reference_observation: the project's reference source_url, real duration_s, evidence_mode playback or frames_and_audio, observed_through_s covering 95%, and summary: what happens with times and gaps, as text or a list of {t, what}. Its data binds the script token. Resolve/attach is not watching.
+
+## Save script and ingredients
+
+Follow the harness phases. Discover specialists for the actual scenes; check inputs, outputs, dependencies and managed execution. Reuse suitable product photos and deterministic text animation. Never substitute a template driver. Bind operations to this project and approved scene/script revisions.
+video_change needs expected_revision (plan_revision), custom draft and optional script. Bind brand_context_digest to the returned bundle; never author server context. Keep packages outside the review payload. Quote paid operations through the live managed estimate path with real inputs/project. Save preview_estimate/render_estimate for the work still to buy; the server adds committed_credits. Never edit a field the owner approved: the save sets their approval aside until the approved text is back. Missing price/unsupported inputs blocks production; no guessed rates/direct keys.
+
+## Two authenticated owner reviews
+
+Show the complete saved script and exact cumulative budget on the authenticated review card. Only the owner's actual signed button press approves. Chat yes, OAuth, user_quote, widget origin or a copied token is not proof; never manufacture a click or self-approve. Text-only/large reviews use returned authenticated Studio phase buttons and approval_surface URL.
+Reread video_read after owner actions. Script approval permits quoted previews only. Save the actual storyboard, playable ingredients and render budget; ingredient approval permits clips. Require current script_approved/ingredients_approved, matching tokens/revision and budget. Changed reviews need renewed approval. A prior yes does not authorize changed work.
+
+## Execute, check and deliver
+
+Require execution.local from a verified customer shell. No cloud, style-only kit, API host, worker or coworker sandbox. Otherwise report the gap.
+video_make needs expected_revision and custom render state. Resume the same render with approved tokens; report running/failed/complete honestly and honor Stop. Save actual prompts, settings, every scene and clip checks through video_change custom production. Watch the full output against the approved script, product and brand; save its full quality report. Completion needs a confirmed upload and rebuild recipe here; pin only the checked complete render. Read back manifest/final before delivery. Repairs need affected assets only and renewed approvals/budget.
+
+Rebuild recipe: every input the build reads, uploaded here or a linked Library original, plus recipe/source.json; prove a clean-folder rebuild, then save it as custom production source. The next step gives the format.
+
+Use plain words and returned credits. No invented claims, approvals, assets or passing checks.
 `,
 };
 /** renderEntrySkillRules(product) for the products the CLI's own entry skills cover. */
 exports.SERVER_ENTRY_SKILL_RULES = {
-    all: `- Talk to marketers: what they get and what they decide, never how it is made.
+    all: `- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.`,
-    ads: `- Talk to marketers: what they get and what they decide, never how it is made.
+    ads: `- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.
+- Before choosing an angle, claim, product or source, or asking a brand fact, brand_read then knowledge_search for the task.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.`,
-    photos: `- Talk to marketers: what they get and what they decide, never how it is made.
+    photos: `- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.
+- Before choosing an angle, claim, product or source, or asking a brand fact, brand_read then knowledge_search for the task.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.`,
 };

package/dist/skills/server-entry-skills.js.map

@@ -1 +1 @@
-{"version":3,"file":"server-entry-skills.js","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,qDAAqD;AACrD,EAAE;AACF,yCAAyC;AACzC,mFAAmF;AACnF,uFAAuF;AACvF,EAAE;AACF,+EAA+E;AAC/E,wEAAwE;AACxE,6EAA6E;AAC7E,6EAA6E;AAC7E,sEAAsE;AACtE,iEAAiE;;;AAEjE,qDAAqD;AACxC,QAAA,uBAAuB,GAAG,OAAO,CAAC;AAElC,QAAA,yBAAyB,GAAG;IACvC,aAAa,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgChB;IACC,mBAAmB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgCtB;CACS,CAAC;AAIX,wFAAwF;AAC3E,QAAA,wBAAwB,GAAG;IACtC,GAAG,EAAE;;;;;;;;mJAQ4I;IACjJ,GAAG,EAAE;;;;;;;;;mJAS4I;IACjJ,MAAM,EAAE;;;;;;;;;mJASyI;CACzI,CAAC"}
+{"version":3,"file":"server-entry-skills.js","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,qDAAqD;AACrD,EAAE;AACF,0FAA0F;AAC1F,mFAAmF;AACnF,uFAAuF;AACvF,EAAE;AACF,+EAA+E;AAC/E,wEAAwE;AACxE,6EAA6E;AAC7E,6EAA6E;AAC7E,sEAAsE;AACtE,iEAAiE;;;AAEjE,qDAAqD;AACxC,QAAA,uBAAuB,GAAG,OAAO,CAAC;AAElC,QAAA,yBAAyB,GAAG;IACvC,aAAa,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0ChB;IACC,mBAAmB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmDtB;CACS,CAAC;AAIX,wFAAwF;AAC3E,QAAA,wBAAwB,GAAG;IACtC,GAAG,EAAE;;;;;;;;mJAQ4I;IACjJ,GAAG,EAAE;;;;;;;;;mJAS4I;IACjJ,MAAM,EAAE;;;;;;;;;mJASyI;CACzI,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gooseworks",
-  "version": "0.5.7",
+  "version": "0.5.9-dev.53.c1bd6be2",
   "description": "GooseWorks CLI — give your coding agent real data tools",
   "bin": {
     "gooseworks": "./dist/index.js"
@@ -61,7 +61,7 @@
   "homepage": "https://gooseworks.ai",
   "author": "GooseWorks <help@gooseworks.ai>",
   "gooseworksRelease": {
-    "commit": "dc225cc93a199a8d410dafd47850a8dd5fb3d4bd",
-    "branch": "main"
+    "commit": "c1bd6be2d08e7aa8ae5573b16f8aed96e1b86fc5",
+    "branch": "dev"
   }
 }

package/skills/goose-ads/SKILL.md

@@ -28,13 +28,13 @@ Then follow the next_step in every answer.
 
 ## Rules
 
-- Talk to marketers: what they get and what they decide, never how it is made.
+- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.
+- Before choosing an angle, claim, product or source, or asking a brand fact, brand_read then knowledge_search for the task.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.

package/skills/goose-product-photos/SKILL.md

@@ -25,13 +25,13 @@ Then follow the next_step in every answer.
 
 ## Rules
 
-- Talk to marketers: what they get and what they decide, never how it is made.
+- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.
+- Before choosing an angle, claim, product or source, or asking a brand fact, brand_read then knowledge_search for the task.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.

package/skills/goose-video/SKILL.md

@@ -1,30 +1,40 @@
 ---
 name: goose-video
-description: "Make a video ad with GooseWorks in this chat: the product first, then the brand read, then video_formats; follow the next_step in every answer."
-version: 4.1.0
+description: "Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer."
+version: 4.4.3
 ---
 
 # GooseWorks video
 
-Use GooseWorks to make the customer's video, here in this chat. For a video already started (named, or sent by a card), call video_read and follow its next_step.
+From an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.
 
-For a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.
+For a video already started, call video_read and follow its next_step.
+
+Explicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.
+
+For other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.
 
 1. The request. If they haven't said what the video is about, ask in one short question.
 2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Unless they named one or want none, ask which product, offering the brand's products by name from brand_read (sections: products). Use the only one if there is one; with none, go on without.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids): photos, specs, creative notes. Then knowledge_search for them. Keep a few plain lines of what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids: [] for none or a style without products. The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, list the fitting styles, each with its name, one line and price as written, and ask which one.
-6. The plan. Call video_create with the picked style and the products; its next_step says how to write the scenes with video_change and what follows.
+3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.
+4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.
+5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.
+6. The plan. Call video_create with the picked style and the products; its next_step says what follows.
+
+## A supplied video reference comes first
+
+Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
+When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
+If no available style fits, or they explicitly want custom, catalog_fetch type skill make-custom-video on this connection before a project write. Require its complete production-harness dependency and current custom schemas. Follow its separate authenticated script and ingredient approvals, cumulative budgets and verified execution capability. If anything is unavailable, say so and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. Fetching a skill alone proves no execution capability.
 
 ## Rules
 
-- Talk to marketers: what they get and what they decide, never how it is made.
+- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
 - A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
 - Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.

package/skills/goose-video-local/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: goose-video-local
 description: Make an approved GooseWorks video on this computer when the server's next_step says to.
-version: 1.0.0
+version: 1.0.2
 ---
 
 Run `gooseworks video make <id>` when the server's next_step says so.

package/skills/gooseworks/SKILL.md

@@ -33,7 +33,7 @@ social data. Hand specialist work to its skill; do data work here.
 | --- | --- | --- |
 | Make, edit or study image ads: from a template, a source ad or the brand's products; why a campaign underperforms; competitor ads, angles and hooks | **`goose-ads`** | Use goose-ads: open it with catalog_fetch in a chat app, or use the installed copy in a terminal. |
 | Charts, infographics, slides, social graphics, branded visual designs from a style or format | **`goose-graphics`** | Fetch it with catalog_fetch, or `gooseworks fetch goose-graphics` in a terminal. |
-| Any **video**: a video ad from a style, an original video from a brief or a reference video, or a video already started | **`goose-video`** | Use goose-video: ask which product first, read the brand, then video_formats; follow the next_step in every answer. |
+| Any **video**: a video ad from a style, an original video from a brief or a reference video, or a video already started | **`goose-video`** | Use goose-video: explicit custom skips the picker; otherwise watch the reference, read the brand and compare style constraints. |
 | Make **product photos**: studio, lifestyle, marketplace, social or on a model | **`goose-product-photos`** | Use goose-product-photos: open it with catalog_fetch in a chat app, or use the installed copy in a terminal. |
 | Animate an approved static ad or product image | **`animate-image`** | Fetch it with catalog_fetch, or `gooseworks fetch animate-image` in a terminal. |
 | Anything else: scraping, research, lead lists, enrichment, any data lookup | (stay here) | Follow "Data work" below. |
@@ -91,12 +91,12 @@ for their yes. Each paid answer says what it charged.
 
 ## Rules
 
-- Talk to marketers: what they get and what they decide, never how it is made.
+- Talk to marketers: what they get and decide, never how it's made.
 - Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
+- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
+- Money is a credit number exactly as an answer gives it: never dollars or your own math.
+- Follow the next_step in every answer.
+- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
 - Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
 - Never invent an offer, a claim or proof.
 - GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.

package/skills/make-custom-video/SKILL.md

@@ -1,32 +1,51 @@
 ---
 name: make-custom-video
-description: "Make an original video from a brief or a reference video with GooseWorks in this chat: the product first, then the brand read, then video_formats; follow the next_step in every answer."
-version: 3.1.0
+description: "Make a custom video from its brief and studied reference, with authenticated script and ingredient reviews."
+version: 3.5.0
+requires_skills: [video-production-harness]
+harness_binding: gooseworks/video-actions/v1
 ---
 
-# GooseWorks video
+# Human version
 
-Use GooseWorks to make the customer's video, here in this chat. For a video already started (named, or sent by a card), call video_read and follow its next_step.
+The owner approves the script, then actual storyboard/ingredients and budget. Both authenticated reviews must pass before production.
 
-For a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.
+---
+
+# Agent version
+
+Installed entry: catalog_fetch type skill make-custom-video here once. Check live custom schemas before writes. Keep this environment; no retired actions, template fallback or reference-as-final import.
+
+## Load the production harness
+
+Require complete video-production-harness content/scripts/files/version/contentHash. Read its orchestrator, phases and editorial/specialist guides. Save safe paths separately with hashes/dependencies. Incomplete/mixed packages block work. Resume recorded packages, inputs and jobs.
+
+## Keep the brief and study the reference
+
+Explicit custom skips video_formats and the picker. Keep requested mechanics/assets; animated text and product photos must not become a creator montage. Implicit references use goose-video to watch and compare template constraints; custom follows no match or their choice.
+Read brand_read (kit, products, rules), then knowledge_search. Use supported claims, real photos/logo. Watch playback, or timed frames spanning the video plus audio/transcript. Record hook, scene order, pace, framing, dialogue, text, product interactions and ending with times/gaps. URLs/thumbnails are not viewing. Missing access needs an accessible source or explicit brief-only choice.
+
+## Create or resume
+
+New: video_create with brand_id, style custom, request and a required agent-generated UUID idempotency_key; retain products, name, reference_url and campaign. Reuse that key on retries. Resume with video_read the same project: retain plan_revision, custom_review, brand_context, production_manifest and execution; never create a replacement.
+Reference resolve accepts direct files; social links cause no automatic paid lookup. If GooseWorks can't download it, upload the file you watched into this project (media_upload scope video_project, media_confirm), wait for media_analyze read to show its duration, then video_change custom reference attach with asset_id and its current_revision as analysis_revision; each refusal names the condition to fix. Skip needs explicit brief-only user_quote. Pending/failed reference blocks approval; a URL is not viewing.
+A resolved reference also needs draft.reference_observation: the project's reference source_url, real duration_s, evidence_mode playback or frames_and_audio, observed_through_s covering 95%, and summary: what happens with times and gaps, as text or a list of {t, what}. Its data binds the script token. Resolve/attach is not watching.
+
+## Save script and ingredients
+
+Follow the harness phases. Discover specialists for the actual scenes; check inputs, outputs, dependencies and managed execution. Reuse suitable product photos and deterministic text animation. Never substitute a template driver. Bind operations to this project and approved scene/script revisions.
+video_change needs expected_revision (plan_revision), custom draft and optional script. Bind brand_context_digest to the returned bundle; never author server context. Keep packages outside the review payload. Quote paid operations through the live managed estimate path with real inputs/project. Save preview_estimate/render_estimate for the work still to buy; the server adds committed_credits. Never edit a field the owner approved: the save sets their approval aside until the approved text is back. Missing price/unsupported inputs blocks production; no guessed rates/direct keys.
+
+## Two authenticated owner reviews
+
+Show the complete saved script and exact cumulative budget on the authenticated review card. Only the owner's actual signed button press approves. Chat yes, OAuth, user_quote, widget origin or a copied token is not proof; never manufacture a click or self-approve. Text-only/large reviews use returned authenticated Studio phase buttons and approval_surface URL.
+Reread video_read after owner actions. Script approval permits quoted previews only. Save the actual storyboard, playable ingredients and render budget; ingredient approval permits clips. Require current script_approved/ingredients_approved, matching tokens/revision and budget. Changed reviews need renewed approval. A prior yes does not authorize changed work.
+
+## Execute, check and deliver
 
-1. The request. If they haven't said what the video is about, ask in one short question.
-2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Unless they named one or want none, ask which product, offering the brand's products by name from brand_read (sections: products). Use the only one if there is one; with none, go on without.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids): photos, specs, creative notes. Then knowledge_search for them. Keep a few plain lines of what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids: [] for none or a style without products. The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, list the fitting styles, each with its name, one line and price as written, and ask which one.
-6. The plan. Call video_create with the picked style and the products; its next_step says how to write the scenes with video_change and what follows.
+Require execution.local from a verified customer shell. No cloud, style-only kit, API host, worker or coworker sandbox. Otherwise report the gap.
+video_make needs expected_revision and custom render state. Resume the same render with approved tokens; report running/failed/complete honestly and honor Stop. Save actual prompts, settings, every scene and clip checks through video_change custom production. Watch the full output against the approved script, product and brand; save its full quality report. Completion needs a confirmed upload and rebuild recipe here; pin only the checked complete render. Read back manifest/final before delivery. Repairs need affected assets only and renewed approvals/budget.
 
-## Rules
+Rebuild recipe: every input the build reads, uploaded here or a linked Library original, plus recipe/source.json; prove a clean-folder rebuild, then save it as custom production source. The next step gives the format.
 
-- Talk to marketers: what they get and what they decide, never how it is made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens in this chat: never ask the customer to install anything or use a CLI, slash command or other app; the only commands are gooseworks video check and gooseworks video make <id>, when a next_step gives them.
-- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.
-- Follow the next_step in every answer; it says what to do now.
-- With a card on screen (display_hint "widget"), add at most one short line; never re-list it or its links.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
-- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.
-- Never invent an offer, a claim or proof.
-- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.
+Use plain words and returned credits. No invented claims, approvals, assets or passing checks.

package/skills/manifest.json

@@ -1,12 +1,12 @@
 {
   "package": "gooseworks",
-  "version": "0.5.7",
+  "version": "0.5.9-dev.53.c1bd6be2",
   "entries": {
-    "gooseworks": "6a54a8962a390d34639d56226d9078b63a9005b0a8f5c65d7811f2ef5808cec4",
-    "goose-ads": "de1b0342fcc82942e1f9c6a3aa01818973c968cbdb65f7109d73761536d029f8",
-    "goose-video": "9226f2a3373ac4c8f94fdaaede34a30cac7951a160996d56971617097b2b2029",
-    "goose-video-local": "189cd2c24bbbb152d700847832b67ce651962959fd2381e878ed7ace6bc96a54",
-    "make-custom-video": "08f8fd3ef2713064a7f41d5b18ef0407f746a095bcea4334754013c391a030db",
-    "goose-product-photos": "b72df2f34b846f7d559067eec872d6aa6a350166ec61cf919c2278f7556c1832"
+    "gooseworks": "b648ab0e21d94405f2161db5d142770115a6b4551fef778a6aa51e2d30c005bb",
+    "goose-ads": "0fd22d77148ce37500f9dfc3977abc1204baabe5faf8cf30d46c32bf60a410fa",
+    "goose-video": "83f1fe3822c899848a808e99b81f718527e12ef7c4552542ebbf5f0b6862a13d",
+    "goose-video-local": "37871252ff2f754d018f22e4335957e6a9e9b829560f8fe19a75b9aa1e510c91",
+    "make-custom-video": "f55b5f870c0cdcc0804304342f10c9ea29fa447471b78af8e17589ed380be19f",
+    "goose-product-photos": "f2f9bcd9f5982b1e53d8aef384b8ee3f4e7dcba15985f40c6075ac3e29f413ce"
   }
 }

package/skills/routes.json

@@ -17,7 +17,7 @@
     {
       "skill": "goose-video",
       "when": "Any **video**: a video ad from a style, an original video from a brief or a reference video, or a video already started",
-      "how": "Use goose-video: ask which product first, read the brand, then video_formats; follow the next_step in every answer.",
+      "how": "Use goose-video: explicit custom skips the picker; otherwise watch the reference, read the brand and compare style constraints.",
       "delivery": "entry"
     },
     {