gooseworks-ai/goose-skills / skills/marketing/make-static-ads
make-static-ads
VerifiedMake new static image ads, a fresh batch, more ads, a winner's variations, copy variants or a rejected ad fix. Reads the brand, its customers and the ads it already runs, turns real product facts and customer situations into distinct visual ideas, shows a concept board, writes each render prompt, quotes, renders and reviews through GooseWorks. Also handles requested branded header/social graphics. Use for static ad creation rather than goose-ads. Not for video, product photos or launching campaigns.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| references/brand-profile.md | markdown | 4.9 KB |
| references/claims-and-policy.md | markdown | 6.9 KB |
| references/engine-notes.md | markdown | 3.4 KB |
| references/fonts-and-color.md | markdown | 2.5 KB |
| references/formats-and-placements.md | markdown | 2.2 KB |
| references/handoff-format.md | markdown | 4.3 KB |
| references/ideas.md | markdown | 6.5 KB |
| references/levels.md | markdown | 4.2 KB |
| references/prompts.md | markdown | 7.7 KB |
| references/reading-the-brain.md | markdown | 6.0 KB |
| references/review-rubric.md | markdown | 6.6 KB |
| scripts/README.md | markdown | 2.1 KB |
| scripts/place_logo.py | script | 3.6 KB |
| scripts/repair_patch.md | markdown | 2.5 KB |
| scripts/repair_patch.py | script | 9.0 KB |
| scripts/template_sheet.py | script | 3.7 KB |
| skill.meta.json | config | 6.3 KB |
| tests/test-by-hand.md | markdown | 4.9 KB |
| tests/test_place_logo.py | script | 1.9 KB |
| tests/test_repair_patch.py | script | 5.9 KB |
| tests/test_template_sheet.py | script | 1.5 KB |
tests/test-by-hand.md
View on GitHub# make-static-ads — test by hand
**Also test through staging, not only from a local copy:** merge, let the catalogue deploy, then give a fresh agent only the marketer's words (Test 0).
**The bar:** this playbook must produce better ideas than a capable agent with no playbook at all. If it doesn't, it is making agents worse (it did, up to 0.5.4). Test 1 is the acceptance test; run it after any change to the idea steps.
## Setup
1. Connect GooseWorks **staging** to your agent.
2. Link the skills side by side, as `docs/marketing/README.md` (How to test) says, so the playbook can open its steps at `../make-static-ads-<step>/`.
3. Generation spends credits. Tests 1–3 stop at the quote and cost nothing.
## Test 0 — the real loop on staging
A fresh agent connected to GooseWorks staging gets only "make 5 static ads for <brand>". It follows the server and loads the playbook from the staging catalogue. **Passes if:** it writes `profile.md` from the brand's own ads, posts, site and kit; asks short clickable questions with the host's question tool, never a paragraph (creativity first, recommendation first; covering angles with the brand's own first, product, count, conflicts); every board row names its angle and template; the brand's marketer looks at the board and says "yes, we'd run these".
## Test 1 — beats a no-playbook agent (free)
Pick a staging consumer brand with real product photos that no earlier test used. Run two fresh agents in parallel, same brand, same words: **"Make 5 static ads for <brand>. Your choice on everything. Stop before spending credits and show me the concept board."**
- **Agent A** reads this playbook.
- **Agent B** gets no playbook: "Use your own judgment; don't open any GooseWorks playbook or skill catalog."
Both may read the brand on staging and browse the web. Neither sees the other's work or any earlier batch's concepts.
Then a third fresh agent compares the two boards, shuffled and unlabelled, row by row, with two of the brand's real ads beside them: Would this brand run it? Would a competitor's product fit this ad (swap test)? Is it an idea or a demonstration? Do the five say different things? Which board would you pay to render?
**Passes if:** the blind comparison prefers A's board or calls them even, and A's board has at most one demonstration, five different meanings, a source or hypothesis label on every row, a protected choice on every row, and critic notes with real changes.
**Telltale failures:** product + headline + the product doing its job, five times; headlines that name features ("Two oils. Different jobs."); a board that says "read" where the agent skimmed; critic notes with no changes.
## Test 2 — short answers don't skip the board
Say "your choice, show me the final ads only, make one ad", then "make 5 more".
**Passes if:** the quote message still shows the board (one row, then five) with each ad's template sheet as an image; the five don't repeat the first ad's meaning or the brand's live-ad messages; a fresh critic ran on both.
## Test 3 — B2B SaaS, no product photo
Brand: Gooseworks on staging, or any SaaS. Say: "Make me six LinkedIn ads for our product."
**Passes if:** the ideas start from customer situations, not the feature list; it asks for real screenshots instead of generating UI; no customer logo or stat without a confirmed claim.
## Test 4 — nothing on file
A brand with no claims, no reviews and no own ads (staging: Greener Closet). Say: "Ads for our app launch."
**Passes if:** it reads public reviews or says there are none; marks every authored situation as a hypothesis; writes only puffery and verified facts; never invents ratings, users or reviews.
## Test 5 — paid render and review (small)
Approve two ads from a passing board. **Passes if:** each prompt contains the board's protected choice word for word and names each attached image's role; no ad-library ad's image is attached; at close and balanced the brand's own ad or a library template is attached as the layout image; each finished ad has its "Based on" sheet; a fresh judge checks the idea first, then the product and spelling; at most one retry per image within the quote; failures are shown, not hidden.
## Test 6 — reactive modes
- "My image ad got rejected for 'personal attributes'." → finds the faulty line; copy-only fixes are free; an image fix keeps the scene and changes only the faulty part, quoted; both checks re-run.
- "Same image as #3, three other headlines." → says these test copy, not ideas; re-render with the approved image attached, quoted and judged.
- "A 600-wide header for the welcome email, text: 'Welcome to the routine'." → no CTA button, claims check, quote and yes, `Graphic ready:` line.
## Test 7 — garbled label, good idea
A render whose scene passes but whose printed label drifted. **Passes if:** the original stays failed; the free label repair runs only with a compatible pose and rights checked; the patched image is judged again in full; nothing is hidden.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |