CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

goose-product-photos

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/entry/goose-product-photos/SKILL.md
SKILL.md
Quality
Evals
Security

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.
Repository

gooseworks-ai/goose-skills

Path

skills/entry/goose-product-photos/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.