agentleFS
lilly-buildslilly-builds/ads-cooking/skills/copy/SKILL.md

copy

Skill0 starsChanged 2 months agoMITView on GitHub

Change the wording on a live Meta ad. Builds a new creative with the new text and points the existing ad at it, so the ad keeps its id and its delivery history. Use when the user says "/ads-cooking:copy", "change the ad copy", "update the headline", "the wording isn't working", or wants to test different text on a running ad.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scope, prototype and 4 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.
  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 3 projects that use this

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 4 projects that use this

  • photon-groveSkill

    unslop

    Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask when it launched. Changing the creative on a live ad set can restart the learning phase, and at a small daily budget that costs a few …

    line 35
  2. Distinctive:

    If they want to test new copy without disturbing a campaign that is working, the safer move is duplicating the ad set and changing the copy …

    line 39
  3. Very specific:

    Never run --go without them asking in that turn.

    line 44
  4. Distinctive:

    Do not rewrite their copy unless they asked you to.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 11 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

Change the copy on a live ad

First, say what this actually does

Ad creatives cannot be edited. So changing a headline is not an update, it is: build a new creative with the new text, then point the existing ad at it. The ad keeps its id, which is what preserves its delivery history. Worth saying once, because "why is there a new creative in my account" is a reasonable question.

Edit the text

In campaign.json, under creative: primary_texts and headlines. Several of each is better than one. Meta picks the combination per person, which beats splitting a small budget across near-identical ads.

Run it

PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m adscooking copy

Dry run. Shows what would change, sends nothing. Then, only if they confirm:

PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m adscooking copy --go

Before running it on a campaign that is still learning

Ask when it launched. Changing the creative on a live ad set can restart the learning phase, and at a small daily budget that costs a few days of stable delivery. If it launched in the last few days, say so and let them decide whether it can wait. Do not just do it quietly.

If they want to test new copy without disturbing a campaign that is working, the safer move is duplicating the ad set and changing the copy on the duplicate. That leaves the original alone.

What not to do

  • Never run --go without them asking in that turn.
  • Do not rewrite their copy unless they asked you to. Changing the wording is their call; this command's job is to get their wording live.

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.