agentleFS
Sign inStart free
narayan-metaflownarayan-metaflow/metaflow-marketing-skills/AGENTS.md

metaflow-marketing-skills

AGENTS.md14 starsChanged 7 months agoMITView on GitHub

Use these skills as deep playbooks when the user’s task matches the skill’s domain. Prefer loading SKILL.md end-to-end, then open references/ files when the main doc points to them. Routing (high level): If multiple skills apply, sequence them (strategy → execution → measurement) and say which skill you used for each section.

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

    Use these skills as deep playbooks when the user’s task matches the skill’s domain.

    line 3
  2. Very specific:

    Long-form methodology / beliefs: when a single SKILL is not enough → seo-max-kt (SEO_AND_AEO_KT.md).

    line 12
  3. Distinctive:

    If multiple skills apply, sequence them (strategy → execution → measurement) and say which skill you used for each section.

    line 14

≈ “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 guidance

Use these skills as deep playbooks when the user’s task matches the skill’s domain. Prefer loading SKILL.md end-to-end, then open references/ files when the main doc points to them.

Routing (high level):

  • Google / Microsoft Ads execution, audits, or builds → paid-search slugs (google-ads-*, paid-search-ads-playbook).
  • Meta (Facebook / Instagram) ads → paid-social slugs (meta-ads-*, meta-ads-playbook).
  • Budget mix, reporting, or cross-channel analysis → ad-spend-allocator, campaign-analyzer, paid-media-reporter.
  • Organic + AI answer engines (crawlers, content, measurement) → SEO slugs (seo-*, ai-search-visibility-*, bofu-seo-aeo-strategy).
  • LLM visibility prompt libraries → prompt-picker.
  • Long-form methodology / beliefs when a single SKILL is not enough → seo-max-kt (SEO_AND_AEO_KT.md).

If multiple skills apply, sequence them (strategy → execution → measurement) and say which skill you used for each section.

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.

Check your setup, free