agentleFS
inreels-aiinreels-ai/inreels-skills/skills/ad-creative/SKILL.md

ad-creative

Skill1 starsChanged 11 days agoMITView on GitHub

Produce static ad creatives — hook, angle, and rendered image — for a product or landing page, using the inReels MCP server. Use when asked to make ads, ad creatives, Meta/Instagram/TikTok ad images, or to test creative angles for a product.

85 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use popups, free-tools and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • CesarjoquinSkill

    free-tools

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    Also in 19 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 20 projects that use this

  • timruebenachSkill

    competitor-profiling

    When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

    Also in 23 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • +6 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not generate anything yet.

    line 27
  2. Distinctive:

    If the user gave you a landing page, read it first.

    line 37
  3. Distinctive:

    Look at what the page's objection-handling and FAQ reveal about the real hesitation, and aim there.

    line 39
  4. Very specific:

    Call list_models and pick on what the creative needs:

    line 56
  5. Very specific:

    If the user supplied product photos, pass them as ref_urls so the product in the ad is the real product.

    line 67
  6. Distinctive:

    When the user wants options, change exactly one variable per creative — the angle, or the framing, or the product placement — and say which.

    line 93
  7. Distinctive:

    Product legible at thumbnail size: If it is unrecognisable at 100px wide, the creative does not work, however good it looks full size.

    line 106
  8. Distinctive:

    Do not loop. If two renders in a row miss, the prompt is wrong, not unlucky.

    line 115

“Common” is measured: kept by at least 6 in 10 of the 77 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ad creative

Turn a product into ad creatives that a buyer could actually run: a stated angle, a hook written to be read in under a second, and a rendered image sized for the placement.

Requirements

The inReels MCP server must be connected. Check with get_account — if it fails, the user needs to add the connector:

claude mcp add --transport http --scope user inreels https://www.inreels.ai/api/mcp

Then set an API key from https://www.inreels.ai/dashboard/settings/api-keys.

Method

1. Get the angle before the image

Do not generate anything yet. Ads fail on the angle far more often than on the render, and an image made before the angle is settled is a wasted credit.

From the product (URL, description, or images the user gave you) establish:

  • Who it is for, specifically. "Busy people" is not a who.
  • The friction they feel today, in their words, not the brand's.
  • The angle — the single claim this creative makes. One per creative.
  • The hook — 3 to 7 words, readable at a glance in a feed.

If the user gave you a landing page, read it first. The page's own headline is usually the weakest available angle, because it was written to satisfy everyone. Look at what the page's objection-handling and FAQ reveal about the real hesitation, and aim there.

State the angle and hook back to the user before spending anything. One round of correction here is worth three regenerations.

2. Price it

quote { "media": "image", "image": { "prompt": "<your prompt>", "aspect_ratio": "9:16" } }

The number returned is exactly what the generation charges. Report it if the user has not already approved a spend.

3. Choose the model deliberately

Call list_models and pick on what the creative needs:

  • nano-banana — the default. Good general renderer, accepts up to 3 reference images, so this is the one to use when the real product must appear.
  • nano-banana-pro — when the creative carries text or needs detail to hold up at full size.
  • flux-schnell — cheapest. Use it to test several angles quickly before committing to a final render.
  • flux-kontext-pro — editing. Requires exactly one reference image, and edits it rather than inventing a new scene.

If the user supplied product photos, pass them as ref_urls so the product in the ad is the real product. An invented stand-in is the fastest way to make a creative unusable.

4. Render

generate_image {
  "prompt": "<scene, framing, lighting, where the product sits, where text goes>",
  "aspect_ratio": "9:16",
  "model": "nano-banana",
  "ref_urls": ["https://…/product.jpg"]
}

This returns a run_id immediately. Then:

get_run_status { "run_id": "…", "wait": true }

wait: true blocks up to 45 seconds and usually returns a finished image in one call. Never give the user a URL before the run reports completed.

5. Vary one thing at a time

When the user wants options, change exactly one variable per creative — the angle, or the framing, or the product placement — and say which. Four images that differ in everything teach nothing about what worked.

Prompting for ads specifically

What actually moves ad performance, in rough order:

  • Leave room for text. Decide where the hook will sit and keep that area uncluttered. State it in the prompt: "lower third clear for text overlay".
  • Native over polished. Feed ads that look like studio work read as ads and get scrolled. Phone-camera framing, ordinary light, and a real surface beat a seamless gradient.
  • Product legible at thumbnail size. If it is unrecognisable at 100px wide, the creative does not work, however good it looks full size.
  • One subject. Two competing focal points halves both.

Spending rules

  • quote before generate_image whenever the user has not pre-approved.
  • Failed runs are refunded in full, so a failure is not a loss — but a successful render of the wrong angle is.
  • Do not loop. If two renders in a row miss, the prompt is wrong, not unlucky; go back to the angle and say so.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.