agentleFS
vindreshsinghvindreshsingh/engineering-skills/marketing/SKILL.md

marketing-router

Skill0 starsChanged 5 months agoMITView on GitHub

Routes marketing tasks to the right skill and agent in the marketing team. Load when you need to market a product, grow traffic, write content, post on social, improve SEO, or engage a community — and you're not sure which marketing skill or agent to use.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run in this order unless the campaign brief says otherwise:

    line 44
  2. Distinctive:

    All agents report metrics to growth-lead for weekly review

    line 76
  3. Distinctive:

    No ICP defined before content creation

    line 87
  4. Distinctive:

    No primary metric or weekly review

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Marketing Router

The marketing team has eight skills and eight agents, grouped under skills/marketing/ and agents/marketing/. This router maps your task to the right process — then load that skill's SKILL.md and follow it fully ([[skill-router]] pattern for the Grow phase).

When to Use

  • Product is live and you need marketing but don't know where to start
  • Unsure whether you need strategy, content, social, SEO, or community
  • Onboarding the marketing team for a campaign
  • Coordinating multiple marketing agents on one launch

Skip when you already know the agent — go directly to prompts/agents/marketing/<agent>.md.

Process

1. Classify the marketing task

You need to…Load skillRun agent
Plan GTM, positioning, channels, campaign calendar[[growth-strategy]]growth-lead
Write blog, tutorial, newsletter, landing copy[[content-marketing]]content-marketer
Post on X/LinkedIn/Reddit, launch threads[[social-distribution]]social-media-manager
Improve rankings, keywords, landing page SEO[[seo-growth]]seo-strategist
Build community, welcome flows, engagement[[community-engagement]]community-manager
Plan and run paid ads (Google, LinkedIn, Reddit)[[paid-ads]]paid-media-manager
Design email welcome / nurture sequences[[email-nurture]]email-marketer
Build referral / invite loops[[referral-loop]]referral-manager

Skill files live at skills/marketing/<skill-name>/SKILL.md.

2. Default sequence for a new product launch

For a full launch, load [[launch-campaign]] — the Grow-phase conductor that runs this whole sequence with intake, sign-off, and the community-before-traffic ordering gate, and assembles the launch kit. Use the steps below directly only when running one phase in isolation.

Run in this order unless the campaign brief says otherwise:

growth-lead (strategy + briefs)
  → community-manager (seed before traffic)
  → seo-strategist (landing page + keywords)
  → content-marketer (launch blog + tutorials)
  → social-media-manager (post pack + launch thread)
  → growth-lead (weekly review)

Critical rule: community-manager seeds content before social-media-manager drives traffic.

3. Load references when executing

SkillReference checklist
social-distributionchannel-checklist.md
paid-adspaid-ads-checklist.md
email-nurtureemail-nurture-checklist.md
referral-loopreferral-loop-checklist.md
content-marketingcontent-checklist.md
seo-growthseo-checklist.md
community-engagementcommunity-checklist.md
growth-strategyAll of the above when reviewing channel feasibility

4. Hand off rules

  • growth-lead produces briefs — does not write posts or articles
  • content-marketer hands social snippets to social-media-manager
  • seo-strategist hands spoke topics to content-marketer
  • community-manager coordinates launch timing with social-media-manager
  • All agents report metrics to growth-lead for weekly review

Common Rationalizations

  • "Let's just post on social first" — Without positioning and seeded community, posts bounce.
  • "SEO can wait" — Every month delayed is compounding traffic lost.
  • "One person does it all" — Run agents sequentially; each has a focused process.
  • "Marketing is separate from product" — Community feedback loops back to product-manager.

Red Flags

  • No ICP defined before content creation
  • Social launch before community is seeded
  • Same caption cross-posted to every platform
  • SEO keywords assigned to multiple pages (cannibalization)
  • No primary metric or weekly review

Verification

  • Task mapped to correct skill and agent
  • Launch sequence respected (community before social traffic)
  • Reference checklist identified for the skill
  • Next agent in the chain noted

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.