agentleFS
ajstars1ajstars1/founder-stack/marketing/SKILL.md

marketing

Skill1 starsChanged 17 days agoMITView on GitHub

Marketing for founders: offers, lead magnets, upsells, continuity, headlines, copy, sticky messages, word of mouth, referrals, channel tests, growth experiments, activation, retention, ethical persuasion. Use for \"offer\", \"copy\", \"ads don't pay back\", \"nobody shares\", \"churn\", \"which channel\".

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing, research 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.
  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.

    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

    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 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read the venture context if it exists: discovery/00-CONTEXT.md, discovery/LEDGER.md and discovery/FIELD-NOTES.md (own numbers beat book …

    line 11
  2. Distinctive:

    If two rows fit, pick the one matching the buyer's or user's latest *action*, not their words.

    line 15
  3. Distinctive:

    Every lever must be true: real limits, real deadlines, real proof.

    line 42
  4. Distinctive:

    Remove effort before the first reward.

    line 43
  5. Distinctive:

    Every channel and claim wears out, so keep a pipeline of tests [Weinberg] [Schwartz].

    line 45
  6. Distinctive:

    Every answer ends with:

    line 60
  7. Very specific:

    Before: /problem-discovery, /customer-discovery, /jtbd, /where-to-play, /value-proposition-canvas.

    line 72
  8. Very specific:

    After: /experiments, /facts-assumptions-unknowns, /business-model-canvas, /startup-scorecard.

    line 74
  9. Very specific:

    If the business-books MCP is connected, search_library / read_passage give the original passages behind a playbook.

    line 77

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

Marketing

Turns a validated problem into paying customers through the offer, the message, the spread and the growth system. Synthesized from eleven marketing books, each method credited.

Start here

  1. Read the venture context if it exists: discovery/00-CONTEXT.md, discovery/LEDGER.md and discovery/FIELD-NOTES.md (own numbers beat book benchmarks). Else ask at most 3 questions: what you sell and to whom, stage and evidence so far, the decision at hand.
  2. Gate before tactics: does a reachable group already want this, and does the product deliver? If not, route to audience-and-permission or /customer-discovery. Copy can't fix a market problem.
  3. Route with the table below and read only the matching playbook, or two at most. If two rows fit, pick the one matching the buyer's or user's latest action, not their words. Name other relevant playbooks; don't read them.

Router

The founder says / needsPlaybook
"People compare us with cheaper options." "Close rate is low." "Should we discount?"playbooks/offer-design.md
"What should we give away to get leads?" "Our free offer brings junk."playbooks/lead-magnets-and-attraction-offers.md
"Ads don't pay back." "Cash runs out before customers pay off." "How do we upsell or keep them paying?"playbooks/money-model.md
"The headline or landing page falls flat." "The claim that used to work has died." "They don't believe us."playbooks/copywriting-and-headlines.md
"People nod and forget." "We explain it like engineers." "Our pitch doesn't change anything."playbooks/sticky-messages.md
"Nobody talks about us." "Should we pay for referrals?" "We went viral and sales didn't move."playbooks/word-of-mouth-and-virality.md
"Which channel should we use?" "Nothing works." "Our one good channel gets worse every quarter."playbooks/channel-selection.md
"Our posts get likes, not leads." "The community removed our post." "Where should we post or list our startup?"playbooks/founder-posts-and-communities.md (+ reference/places-to-post.md for the list)
"Do we have product/market fit?" "We have too many growth ideas." "Can we scale spend yet?"playbooks/growth-experiments.md
"Users sign up and never come back." "They never reach the point where it clicks." "Members churn in month three."playbooks/activation-and-retention.md
"Is this countdown, scarcity claim or notification over the line?" "Buyers regret it."playbooks/ethical-persuasion.md
"We're for everyone and nobody cares." "Who do we target first?" "How do we build an audience or list?"playbooks/audience-and-permission.md
"The rational fix is too expensive." "Customers act irrationally." "Discounts aren't working."playbooks/reframing-and-psycho-logic.md
"Can we raise prices?"playbooks/offer-design.md for value; the price itself is /gtm

Principles

  1. Steer desire that already exists. Market beats offer, and offer beats copy [Schwartz] [Hormozi] [Godin].
  2. Go narrow first. Win a small group completely before you widen [Godin] [Hormozi] [Berger].
  3. Marketing amplifies the product and can't replace it. Plug leaks before you pour in traffic [Ellis] [Weinberg] [Eyal].
  4. Value is perceived. Try the cheap psychological fix before the expensive logical one, then test it [Sutherland] [Hormozi].
  5. Price is a signal. Compete on proof, speed and certainty, not discounts [Hormozi] [Godin] [Sutherland] [Cialdini].
  6. Status and identity drive choice. Ask what people like your buyer do, and how buying changes how they are seen [Godin] [Berger] [Heath].
  7. Every lever must be true: real limits, real deadlines, real proof. Fake cues borrow against trust [Cialdini] [Hormozi].
  8. Remove effort before the first reward. Ask for effort after it [Eyal] [Ellis] [Sutherland].
  9. Believe behaviour over opinion. Money, usage and clicks outrank what people say [Sutherland] [Ellis] [Weinberg].
  10. Every channel and claim wears out, so keep a pipeline of tests [Weinberg] [Schwartz].
  11. Earn before you ask: be useful where your buyers gather before asking them for anything [Godin] [Cialdini] [Weinberg].

When the experts disagree

TensionGo with A when…Go with B when…
Hard offer with enhancers [Hormozi] vs. patient permission [Godin]Desire exists, results show within weeks, and the sale is 1:1 services or localYou're asking for new behaviour, repeat trust is the asset, or the crowd isn't hungry yet. Godin picks who, then Hormozi packages the offer
Data-led testing [Ellis] vs. psycho-logic [Sutherland]The decision has high traffic and fast feedback: onboarding, pricing pages, invitesYou're generating ideas, or the effects lag (trust, brand, signalling). Run them as protected moonshots with holdouts
Reach everyone, stay on air [Sharp] vs. smallest viable audience [Godin]Known category and buyers; the job is staying remembered. Keep a steady rhythm, never go darkEarly and unknown: win one peer group first; borrow only Sharp's consistency
Channels from day one [Weinberg] vs. loops after must-have [Ellis]You're pre-fit and channel tests are cheap research, or the product is sold through outside channels (sales, BD, events)You're post-fit and usage recruits the next user
Lead with the core claim [Heath] vs. delay it [Schwartz]The audience has context: staff, investors, a first-to-market claimThe market is cold, sceptical or saturated. Lead with identity or mechanism and land the claim later
Remove friction [Eyal] [Ellis] vs. add effort [Sutherland] [Hormozi]It's before the first rewardIt's after the reward, or you need to filter out free-lead tourists
Pay for referrals?No cash for talk; it crowds out the real motive [Berger] [Eyal]In-kind rewards tied to core value [Ellis], or affiliates paid per sale as a channel [Weinberg]

Output contract

Every answer ends with:

  • Recommendation: the call, specific to their business.
  • Deliverable: the artifact, filled in (offer stack, headline set, channel ring, test card, hook map).
  • Why: the framework(s) behind it, credited [Author].
  • Assumptions to log: each one as a ledger item (A#, [ASSUMPTION, E0]) with the cheapest test and its evidence bar. Hand off to /experiments or /customer-discovery. Grades: E0 opinion · E1 told story of past behaviour · E2 observed behaviour/artifact · E3 commitment (time, intro, next step) · E4 money.
  • Next action: one thing to do this week.

Research

Web-search only for current, external facts: competitor offers and ads, CPMs and CPCs, platform ad rules, consumer and subscription law, market data. Cite as [FACT — url, date]. Never web-search for "what the books say"; the playbooks are the method. No source → [UNKNOWN] plus a research step. The books are thin on SEO, modern paid social, AI search, B2B demand generation and India-specific distribution (vernacular, WhatsApp, cash on delivery): say so and research rather than guess.

Hand-offs

  • Before: /problem-discovery, /customer-discovery, /jtbd, /where-to-play, /value-proposition-canvas.
  • Elsewhere: positioning, price and PLG /gtm; names and brand messaging /branding; leads to closed deals /sales; running a push /outreach-sprint.
  • After: /experiments, /facts-assumptions-unknowns, /business-model-canvas, /startup-scorecard. Lost: /founder-stack. Learning: /learn.

Go deeper (optional)

If the business-books MCP is connected, search_library / read_passage give the original passages behind a playbook. Not required.

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.