Creates one simple, non-ad brand graphic for placements such as email headers, social posts, stories, or blog previews. It checks claims and image rights, requires approval of the quoted cost, and returns the graphic link with alt text. Best when purpose, placement, and wording are already set.
Makes one simple non-ad brand graphic, such as an email header, social feed or story image, or a blog or link-preview image, in the brand's style with at most a short line of text, after claim and rights checks and a yes to the quote; returns the link and alt text. Not for carousels, decks or print. Use alone when you already have the purpose, placement and exact wording; otherwise run make-static-ads.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
No concept board: the request's purpose and exact text are the basis. Record both in the batch file.
Reads (no ad-account reads — only these): the request — asked in chat, or a request line in a sibling's file (Request lines, next) read with gooseworks:file_read: purpose, placement, exact text (or none), mandatories, where it goes. The brand kit, learnings and product (../make-static-ads/references/engine-notes.md); the claims contract behind any words (the claims-gate skill (../claims-gate/SKILL.md) §1).
Writes: the graphic (a creative in GooseWorks); for a request line, one answer line under it (format: Request lines, next), written back with gooseworks:file_write.
Request lines. Requests arrive as Graphic needed: for make-static-ads · <purpose, placement, exact text> · return to: <path> lines (open = no Graphic ready: line under it), in:
lifecycle/flows/<flow-slug>.md (header art for a flow message);social/calendar/<start-date>.md (a single image or a carousel's slide-1 cover);content/repurposed/<source-slug>/<date>.md and content/drafts/<date>-<slug>.md.
Older files may still carry a Header art needed: line or a plain asset line naming this side door — treat it the same way.
Answer under the request (re-read the file, insert, write it all back): Graphic ready: <link> · <YYYY-MM-DD> · alt: <text> · <ratio> · claims: <ok / cut …>. The requester reads it on its next run.../make-static-ads/references/formats-and-placements.md §1.gooseworks:ads_template_read mode: "static_library"); describe it in the prompt; graphic requests never attach a template image (find-references §4 covers ads).make-static-ads-compose skill (../make-static-ads-compose/SKILL.md): the shared foundation, the layout, and the exact text as the marketer or request line gave it. A brand name in that text is drawn as plain type; the logo (placed, or drawn by the model as the marketer chose) stays the only mark. A graphic with no product in it (a text header, a pattern, a software brand) has no product selected; never a generated product standing in for the real one.make-static-ads-claims-extract skill (../make-static-ads-claims-extract/SKILL.md) on any words in the prompt ("clinically proven" in a header is still a claim); rights on any person or logo; no CTA button, offer badge or price unless asked. Organic use → the disclosure rules in ../ad-policy-check/disclosure.md.gooseworks:ads_render dry_run: true; the quote as given, plus the redo sentence (../make-static-ads/references/handoff-format.md §2); the human's yes in this chat (the spend-gate skill (../spend-gate/SKILL.md), branch A). A request line in a file is never a yes.make-static-ads-render-review skill (../make-static-ads-render-review/SKILL.md): the judge with rubric checks 2, 3, 8, 15, 16 and legibility at 375 px, you with 1 and 20 (its step 3), and its one retry (no idea or template check).Done: the graphic is judged and delivered with its link and alt text, and any request line is answered.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
The supplied material contains only placeholder text for the skill’s purpose, inputs, steps, and completion criteria. It does not provide enough information to describe a task or result reliably.
Research supported advertising angles using buyer context, current product facts, customer language, and observed ads. Turn the evidence into static ad, video, or copy ideas, matching video concepts to available recipes. Scores rank ideas for testing; they do not predict results.
Analyze campaign data from Google, Meta, and LinkedIn to find strong and wasteful spend. The skill checks funnel performance and test results, then recommends which campaigns to pause, scale, or test and how to shift budget across channels.
Compare ad spend and signups with downstream outcomes to calculate the cost of each qualified lead. The skill checks tracking coverage, accounts for how long leads need to mature, and groups creatives into actionable categories with confidence notes.
Prepare the intake for a Meta ad campaign by reviewing available brand information first, stating reasonable assumptions, and asking only questions whose answers could affect budget, claims, or legal exposure. It records stable brand facts, a campaign brief, and what was asked versus assumed.
Review ad copy, image text, visuals, and people against platform and brand category rules. It suggests honest fixes and needed disclosures, then flags issues requiring human or legal review, with a separate result for each ad and platform.