agentleFS
adwarp-devadwarp-dev/paid-ads-skills/AGENTS.md

paid-ads-skills

AGENTS.md0 starsChanged 26 days agoMITView on GitHub

This repo holds agent skills for LinkedIn Ads and Google Ads under skills/. Each folder has a SKILL.md with a description that lists the asks it covers. When a request matches a skill's description, read that skill's SKILL.md and follow it from the top: check which data mode applies, follow the method in order, and write the report in the exact format under ## Output. When editing this repo, follow CONTRIBUTING.md and run node scripts/check-skills.mjs and node scripts/build-readmes.mjs before committing.

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a request matches a skill's description, read that skill's SKILL.md and follow it from the top: check which data mode applies, follow …

    line 5
  2. Very specific:

    Prefer Connected mode when the Adwarp MCP tools or the adwarp CLI are available.

    line 7
  3. Distinctive:

    Never change an ad account without showing the exact change and getting the user's confirmation first.

    line 8
  4. Very specific:

    When editing this repo, follow CONTRIBUTING.md and run node scripts/check-skills.mjs and node scripts/build-readmes.mjs before committing.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “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
AGENTS.md

Agent instructions

This repo holds agent skills for LinkedIn Ads and Google Ads under skills/. Each folder has a SKILL.md with a description that lists the asks it covers.

When a request matches a skill's description, read that skill's SKILL.md and follow it from the top: check which data mode applies, follow the method in order, and write the report in the exact format under ## Output.

  • Prefer Connected mode when the Adwarp MCP tools or the adwarp CLI are available. Otherwise use Export mode and ask the user for the CSV the skill names.
  • Never change an ad account without showing the exact change and getting the user's confirmation first.
  • Data under examples/ is made up. Use it for trying a skill out, never as a benchmark.

When editing this repo, follow CONTRIBUTING.md and run node scripts/check-skills.mjs and node scripts/build-readmes.mjs before committing.

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.