agentleFS
AbdulFaiz123AbdulFaiz123/founder-skill-eu/skills/founder-marketing/SKILL.md

founder-marketing

Skill1 starsChanged 13 days agoMITView on GitHub

Your marketing director. Turns the buyer panel and the competitor map into positioning, the channels the target customer actually uses, a 30-day launch campaign with dated posts and ads, the first ten hooks, a budget split and the numbers to watch. Every message answers an objection real or simulated buyers raised. Use when the user says "how do I market this", "marketing plan", "launch campaign", "how do I get customers", "where do I advertise", "write my ads", or "positioning".

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Very specific:

    If none of these exist, say what is missing and offer to run /founder-consumer --quick first.

    line 31
  2. Distinctive:

    No fake reviews, follower counts, testimonials, before/afters or "as seen on".

    line 77
  3. Distinctive:

    Never offer a discount or gift for a Google review unless it is disclosed and for any review, not just good ones.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

founder-marketing

A business no one hears about does not exist. This skill plans how the first customers hear about it, using what the rest of the pack already learned instead of a generic playbook.

Step 1: read the evidence

  • founder/panel/results.md: who buys, who doesn't, and why. The segments with the highest buy rate are the first audience. The top objections are what the marketing must answer.
  • founder/competitors.md: how competitors position themselves (so you do not sound like them) and the gap.
  • founder/offer.md and founder/pricing.md: what is being sold, at what price.
  • founder/numbers.json: what a customer is worth, which caps what you can spend to win one.

If none of these exist, say what is missing and offer to run /founder-consumer --quick first. Do not invent an audience.

Step 2: positioning

One line, then the reasons:

For <the segment that buys most>, who <their problem in their words>,
<business> is the <category> that <the gap>, unlike <the nearest alternative>.

Give three versions, recommend one, and say which panel evidence supports it.

Step 3: channels

List where the first audience actually spends attention, specific to the business type and place: foot traffic and window signage, Google Maps (huge for local search in Europe), Instagram and TikTok, local creators, nebenan.de and neighbourhood Facebook or WhatsApp groups, Kleinanzeigen, Too Good To Go for food, university and Erasmus groups, partnerships with nearby businesses, LinkedIn for B2B, email, paid search, paid social. Pick the language(s) on purpose: in German cities a German-first message reaches more people, English reaches expats and tourists. For each: why it fits this buyer, rough cost, and how you will know it worked. Pick two or three to start; say what you are not doing and why.

Step 4: the 30-day campaign

founder/marketing.md gets a dated calendar from launch minus 14 days to launch plus 16: what goes out each day, on which channel, with the message. Include:

  • Ten hooks, each answering one panel objection or using one buyer reason, written for the format (a 3-second opening line for video, a headline for an ad, a sign in the window).
  • The launch-week offer from founder/pricing.md and when it ends.
  • What to post when there is nothing new to say (behind the scenes, the making of).

Step 5: budget and numbers

  • The budget split across the chosen channels.
  • The most you can pay to win a customer: from the CFO's contribution per unit and the panel's purchases per buyer, show the sum.
  • The three numbers to watch weekly and the level that means "change something".

Rules

  • No fake reviews, follower counts, testimonials, before/afters or "as seen on".
  • Panel quotes are research; never use them as customer quotes in ads.
  • Disclose paid partnerships: creator posts are labelled "Werbung" or "Anzeige" in Germany, including free products given for a post.
  • Email, SMS and WhatsApp marketing to consumers need prior opt-in consent (GDPR and, in Germany, section 7 UWG); use double opt-in for the newsletter and the waitlist. No cold emails or bought lists.
  • Tracking pixels (Meta, TikTok, Google) need cookie consent before they fire (ePrivacy; Germany: TDDDG); budget for a consent tool and expect fewer tracked conversions than US guides promise.
  • Ads may not target minors with profiling or use sensitive data (Digital Services Act). Health and earnings claims follow the user's market rules.
  • Never offer a discount or gift for a Google review unless it is disclosed and for any review, not just good ones. Not legal advice.

Output

founder/marketing.md. Next: /founder-brand, then /founder-launch.

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.