agentleFS
mypip-iomypip-io/skills/who-buys-from-me/SKILL.md

who-buys-from-me

Skill1 starsChanged 27 days agoMITView on GitHub

Works out who should buy from a founder, starting from their website or a short description of the product. Produces an ideal customer profile built on how people think and behave instead of job titles, plus a one-line test for who fits. Use when a founder asks \"who is my customer\", \"what's my ICP\", \"who should I sell to\", or has built something and doesn't know who it's for.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Use the customer's words, not the founder's category.

    line 53
  2. Distinctive:

    Don't invent customers or evidence.

    line 54
  3. Distinctive:

    If the profile could describe half the internet, it isn't finished.

    line 55
  4. Distinctive:

    Treat it as a first rough block of marble.

    line 56
  5. Distinctive:

    When the MyPip MCP is live, this skill will be able to start from the profile MyPip built from your website and from who has actually said …

    line 64

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

Who buys from me

Turn a website into the person most likely to say yes to it today.

Most ideal customer profile templates ask for thirty fields: job title, industry, headcount, revenue band. Many of those templates are written by companies that sell contact data, and the fields happen to match the filters they sell. A founder with no customers doesn't need a database query. They need to know which human being would hear their one-line pitch and say "yes, I want that" without asking a single follow-up question.

That is the definition this skill works to: your ideal customer is the person who says yes to your one-line pitch with no further questions.

What you need

Any one of these is enough to start.

  1. The founder's website, or a paragraph describing the product.
  2. Why they built it, and who they had in mind at the time.
  3. Anyone who has already used it, paid for it, or got excited about it.

Steps

  1. Start from the person the founder built it for. Every product was built with someone in mind, even if nobody wrote it down. Often it's the founder, or someone they watched struggle. "I have no customers, so I can't know my customer" isn't true. The customer was there when the idea was.
  2. Describe them as a person. How they think, what frustrates them, what they've already tried, where they spend time online, who they follow, how they talk about the problem. Job title and company size can break a tie, nothing more. When Plastic Bank looked at who actually signed up, the job titles in its plan predicted nothing. Shared personality traits predicted almost everyone.
  3. Narrow until it feels uncomfortable. "SaaS founders" is a market. "Solo founders who shipped in the last three months, have fewer than ten users, and post their progress in public" is a person. Narrow wins because people who match most of the description recognise themselves in it, and the rest aspire to it. Speak to one person and more people hear you.
  4. Find the five in a hundred. Most of any market isn't ready to buy right now. Describe what the ready few are doing this week that the others aren't.
  5. Write the one-line test. One sentence a stranger would understand. Picture three people from your description hearing it. If any of them would ask "what do you mean?", the sentence or the description needs work.

Output

The person: <a short paragraph, specific enough to feel uncomfortable>

The one-line test: <the pitch>. The right person says yes without asking anything else.

How they describe the problem, in their words:
- "<phrase>"

What the ready few are doing this week: <one or two sentences>

Who looks right but isn't: <one or two sentences>

Where to look for the first one: <two or three places>

Rules

  • Use the customer's words, not the founder's category.
  • Don't invent customers or evidence. If you don't know, say so and ask.
  • If the profile could describe half the internet, it isn't finished.
  • Treat it as a first rough block of marble. Real conversations and real customers do the carving. Rewrite it as soon as they show you who actually says yes.

A quick check

How fast people get it is the tell. With the right person and the right words, conversations are quick and simple. If every conversation needs a long explanation, it's the wrong person or the wrong message.

With MyPip (coming)

When the MyPip MCP is live, this skill will be able to start from the profile MyPip built from your website and from who has actually said yes to your introductions.

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.