gooseworks 0.6.0-dev.77.f7d39aeb → 0.6.0-dev.78.6a887e57

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

@@ -1,163 +0,0 @@
-"use strict";
-// Server-backed entry snapshots for the CLI. Custom production guidance includes
-// the quality release below and the current in-chat approval backport.
-// Regenerate committed skills from these snapshots; do not edit their output.
-//
-// Source: gooseworks-app akhil/vq-wp7a2-custom-kit-handoff @ 036fa8393
-//   apps/api/src/services/playbooks/entry-skill.ts      buildVideoEntrySkill(slug)
-//   apps/api/src/app-mcp-server/lib/video-policy.ts     renderEntrySkillRules(product)
-//
-// Approval fragments: gooseworks-app PR #2047, captured 2026-10-14.
-// goose-video 4.5.0 (custom-first: a found or supplied reference ad by default) is copied whole from
-// gooseworks-app akhil/custom-first-default @ b229eec47 (PR athina-ai/gooseworks-app#2076), rules block included (rulebook 1.5.1).
-// make-custom-video 3.8.0 (custom-first: video_references find and pick when no reference is given; price check and
-// Standard/Best prices included) is copied whole from gooseworks-app akhil/custom-first-default @ 50472f801 (PR #2076).
-// Actor/voice selection and format guidance backported from the custom entry companion PR (2026-10-19).
-// Custom review wording keeps approvals in this chat.
-// The rules blocks (gooseworks, goose-ads, goose-product-photos) are rulebook 1.5.3 from gooseworks-app
-// dev @ f9d52a970 (renderEntrySkillRules), captured 2026-10-19: ads and photos start brand work with brain_map.
-// Other entries retain the earlier source above.
-// Video entries combine the recorded server snapshots above. The rules blocks are
-// the rulebook's entry-skill rules for the skills the CLI writes itself
-// (gooseworks, goose-ads, goose-product-photos), so no skill restates a rule
-// by hand. tests/skills/server-entry-skills.test.ts checks this file against
-// tests/fixtures/server-entry-skills.json, and that fixture against a
-// gooseworks-app checkout when GOOSEWORKS_APP_DIR points at one.
-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 of the unchanged shared rules snapshot. */
-exports.SERVER_RULEBOOK_VERSION = '1.5.3';
-exports.SERVER_VIDEO_ENTRY_SKILLS = {
-    'goose-video': `---
-name: goose-video
-description: "Make a video ad in this chat from a real reference ad, found or theirs; styles are the fallback. Follow every answer's next_step."
-version: 4.5.0
----
-
-# GooseWorks video
-
-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 video already started, call video_read and follow its next_step.
-
-New videos default to a real reference ad remade for the brand (custom); ready-made styles are the fallback. Start with get_started (wants video, request). A card is not a pick or proof of viewing.
-
-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. 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 kit, learnings and selected products with brand_read, then knowledge_search. Verify product size/use from facts and size-reference photos; resolve essential unknowns before planning. Note what to say and avoid.
-5. The reference. Their own video ad: video_create with style custom, request, products, its reference_url and a new UUID idempotency_key, then the custom rule. Otherwise, custom asked or not, video_references (action find) with the request and products ([] for none); it's free and reuses the brand's saved list unless they want new ideas (fresh: true). Show it as the answer says; they pick.
-6. The pick. video_references (action pick) with candidate_id, request, products and a new UUID idempotency_key starts the custom video. Then the custom rule.
-7. Styles, only if no found ad fits or they ask for a style or template: video_formats with the request and products; they pick. Card on screen: one line and wait; else print its table as it is. Then video_create with that style and the products.
-
-## A supplied video reference comes first
-
-Watch the whole video with sound before choosing a style or writing a custom plan, or use the server's measured reference profile. URLs, titles, thumbnails and frames are not viewing. Log the hook, scene order, pace, speech, framing, product interactions, text and ending with timestamps and gaps. Unreadable essentials need an accessible video or their brief-only choice; never claim a viewing.
-Styles vs a reference: fetch plausible templates and compare plan_note, scenes, duration, cast, sound and assets; titles and rankings prove no fit.
-Custom route (a picked or supplied reference, or explicit custom): catalog_fetch type skill make-custom-video on this connection before a project write and follow it: full harness, current schemas, two authenticated approvals, cumulative budgets, verified execution. Keep their mechanics and assets. If anything is unavailable, say so and keep the brief; never run a template's renderer as custom, import the reference as a finished video, use retired actions or switch environments. Fetching a skill proves no execution capability.
-
-## Rules
-
-- 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 here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- 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; never decide it for them, and pass on a yes only once they gave it to that total.
-- If you can run commands on the customer's computer, ask for the yes with the answer's own question: it says the video is then made on their computer, so that one yes covers starting it.
-- A yes is to the credit total the customer was shown: their press on the plan card, or their yes in chat sent with that total.
-- Every video approval, including a higher price or a priced fix, can happen in this chat. Show the plan and its price here when no card is visible; cards and websites are optional for approval.
-- 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.
-`,
-    'make-custom-video': `---
-name: make-custom-video
-description: "Create a custom video with sourced product accuracy, explicit sound routing and exact-final audiovisual review."
-version: 3.8.2
-requires_skills: [video-production-harness]
-harness_binding: gooseworks/video-actions/v1
----
-
-# Human version
-
-The owner approves the script, then the actual ingredients and budget, in this chat; cards and Studio are optional. Production keeps the reference's format, the product and the sound. GooseWorks measures and judges the final itself.
-
----
-
-# Agent version
-
-## Non-negotiables
-
-1. Watch every reference end to end with sound, or use the server's measured reference profile, and save the evidence before any script.
-2. Write the script with write-video-ad-script (catalog_fetch it; scripts without it are refused).
-3. Keep the reference's format: people stay people, demos stay demos, sound type stays. Otherwise list the change in changes_from_reference.
-4. The voice is the master clock. Never cut or retime sound apart from a talking face.
-5. Always real sound. No silent or tone tracks unless the owner asked for silence.
-6. Show the product correctly, at real size, from real photos.
-7. The review is listened or measured, never claimed.
-8. Under a deadline, deliver fewer correct videos. Never downgrade a format.
-
-Read one file per call; if output says truncated, re-read in parts. Fetch make-custom-video on this connection and read live schemas before writes. Keep this environment; no retired actions or reference-as-final import.
-
-## Load and resume
-
-Fetch the complete video-production-harness with catalog_fetch delivery archive; read SKILL.md and its phase references and keep version/contentHash/files. Mixed or incomplete packages block work. Resume recorded jobs with video_read; never resend a batch instead of polling.
-Custom skips the style picker. With a supplied reference, create once with style custom, its reference_url and a UUID idempotency_key reused on retries. Without one, run video_references find with the request and products and show the list; the owner's pick goes to video_references pick, which creates the project. Never use a template's demo as the reference. Keep requested mechanics, assets, products and campaign. Resume the same project, plan_revision, approvals and production_manifest.
-
-## Reference, product and creative contract
-
-Read brand_read and knowledge_search. Source product geometry, colour, label, allowed use and scale; size-sensitive shots need dimensions or a known-scale photo. Never guess capacity or invent a real process.
-Save reference_observation bound to media_id/media_revision with duration, full coverage, audio_perception (listened, or measured from the server's sound profile), motion_perception and timed picture/audio findings. Skipping a reference needs the owner's brief-only user_quote.
-Save draft.creative_contract: speech_mode, soundtrack_modes, required_features, reference_map per scene (beat/action/proof/sound), sourced product_grounding, voice_plan and changes_from_reference. Native speech keeps source audio; external speech over a speaking face needs exact-audio lip sync. No detected words never authorizes mute.
-Match capture/finish to the brief/reference; phone texture only for phone footage. Read harness references/talking-actor.md for speaking people: three actor options when needed, then playable voice choices beside the selected actor. Compare the generated voice with its audition.
-
-## Save and review twice
-
-video_change needs expected_revision and the current brand_context_digest; never author server context. Price paid requests free and read-only with data_price_provider (up to 20 per call; follow any price_unknown entry's next_step first). Save the shot_list with the script so the server prices Standard and Best, and put picture-upgrade money (about two pictures at high) in render_estimate.upgrade_allowance; it pays for no clip.
-Show the full saved script, then the actual playable ingredients and exact cumulative budget, here. At the script, show both approval_quote.tier_quotes totals as given, with no math of your own, and let the owner pick. Seedance is in neither total: offer each seedance_addons price, and only the owner's yes adds it. After the owner's explicit yes, call video_approve with the custom phase, review_token and total_credits from custom_review.approval_quote (with their quality_tier and its total when there are two), expected_revision and their words as user_quote. Never infer consent or approve yourself. Honor Stop.
-
-## Produce, assemble and deliver
-
-With fitting parts, save the kit block and follow video_make after ingredient approval; otherwise run on the customer's verified shell, never a cloud sandbox. Report progress per paid piece.
-Review the first take and the riskiest product action before batching. Send every clip to clip_check; the final may use only checked bytes. Save full prompts/settings and source-byte clip reviews as custom production.
-Build the source-linked assembly_timeline: native picture and audio ranges stay together, pauses and freezes are declared, real soundtrack cues. Edits invalidate affected evidence.
-Review the exact final at normal speed: listen, or rely on the server's final_measure and frame judge (measured). Save quality_report.content_review with final SHA-256, timeline and creative_contract revisions, reviewer, capabilities, full coverage and per-dimension findings. Serious defects block delivery.
-Direct builds also need the stored rebuild recipe (references/recipe-format.md). Complete with the confirmed same-project H.264/AAC MP4 URL and report complete again while server checks run. Kit uploads follow the saved review request. Pin only the checked version.
-
-Use plain words and returned credits. Never invent 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 decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow next_step for factual setup, claim/rights restrictions, spend approval, execution, polling and publishing. A fetched playbook owns research, creative planning and review gates; generic speed/planning suggestions do not waive them.
-- A card for an unresolved choice: show it and wait as directed. Already completed setup and a selected task continue in the active playbook; preserve its required gates.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; never decide it for them, and pass on a yes only once they gave it to that total.
-- 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 decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow next_step for factual setup, claim/rights restrictions, spend approval, execution, polling and publishing. A fetched playbook owns research, creative planning and review gates; generic speed/planning suggestions do not waive them.
-- A card for an unresolved choice: show it and wait as directed. Already completed setup and a selected task continue in the active playbook; preserve its required gates.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; never decide it for them, and pass on a yes only once they gave it to that total.
-- Read the brand and its listed knowledge actions for core rules and task evidence. Never guess unknown facts.
-- 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 decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- 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; never decide it for them, and pass on a yes only once they gave it to that total.
-- Start brand work with brain_map and its core. Open the chapters the job needs; search gaps. Never guess unknown facts.
-- 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.`,
-};
-//# sourceMappingURL=server-entry-skills.js.map

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

@@ -1 +0,0 @@
-{"version":3,"file":"server-entry-skills.js","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":";AAAA,iFAAiF;AACjF,uEAAuE;AACvE,8EAA8E;AAC9E,EAAE;AACF,uEAAuE;AACvE,mFAAmF;AACnF,uFAAuF;AACvF,EAAE;AACF,oEAAoE;AACpE,qGAAqG;AACrG,mIAAmI;AACnI,oHAAoH;AACpH,wHAAwH;AACxH,wGAAwG;AACxG,sDAAsD;AACtD,wGAAwG;AACxG,gHAAgH;AAChH,iDAAiD;AACjD,kFAAkF;AAClF,wEAAwE;AACxE,6EAA6E;AAC7E,6EAA6E;AAC7E,sEAAsE;AACtE,iEAAiE;;;AAEjE,mEAAmE;AACtD,QAAA,uBAAuB,GAAG,OAAO,CAAC;AAElC,QAAA,yBAAyB,GAAG;IACvC,aAAa,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0ChB;IACC,mBAAmB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuDtB;CACS,CAAC;AAIX,wFAAwF;AAC3E,QAAA,wBAAwB,GAAG;IACtC,GAAG,EAAE;;;;;;;;mJAQ4I;IACjJ,GAAG,EAAE;;;;;;;;;mJAS4I;IACjJ,MAAM,EAAE;;;;;;;;;mJASyI;CACzI,CAAC"}

package/skills/goose-ads/SKILL.md

@@ -1,41 +0,0 @@
----
-name: goose-ads
-slug: goose-ads
-description: Edit, resize, animate and study image ads with GooseWorks in this chat. New static or image ads go to the make-static-ads skill when it is installed or catalog_fetch opens it. Read the brand and follow the active playbook, preserving factual prerequisites and approvals.
-category: ads
-version: 3.2.1
-author: GooseWorks
----
-
-# GooseWorks ads
-
-Use this entry for existing-ad operations and analysis. For new image ads, more ads, a winner's
-variations, copy/font changes, a rejected ad fix or a requested social graphic, fetch
-make-static-ads with catalog_fetch (or use the installed current package) and follow its
-research, selection, claims and quote gates. If it cannot be fetched, report that creation
-is unavailable on this connection and stop. The server generator is a different workflow,
-not a fallback for the missing playbook.
-
-- Save lasting human brand facts with the connection's listed knowledge action in their words.
-- A batch on its way: job_get. Finished ads: ads_read.
-- One finished ad: a new size, an animation, its tags or the customer's rating, all with ads_edit.
-- The customer's own image as a template: ads_template_save. Their files: media_upload.
-- Campaign planning/launch requests use their matching marketing playbook. Static creation for
-  a campaign still uses make-static-ads; a campaign record is input, not a generation fallback.
-- How ads are doing: meta_read, or an analysis skill found with catalog_search, whose data comes
-  through data_get and data_post.
-
-For these existing-ad actions, follow the actual execution next_step.
-
-## Rules
-
-- Talk to marketers: what they get and decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow next_step for factual setup, claim/rights restrictions, spend approval, execution, polling and publishing. A fetched playbook owns research, creative planning and review gates; generic speed/planning suggestions do not waive them.
-- A card for an unresolved choice: show it and wait as directed. Already completed setup and a selected task continue in the active playbook; preserve its required gates.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; never decide it for them, and pass on a yes only once they gave it to that total.
-- Read the brand and its listed knowledge actions for core rules and task evidence. Never guess unknown facts.
-- 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

@@ -1,39 +0,0 @@
----
-name: goose-product-photos
-slug: goose-product-photos
-description: Make product photos (studio, lifestyle or on a model) of a brand's real products with GooseWorks in this chat. Start brand work with brain_map and follow the next_step in every answer.
-category: ads
-version: 1.1.0
-author: GooseWorks
----
-
-# GooseWorks product photos
-
-Use GooseWorks to photograph the customer's physical products, here in this chat. A software
-screen or an app is not a product photo.
-
-- A fact the customer states about the brand (a price, a rule, their audience): save it with
-  brain_save in their words, never in your own notes, and confirm in one line.
-- Offer the brand's real products from brand_read; never describe one you can't see. A product
-  that isn't listed yet: brand_update adds it from its page. A photo the customer sends:
-  media_upload.
-- photos_generate makes the photos: get its price first, tell the customer the credit total, and
-  make them only after their yes. Show a person only when the customer asks for one and confirms
-  they have the rights.
-- Follow the photos with photos_read until they are ready.
-- Keep or drop photos with media_update. Only kept photos join the brand kit and reach ads.
-
-Then follow the next_step in every answer.
-
-## Rules
-
-- Talk to marketers: what they get and decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- 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; never decide it for them, and pass on a yes only once they gave it to that total.
-- Start brand work with brain_map and its core. Open the chapters the job needs; search gaps. Never guess unknown facts.
-- 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,42 +0,0 @@
----
-name: goose-video
-description: "Make a video ad in this chat from a real reference ad, found or theirs; styles are the fallback. Follow every answer's next_step."
-version: 4.5.0
----
-
-# GooseWorks video
-
-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 video already started, call video_read and follow its next_step.
-
-New videos default to a real reference ad remade for the brand (custom); ready-made styles are the fallback. Start with get_started (wants video, request). A card is not a pick or proof of viewing.
-
-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. 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 kit, learnings and selected products with brand_read, then knowledge_search. Verify product size/use from facts and size-reference photos; resolve essential unknowns before planning. Note what to say and avoid.
-5. The reference. Their own video ad: video_create with style custom, request, products, its reference_url and a new UUID idempotency_key, then the custom rule. Otherwise, custom asked or not, video_references (action find) with the request and products ([] for none); it's free and reuses the brand's saved list unless they want new ideas (fresh: true). Show it as the answer says; they pick.
-6. The pick. video_references (action pick) with candidate_id, request, products and a new UUID idempotency_key starts the custom video. Then the custom rule.
-7. Styles, only if no found ad fits or they ask for a style or template: video_formats with the request and products; they pick. Card on screen: one line and wait; else print its table as it is. Then video_create with that style and the products.
-
-## A supplied video reference comes first
-
-Watch the whole video with sound before choosing a style or writing a custom plan, or use the server's measured reference profile. URLs, titles, thumbnails and frames are not viewing. Log the hook, scene order, pace, speech, framing, product interactions, text and ending with timestamps and gaps. Unreadable essentials need an accessible video or their brief-only choice; never claim a viewing.
-Styles vs a reference: fetch plausible templates and compare plan_note, scenes, duration, cast, sound and assets; titles and rankings prove no fit.
-Custom route (a picked or supplied reference, or explicit custom): catalog_fetch type skill make-custom-video on this connection before a project write and follow it: full harness, current schemas, two authenticated approvals, cumulative budgets, verified execution. Keep their mechanics and assets. If anything is unavailable, say so and keep the brief; never run a template's renderer as custom, import the reference as a finished video, use retired actions or switch environments. Fetching a skill proves no execution capability.
-
-## Rules
-
-- 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 here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- 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; never decide it for them, and pass on a yes only once they gave it to that total.
-- If you can run commands on the customer's computer, ask for the yes with the answer's own question: it says the video is then made on their computer, so that one yes covers starting it.
-- A yes is to the credit total the customer was shown: their press on the plan card, or their yes in chat sent with that total.
-- Every video approval, including a higher price or a priced fix, can happen in this chat. Show the plan and its price here when no card is visible; cards and websites are optional for approval.
-- 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-local/SKILL.md

@@ -1,7 +0,0 @@
----
-name: goose-video-local
-description: Make an approved GooseWorks video when an answer's next_step gives its command.
-version: 1.0.3
----
-
-When an answer's next_step gives a command to make a video, its last line says who starts it and how: follow that line exactly, with the command exactly as given.

package/skills/gooseworks/SKILL.md

@@ -1,104 +0,0 @@
----
-name: gooseworks
-slug: gooseworks
-description: >
-  GooseWorks growth coworker and router for markets, competitors, audiences, creators,
-  campaigns, ads, photos, graphics, video, content, email, SEO, social, leads and contacts.
-  Use for brand facts or copy too, so offers, prices, rules, audience and bestsellers
-  reach the brand's Marketing Brain.
-category: general
-version: 2.2.1
-author: GooseWorks
-tags: [gooseworks, data, scraping, search, research, gtm, leads, prospecting, ads, video]
----
-
-# GooseWorks
-
-Route specialist jobs to their skills; use GooseWorks for web and social data.
-
-## First steps
-
-1. Discover the listed setup/status action and read brand/task state. Complete missing facts;
-   preserve the selected brand/task and continue once setup is done.
-2. Read brand_read and advertised knowledge actions for rules/evidence; pass results to the
-   playbook. Use legacy action names only when listed; ask only what remains ambiguous.
-3. Save lasting human brand facts in their words through the listed typed knowledge action.
-   Keep guesses and temporary creative choices as proposals; follow claim, rights and approval
-   rules. Generic context is not approved product proof.
-
-## Skill routes
-
-| If the user wants… | Route to | How |
-| --- | --- | --- |
-| Raw social post lists, engagement rankings or voices lists | **`marketing-data-access`** | Fetch marketing-data-access and follow focused-reads.md. |
-| Learn a reusable brand or author voice from blog posts or social writing | **`voice-card`** | Fetch it with catalog_fetch, or `gooseworks fetch voice-card` in a terminal. |
-| Static/image ads, including campaigns, more ads, winner variants, copy/font changes or rejected-image fixes | **`make-static-ads`** | Fetch with catalog_fetch or gooseworks fetch; follow selection/review/quote gates. Stop creation if unavailable. |
-| Change one ad already made in GooseWorks (an edit, a new size, its tags or rating), or save the customer's image as a template. New image ads: `make-static-ads` | **`goose-ads`** | Open it with catalog_fetch in a chat app, or 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`** | 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`** | Open it with catalog_fetch in a chat app, or 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: find a skill or a single step | (stay here) | catalog_search, or `gooseworks search` in a terminal; see "Data work". |
-
-## Marketing playbooks
-
-| Job | Playbook |
-| --- | --- |
-| Not sure what to do first | `where-to-start` |
-| Market size, trends, brand watch and launch positioning | `research-market` |
-| Competitor research, battlecards, landing-page tools and post engagers | `research-competitors` |
-| Who buys and why; prospect lists, lead enrichment and work contacts | `research-audience` |
-| Cold email and LinkedIn drafts, replies and an import file; you send | `write-outreach` |
-| A campaign plan from a budget and a date | `plan-campaign` |
-| New static image ads | `make-static-ads` |
-| Launch, scale or pause paid ads | `run-paid-campaigns` |
-| What worked; performance reports | `analyze-performance` |
-| Subscriber email flows and broadcast drafts; you send | `email-lifecycle` |
-| SEO audits, metrics, keyword gaps, topic clusters, page-set plans and AI visibility | `improve-search-visibility` |
-| Influencers and UGC creators | `work-with-creators` |
-| Posts, articles, newsletters and one or more content briefs | `make-content` |
-| Organic social research, posts, voices, calendar and drafts | `run-organic-social` |
-
-Fetch playbook, dependencies and brand context. Static creation requires make-static-ads;
-fetch it or stop. Its research and selection run even for one ad or finals only.
-Raw lists: marketing-data-access; voice: voice-card. Supplied surveys use ordinary report
-writing. Skip unrelated calendar/campaign intake.
-
-## Data work
-
-In chat, catalog_search finds skills, catalog_fetch opens them, data_get/data_post run paid
-data calls and account_whoami shows credits.
-
-In a terminal:
-
-- `gooseworks search "<task>"` finds a skill; `gooseworks fetch <slug>` prints instructions and dependencies.
-- Save scripts/files under `/tmp/gooseworks-scripts/<slug>/` (files under `tools/` go to
-  `/tmp/gooseworks-scripts/tools/`), never in the user's project.
-- `gooseworks call <provider> <path>` calls a provider through GooseWorks; `--query` and `--body`
-  take JSON. Use it in place of any raw request a skill shows. A script that needs the GooseWorks
-  settings gets them from `gooseworks env`.
-- When no skill fits, `gooseworks orthogonal find "<task>"` finds an API,
-  `gooseworks orthogonal describe <api> <path>` shows its parameters and `gooseworks call` runs it.
-- `gooseworks credits` shows the balance. If a command says you are not signed in, run
-  `gooseworks login` and let the customer finish signing in. In a cloud sandbox or over SSH,
-  run `gooseworks login --device --no-wait`, show the customer its link and code, and run
-  `gooseworks login --device` once they approve.
-- No GooseWorks actions here but a signed-in CLI? `gooseworks tool --list` lists them;
-  `gooseworks tool <name> '<json>'` calls one.
-- Results go in `~/Gooseworks/` unless the customer names a place. Ask before saving, and never
-  overwrite a file.
-
-Before paid calls, state the call count and total credits; wait for the customer's yes.
-Each paid answer reports its charge.
-
-## Rules
-
-- Talk to marketers: what they get and decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries; do say findings and cost.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except a video's make command when a next_step gives it; its last line says who starts it, and where this app does, never show it to them (original videos follow their own). Never give any other command, sign-in step or setting, and never ask them a technical question.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow next_step for factual setup, claim/rights restrictions, spend approval, execution, polling and publishing. A fetched playbook owns research, creative planning and review gates; generic speed/planning suggestions do not waive them.
-- A card for an unresolved choice: show it and wait as directed. Already completed setup and a selected task continue in the active playbook; preserve its required gates.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; never decide it for them, and pass on a yes only once they gave it to that total.
-- 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,55 +0,0 @@
----
-name: make-custom-video
-description: "Create a custom video with sourced product accuracy, explicit sound routing and exact-final audiovisual review."
-version: 3.8.2
-requires_skills: [video-production-harness]
-harness_binding: gooseworks/video-actions/v1
----
-
-# Human version
-
-The owner approves the script, then the actual ingredients and budget, in this chat; cards and Studio are optional. Production keeps the reference's format, the product and the sound. GooseWorks measures and judges the final itself.
-
----
-
-# Agent version
-
-## Non-negotiables
-
-1. Watch every reference end to end with sound, or use the server's measured reference profile, and save the evidence before any script.
-2. Write the script with write-video-ad-script (catalog_fetch it; scripts without it are refused).
-3. Keep the reference's format: people stay people, demos stay demos, sound type stays. Otherwise list the change in changes_from_reference.
-4. The voice is the master clock. Never cut or retime sound apart from a talking face.
-5. Always real sound. No silent or tone tracks unless the owner asked for silence.
-6. Show the product correctly, at real size, from real photos.
-7. The review is listened or measured, never claimed.
-8. Under a deadline, deliver fewer correct videos. Never downgrade a format.
-
-Read one file per call; if output says truncated, re-read in parts. Fetch make-custom-video on this connection and read live schemas before writes. Keep this environment; no retired actions or reference-as-final import.
-
-## Load and resume
-
-Fetch the complete video-production-harness with catalog_fetch delivery archive; read SKILL.md and its phase references and keep version/contentHash/files. Mixed or incomplete packages block work. Resume recorded jobs with video_read; never resend a batch instead of polling.
-Custom skips the style picker. With a supplied reference, create once with style custom, its reference_url and a UUID idempotency_key reused on retries. Without one, run video_references find with the request and products and show the list; the owner's pick goes to video_references pick, which creates the project. Never use a template's demo as the reference. Keep requested mechanics, assets, products and campaign. Resume the same project, plan_revision, approvals and production_manifest.
-
-## Reference, product and creative contract
-
-Read brand_read and knowledge_search. Source product geometry, colour, label, allowed use and scale; size-sensitive shots need dimensions or a known-scale photo. Never guess capacity or invent a real process.
-Save reference_observation bound to media_id/media_revision with duration, full coverage, audio_perception (listened, or measured from the server's sound profile), motion_perception and timed picture/audio findings. Skipping a reference needs the owner's brief-only user_quote.
-Save draft.creative_contract: speech_mode, soundtrack_modes, required_features, reference_map per scene (beat/action/proof/sound), sourced product_grounding, voice_plan and changes_from_reference. Native speech keeps source audio; external speech over a speaking face needs exact-audio lip sync. No detected words never authorizes mute.
-Match capture/finish to the brief/reference; phone texture only for phone footage. Read harness references/talking-actor.md for speaking people: three actor options when needed, then playable voice choices beside the selected actor. Compare the generated voice with its audition.
-
-## Save and review twice
-
-video_change needs expected_revision and the current brand_context_digest; never author server context. Price paid requests free and read-only with data_price_provider (up to 20 per call; follow any price_unknown entry's next_step first). Save the shot_list with the script so the server prices Standard and Best, and put picture-upgrade money (about two pictures at high) in render_estimate.upgrade_allowance; it pays for no clip.
-Show the full saved script, then the actual playable ingredients and exact cumulative budget, here. At the script, show both approval_quote.tier_quotes totals as given, with no math of your own, and let the owner pick. Seedance is in neither total: offer each seedance_addons price, and only the owner's yes adds it. After the owner's explicit yes, call video_approve with the custom phase, review_token and total_credits from custom_review.approval_quote (with their quality_tier and its total when there are two), expected_revision and their words as user_quote. Never infer consent or approve yourself. Honor Stop.
-
-## Produce, assemble and deliver
-
-With fitting parts, save the kit block and follow video_make after ingredient approval; otherwise run on the customer's verified shell, never a cloud sandbox. Report progress per paid piece.
-Review the first take and the riskiest product action before batching. Send every clip to clip_check; the final may use only checked bytes. Save full prompts/settings and source-byte clip reviews as custom production.
-Build the source-linked assembly_timeline: native picture and audio ranges stay together, pauses and freezes are declared, real soundtrack cues. Edits invalidate affected evidence.
-Review the exact final at normal speed: listen, or rely on the server's final_measure and frame judge (measured). Save quality_report.content_review with final SHA-256, timeline and creative_contract revisions, reviewer, capabilities, full coverage and per-dimension findings. Serious defects block delivery.
-Direct builds also need the stored rebuild recipe (references/recipe-format.md). Complete with the confirmed same-project H.264/AAC MP4 URL and report complete again while server checks run. Kit uploads follow the saved review request. Pin only the checked version.
-
-Use plain words and returned credits. Never invent claims, approvals, assets or passing checks.

package/skills/manifest.json

@@ -1,12 +0,0 @@
-{
-  "package": "gooseworks",
-  "version": "0.6.0-dev.77.f7d39aeb",
-  "entries": {
-    "gooseworks": "91a5468e045198f944a4c8d4872237fbc2b83a56ea5b0ad6a42697a3b6325bce",
-    "goose-ads": "9264031a4acb43cbda268ceb1ba474a41cc38bd18d018c75dba64441a6122c2a",
-    "goose-video": "3419174c9e984e974b7486a088df480b44fcc2004ad4dcadc9c50bce36d7fdf2",
-    "goose-video-local": "3c8c8aecbfe3d8e58e6393e28dc67dc36f9d4b8dcfb1603f8bc442786ce839ee",
-    "make-custom-video": "e2acbb5b920ed7e6ca6a990871a3b8734ed760bdfd00f7e89d7488dcb3b4c839",
-    "goose-product-photos": "8ffbb7a9d61d6ab1a7c3710b0bf013c6abb479d1cc62cee38400ef39d4d116de"
-  }
-}