CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

make-product-photos

Use when the marketer says: studio photos of my product without a shoot, product photos for my store page, packshots on white, lifestyle or on-model shots, photos for the new colourway, fresh product imagery for ads, photos for our launch page, our packaging changed — redo the photos, I have no photographer. Delivers store-ready product photos generated from the brand's real product photos: a shot list built from the page slots (hero, alt angle, scale, detail, in use, lifestyle, on-model), only real photos of this product as references, matched to the brand's photography, every shot checked against the real product for shape, parts, logo, text, colour, finish, scale and honest representation, with a keep / maybe / reject verdict and a page order. The human picks the keepers. Never uploads to a store, never shows a size, part, feature or result the product lacks. Not for ads with text, infographics or screenshots — make-static-ads; not for marketplace listing sets (not covered yet).

Quality

98%

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable playbook: concrete engine calls, exact quotes and formats, sequenced steps with hard rules, approval gates, validation checkpoints and error-recovery loops, and no wasted tokens. The only material weakness is that several step-critical references (the atoms/*.ATOM.md sub-playbooks and the ../../../skills/marketing/* gate skills) are not present in the bundle, leaving parts of the navigation dangling.

Suggestions

Bundle the three atoms/ sub-playbooks cited in Steps 2, 4 and 7 (source-audit, shot-list, fidelity-check), or inline their core procedures into those steps — they are the operational core of those steps but no such files exist in the skill bundle.

Resolve the dangling ../../../skills/marketing/* cross-references (claims-gate, spend-gate, honest-review, save-learning, save-to-brain): either ship those gate skills in the bundle or inline the one-line rule each gate needs, so every relative path cited in the body exists.

Add a short bundle map (one line per file: which file owns which step) near the top of the body so navigation across SKILL.md, the three references/ files and the atoms sub-playbooks is fully self-describing.

DimensionReasoningScore

Conciseness

The body is telegraphic and rule-dense with no filler: every line is a tool call, decision rule, or gate (e.g. "a re-shoot is quoted again, with the engine's suggested_control_change offered"), and it never explains concepts Claude already knows. Not 4: there is no over-explanation or padding to trim — parentheticals like the generator-filename list are operational detection heuristics, not digressions.

5 / 5

Actionability

Every step carries concrete executable guidance: exact tool calls with parameters ("gooseworks:photos_generate dry_run: true", "brand_read lean (sections: [\"summary\",\"kit\",\"products\",\"learnings\"])"), verbatim reply strings ("Connect GooseWorks first — I make your product photos through it."), and exact write-back formats ("Product imagery ready: <photo links> · <YYYY-MM-DD>"). Not 4: the specific examples cover the common cases end-to-end, including both host modes and failure paths.

5 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit validation checkpoints and feedback loops: the hero read-back where "a blocker, or controls the shot needed dropped, stops the run and goes to the human before the rest is spent", the fidelity check on every passed/flagged output, re-shoot re-quoting, workflow_error handling, and bounded polling with "never resubmit (it pays again)". Not 4: validation is not merely present but gated (four named approval gates, a 'Done when' zero-false-passes criterion), covering the money and batch risks.

5 / 5

Progressive Disclosure

Structure is good: the three references/ files exist and are cited by resolvable section numbers one level deep ("Load references/fit-and-honesty.md §1", "references/shot-list-and-surfaces.md §1–2", "rubric in references/fidelity-rubric.md"), and SKILL.md stays an overview. Not 5: the atoms/source-audit, atoms/shot-list and atoms/fidelity-check sub-playbooks (the operational core of Steps 2, 4 and 7) and five ../../../skills/marketing/*/SKILL.md gate references do not exist in the provided bundle, so navigation is partly dangling. Not 3: the references that do exist are clearly signaled with section anchors and the content split is appropriate.

4 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit quoted trigger phrases, a concrete what-clause covering the full deliverable pipeline, third-person voice throughout (the 'I have no photographer' line sits inside a quoted user trigger, not the description's own voice), and explicit out-of-scope pointers that route adjacent requests elsewhere. Its only cost is density — it packs a lot into one paragraph — but every clause is load-bearing rather than padded.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions with comprehensive coverage: "a shot list built from the page slots (hero, alt angle, scale, detail, in use, lifestyle, on-model)", "only real photos of this product as references", "every shot checked against the real product for shape, parts, logo, text, colour, finish, scale and honest representation", "a keep / maybe / reject verdict and a page order". Not 4: the gaps are not minor — inputs, curation, checking, verdicts and delivery are all explicitly named.

5 / 5

Completeness

Both halves are explicit: "Use when the marketer says: …" provides the when with concrete trigger phrases, and "Delivers store-ready product photos generated from the brand's real product photos: …" provides the what. Not 4: the when is not merely present but rendered as quoted user-voice triggers, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural phrasings a marketer would actually say: "studio photos of my product without a shoot", "packshots on white", "lifestyle or on-model shots", "photos for the new colourway", "fresh product imagery for ads", "our packaging changed — redo the photos", "I have no photographer". Not 4: synonyms and colloquial variants (packshots/imagery/colourway) are covered, not just a few good keywords.

5 / 5

Distinctiveness Conflict Risk

A clear niche (store-ready product photography generated from the brand's own product photos) with explicit disambiguation: "Not for ads with text, infographics or screenshots — make-static-ads; not for marketplace listing sets". Not 4: it doesn't just avoid overlap, it actively routes adjacent intents to the correct sibling skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gooseworks-ai/goose-skills

Path

drafts/marketing/make-product-photos/SKILL.md

Reviewed

Table of Contents

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.