Menu

Individual skill

make-static-ads-graphic-request

0upvotes

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.

skills/marketing/make-static-ads-graphic-request/SKILL.md

Read pinned source

Source commit df8298140d434a6363de0c265eb6af2e571d97a5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,315
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# graphic-request

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:
- email-lifecycle's `lifecycle/flows/<flow-slug>.md` (header art for a flow message);
- run-organic-social's `social/calendar/<start-date>.md` (a single image or a carousel's slide-1 cover);
- make-content's `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.
Back to top