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

goose-ads

Skill1.3k starsChanged 23 days agoMITView on GitHub

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.

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:

    Use this entry for existing-ad operations and analysis.

    line 11
  2. Distinctive:

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

    line 35
  3. Distinctive:

    Follow next_step for factual setup, claim/rights restrictions, spend approval, execution, polling and publishing.

    line 38
  4. Distinctive:

    Read the brand and its listed knowledge actions for core rules and task evidence.

    line 41
  5. Distinctive:

    Never invent an offer, a claim or proof.

    line 42

≈ “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 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_creative_read.
  • One finished ad: an animation with ads_creative_animate (price it first, free, with ads_creative_animation_quote), its tags or rating with ads_creative_update. A new size with ads_creative_resize only when the customer asks: it spends credits and has no free price check, so say that and wait for their yes before calling it.
  • The customer's own image as a template: ads_template_create. 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_call_provider and data_post_provider.

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.

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.