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

goose-product-photos

Skill1.3k starsChanged 23 days agoMITView on GitHub

Make product photos (studio, lifestyle or on a model) of a brand's real products with GooseWorks in this chat. Start brand work with brand_knowledge_browse and follow the next_step in every answer.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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 GooseWorks to photograph the customer's physical products, here in this chat.

    line 11
  2. Distinctive:

    Follow the photos with photos_read until they are ready.

    line 22
  3. Distinctive:

    Keep or drop each photo with photos_update: brand_id, the photo's output id and action "approve" (keep) or "archive" (drop, with an …

    line 23
  4. Distinctive:

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

    line 32
  5. Distinctive:

    Follow the next_step in every answer.

    line 35
  6. Distinctive:

    Start brand work with brand_knowledge_browse and its core.

    line 38
  7. Distinctive:

    Never invent an offer, a claim or proof.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 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 brand_knowledge_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 from the same call as a dry run (free, it makes nothing), 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 each photo with photos_update: brand_id, the photo's output id and action "approve" (keep) or "archive" (drop, with an optional reason). 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 brand_knowledge_browse 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.

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.