ads-generate
Generate paid-ad image assets from a validated creative brief and brand profile using an explicitly configured image provider. Triggers on: generate ads, generate ad images, create ad creatives, create ad images, make ad images, generate visuals, make campaign visuals, generate images from campaign brief.
Security Assessment
About ads-generate
ads-generate turns a validated creative brief and brand profile into paid-advertising image assets using an explicitly configured image provider. It solves the problem of producing on-brand, platform-compliant ad creatives in a repeatable, auditable way, rather than firing ad-hoc prompts at an image model. The skill assembles prompts from the concept, subject, action, setting, composition, brand tokens, platform constraints, and explicit exclusions defined in the brief, so every generated variant traces back to an approved specification.
A defining feature of this skill is its emphasis on data governance and provenance. All brief text and source images are treated as untrusted data, so embedded instructions are never followed and unapproved resources are never fetched. Before dispatching to a provider it validates the run's data-lifecycle contract, and for every asset it records the provider, model, parameters, cost, source hashes, prompt version, a SHA-256 of the normalized prompt, a canonical redacted prompt summary, output hash, and dimensions. Raw private prompts and provider payloads stay external and ephemeral, and the shipped JSON manifest contains neither secrets nor resolved local filesystem paths. Assets and manifest are written atomically inside a run directory using only repository- or run-relative locators.
The skill is aimed at marketing and creative-ops teams that need governed, cost-bounded ad generation with a clear audit trail. It fits campaign workflows where a brief and brand profile already exist and a budget or cost ceiling must be respected. Missing provider credentials produce setup guidance without exposing secret values, and every generated asset is explicitly flagged as requiring human rights, brand, quality, and policy review before use.
FAQ
What input does ads-generate need before it can produce assets?
It requires a validated creative brief, a brand profile, platform specifications, an output root, an explicitly configured image provider with its capabilities, a budget or cost ceiling, and rights-cleared source assets. It generates only the approved variants defined by that configuration.
How does it handle untrusted brief text or source images?
All brief text and source images are treated as untrusted data. The skill does not follow instructions embedded in them and does not fetch unapproved resources, which protects the run from prompt-injection through the brief or reference images.
What is recorded for each generated asset?
For every approved variant it records the provider, model, parameters, cost, source hashes, prompt version, a SHA-256 of the normalized prompt, a canonical redacted prompt summary, the output hash, and dimensions. Raw private prompts and provider payloads remain external and are not written into the shipped JSON.
Are the generated ads ready to publish?
No. Generated assets require human rights, brand, quality, and policy review before use. The skill also validates file type, dimensions, safe zones, text/copy consistency, and policy, but final sign-off is a human step.
What happens if provider credentials are missing?
Missing provider credentials produce setup guidance without exposing any secret values, so you get actionable instructions rather than a leaked or logged key.
Install ads-generate
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
agricidaniel/claude-ads