agentleFS
gooseworks-aigooseworks-ai/goose-skills/skills/entry/goose-video/SKILL.md

goose-video

Skill1.3k starsChanged 23 days agoMITView on GitHub

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.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 15 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the gooseworks-ai/goose-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about gooseworks-ai/goose-skills

The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 20

Talked about on GitHub (20 times).

On GitHub · 20

15 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never mention tools, ids, JSON, commands, software, vendors, models, timings or retries.

    line 32
  2. Distinctive:

    Follow next_step for setup, rights, claims, spend approval, execution and publishing.

    line 35
  3. Distinctive:

    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 …

    line 38
  4. Distinctive:

    Every video approval, including a higher price or a priced fix, can happen in this chat.

    line 40
  5. Distinctive:

    Never invent an offer, a claim or proof.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GooseWorks video

Installed entry: catalog_fetch type skill goose-video on this connection and follow it. Already fetched this run: no repeat.

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). Cards prove no pick or 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. Before reference or style choices, ask which product or service to advertise, even with only one saved. Use the product card, or ask by name in chat, and wait. Only their stated choice settles it; a brand name does not. Reuse an explicit pick or request for none; find ids with brand_read, [] for none.
  4. Research. Read the kit, learnings and selected products with brand_read, then knowledge_search. Verify product size and use from facts and size-reference photos 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); free, and it reuses the 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. 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 use, text and ending with timestamps. 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 any project write and follow it. 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 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 setup, rights, claims, spend approval, execution and publishing. An active fetched playbook owns research, creative planning and quality gates; generic advice never skips them.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.