mcpbeat

Verify Product Image

gooseworks-ai/verify-product-image

QC gate for a generated static ad image — verify the file opens, matches the requested dimensions, shows the correct product/subject (right shape, colour, label, logo), and has no garbled text or severe artifacts. Records pass/fail/needs-human in verification.md. Used as the final check in the static ad remix flow before shipping.

391 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1086
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/gooseworks-ai/goose-skills --skill verify-product-image

What comes with it

255 bytes besides the instruction
skill.meta.json

The instruction itself

2 sections, as written by the author

verify-product-image

Verify image files open, match requested dimensions, show the requested subject/product, and have no severe artifacts.

Checks

  • Confirm required input files exist.
  • Confirm output files or written plans match the skill contract.
  • Product/asset: the featured hero is the brand's real product (or app UI for SaaS), matching the

kit asset — not a mascot, logo, or placeholder standing in for the product.

  • Brand alignment: colours come from the intended source (the reference's palette for

style_source: template, the kit's documented colors for brand) — **no invented/off-brand

colour** (e.g. an accent pulled off a logo or mascot). Typography matches the kit's fonts.

  • Text/logo: copy and label text are real and correctly spelled; any logo is the brand's correct,

undistorted mark.

  • Record pass, fail, skipped, blocked, or needs human review in verification.md.

How to use it

Copy the folder

Take gooseworks-ai/verify-product-image from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.