gooseworks 0.5.0 → 0.5.1-dev.21.22f4cf8f

package/dist/skills/server-entry-skills.d.ts

@@ -1,14 +1,14 @@
 /** The rulebook version this text was built from. */
-export declare const SERVER_RULEBOOK_VERSION = "0.6.0";
+export declare const SERVER_RULEBOOK_VERSION = "1.0.2";
 export declare const SERVER_VIDEO_ENTRY_SKILLS: {
-    readonly 'goose-video': "---\nname: goose-video\ndescription: \"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.\"\nversion: 4.1.0\n---\n\n# GooseWorks video\n\nUse 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.\n\nFor a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. 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.\n4. 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.\n5. 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.\n6. The plan. Call video_create with the picked style and the products, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.\n\n## Rules\n\n- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- Paid work needs the customer's yes to the credit total first. For video only their click on the plan card counts; you never approve.\n- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.\n- Where the app can't show the card, give the customer the plan link; they press the button there.\n- Never invent an offer, a claim or proof.\n- 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.\n";
-    readonly 'make-custom-video': "---\nname: make-custom-video\ndescription: \"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.\"\nversion: 3.1.0\n---\n\n# GooseWorks video\n\nUse 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.\n\nFor a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. 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.\n4. 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.\n5. 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.\n6. The plan. Call video_create with the picked style and the products, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.\n\n## Rules\n\n- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- Paid work needs the customer's yes to the credit total first. For video only their click on the plan card counts; you never approve.\n- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.\n- Where the app can't show the card, give the customer the plan link; they press the button there.\n- Never invent an offer, a claim or proof.\n- 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.\n";
+    readonly 'goose-video': "---\nname: goose-video\ndescription: \"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.\"\nversion: 4.1.0\n---\n\n# GooseWorks video\n\nUse 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.\n\nFor a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. 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.\n4. 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.\n5. 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.\n6. 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.\n\n## Rules\n\n- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- 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.\n- 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.\n- 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.\n- Never invent an offer, a claim or proof.\n- 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.\n";
+    readonly 'make-custom-video': "---\nname: make-custom-video\ndescription: \"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.\"\nversion: 3.1.0\n---\n\n# GooseWorks video\n\nUse 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.\n\nFor a new video, in this order. Suggest nothing before step 5 and write no plan before they pick a style.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. 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.\n4. 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.\n5. 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.\n6. 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.\n\n## Rules\n\n- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- 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.\n- 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.\n- 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.\n- Never invent an offer, a claim or proof.\n- 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.\n";
 };
 export type ServerVideoEntrySlug = keyof typeof SERVER_VIDEO_ENTRY_SKILLS;
 /** renderEntrySkillRules(product) for the products the CLI's own entry skills cover. */
 export declare const SERVER_ENTRY_SKILL_RULES: {
-    readonly all: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- Paid work needs the customer's yes to the credit total first. For video only their click on the plan card counts; you never approve.\n- Never invent an offer, a claim or proof.\n- 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.";
-    readonly ads: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- Paid work needs the customer's yes to the credit total first. For video only their click on the plan card counts; you never approve.\n- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.\n- Never invent an offer, a claim or proof.\n- 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.";
-    readonly photos: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- Paid work needs the customer's yes to the credit total first. For video only their click on the plan card counts; you never approve.\n- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.\n- Never invent an offer, a claim or proof.\n- 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.";
+    readonly all: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- 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.\n- Never invent an offer, a claim or proof.\n- 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.";
+    readonly ads: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- 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.\n- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.\n- Never invent an offer, a claim or proof.\n- 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.";
+    readonly photos: "- Talk to marketers: what they get and what they decide, never how it is made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- 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.\n- Money is a credit number, exactly as an answer gives it: never dollars, never your own math.\n- Follow the next_step in every answer; it says what to do now.\n- With a card on screen (display_hint \"widget\"), add at most one short line; never re-list it or its links.\n- 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.\n- Before choosing an angle, claim, product or source, or asking a brand fact: brand_read, then knowledge_search for the task.\n- Never invent an offer, a claim or proof.\n- 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.d.ts.map

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 video/b2-product-first @ aab7d9abb
+// Source: gooseworks-app dev @ 810c496ee
 //   apps/api/src/services/playbooks/entry-skill.ts      buildVideoEntrySkill(slug)
 //   apps/api/src/app-mcp-server/lib/video-policy.ts     renderEntrySkillRules(product)
 //
@@ -15,7 +15,7 @@
 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 = '0.6.0';
+exports.SERVER_RULEBOOK_VERSION = '1.0.2';
 exports.SERVER_VIDEO_ENTRY_SKILLS = {
     'goose-video': `---
 name: goose-video
@@ -32,9 +32,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.
+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, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.
+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.
 
 ## Rules
 
@@ -44,9 +44,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no plan
 - 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. For video only their click on the plan card counts; you never approve.
-- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.
-- Where the app can't show the card, give the customer the plan link; they press the button there.
+- 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.
 `,
@@ -65,9 +65,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.
+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, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.
+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.
 
 ## Rules
 
@@ -77,9 +77,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no plan
 - 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. For video only their click on the plan card counts; you never approve.
-- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.
-- Where the app can't show the card, give the customer the plan link; they press the button there.
+- 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.
 `,
@@ -92,7 +92,7 @@ exports.SERVER_ENTRY_SKILL_RULES = {
 - 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. For video only their click on the plan card counts; you never approve.
+- 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.
@@ -101,7 +101,7 @@ exports.SERVER_ENTRY_SKILL_RULES = {
 - 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. For video only their click on the plan card counts; you never approve.
+- 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.
 - 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.`,
@@ -111,7 +111,7 @@ exports.SERVER_ENTRY_SKILL_RULES = {
 - 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. For video only their click on the plan card counts; you never approve.
+- 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.
 - 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,4DAA4D;AAC5D,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,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"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gooseworks",
-  "version": "0.5.0",
+  "version": "0.5.1-dev.21.22f4cf8f",
   "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": "6bef43494ccc18d234588940551c281d9b3f1b8f",
-    "branch": "main"
+    "commit": "22f4cf8fe2eb8194fa72d5519a67cee9379579b5",
+    "branch": "dev"
   }
 }

package/skills/goose-ads/SKILL.md

@@ -34,7 +34,7 @@ Then follow the next_step in every answer.
 - 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. For video only their click on the plan card counts; you never approve.
+- 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.
 - 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

@@ -31,7 +31,7 @@ Then follow the next_step in every answer.
 - 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. For video only their click on the plan card counts; you never approve.
+- 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.
 - 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

@@ -13,9 +13,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.
+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, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.
+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.
 
 ## Rules
 
@@ -25,8 +25,8 @@ For a new video, in this order. Suggest nothing before step 5 and write no plan
 - 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. For video only their click on the plan card counts; you never approve.
-- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.
-- Where the app can't show the card, give the customer the plan link; they press the button there.
+- 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.

package/skills/gooseworks/SKILL.md

@@ -97,6 +97,6 @@ for their yes. Each paid answer says what it charged.
 - 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. For video only their click on the plan card counts; you never approve.
+- 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

@@ -13,9 +13,9 @@ For a new video, in this order. Suggest nothing before step 5 and write no 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. Search the brand's knowledge for them with knowledge_search. Keep a few plain lines of what to say and avoid.
+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, then follow the next_step in every answer: it says how to write the scenes with video_change and what follows.
+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.
 
 ## Rules
 
@@ -25,8 +25,8 @@ For a new video, in this order. Suggest nothing before step 5 and write no plan
 - 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. For video only their click on the plan card counts; you never approve.
-- Only the customer's click on the plan card approves a video; a yes typed in chat is not an approval.
-- Where the app can't show the card, give the customer the plan link; they press the button there.
+- 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.

package/skills/manifest.json

@@ -1,12 +1,12 @@
 {
   "package": "gooseworks",
-  "version": "0.5.0",
+  "version": "0.5.1-dev.21.22f4cf8f",
   "entries": {
-    "gooseworks": "78ee2e965290323ee8be3ccfd4c55d2d0165f2376224db3bdb21f173d580c3f5",
-    "goose-ads": "325988270933637a02aa81fa18894a8a51b8ea757c5eb47a7c2741820091a4b8",
-    "goose-video": "961b206411c32504e23d5d0682457dc0b375cb57d9dc8006d6afc5e911c2ecd3",
+    "gooseworks": "ca193d9e089d333a74161634b8bb877954d1d8146dbe6463e24fca20dd5e50d1",
+    "goose-ads": "de1b0342fcc82942e1f9c6a3aa01818973c968cbdb65f7109d73761536d029f8",
+    "goose-video": "9226f2a3373ac4c8f94fdaaede34a30cac7951a160996d56971617097b2b2029",
     "goose-video-local": "189cd2c24bbbb152d700847832b67ce651962959fd2381e878ed7ace6bc96a54",
-    "make-custom-video": "75b7bb468c8dafe09bcdc012b66567a0c2d3860f1eaf962a1444321bb80c0eab",
-    "goose-product-photos": "b6a7bb75e9ca7fad105f45da53708ef63e902b7823d57f1f365f0d62521fd880"
+    "make-custom-video": "08f8fd3ef2713064a7f41d5b18ef0407f746a095bcea4334754013c391a030db",
+    "goose-product-photos": "b72df2f34b846f7d559067eec872d6aa6a350166ec61cf919c2278f7556c1832"
   }
 }