agentleFS
mypip-iomypip-io/skills/find-one-person/SKILL.md

find-one-person

Skill1 starsChanged 26 days agoMITView on GitHub

Finds the first real person who best fits a founder's ideal customer, then the next few like them, and plans how to start a conversation with each. Use when a founder has zero customers or users, asks how to find early adopters, how to get their first users, \"where do I even start\", or wants to find beta users for something they built.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't look for a market. Look for one person.

    line 8
  2. Very specific:

    Search where they talk, not where they're listed: Search each phrase on the places they actually spend time, using that site's own search …

    line 26
  3. Distinctive:

    Find four more like them: Look at who replied to their post, who they follow, which communities they post in, and run your phrases there.

    line 30
  4. Distinctive:

    Never pretend to be a customer, and never fake a shared experience.

    line 58
  5. Distinctive:

    If you can't find a single person describing the problem anywhere, that is important information.

    line 59
  6. Distinctive:

    No magic numbers. Don't aim for "40 conversations".

    line 60

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

Find one person

Don't look for a market. Look for one person.

At zero customers, "who's my audience?" is too big a question to act on. "Who is the one person on the internet who most clearly needs this today?" is small enough to answer before lunch. Find that person, start a real conversation, and the next ones are easier, because people like them follow each other, post in the same places, and use the same words.

Early adopters are not a demographic. They are specific people who have the problem now, know they have it, and are already trying to fix it with something worse than what you built.

What you need

  1. Who the customer is, ideally from the who-buys-from-me skill. At minimum: what you built and who you built it for.
  2. The words customers use for the problem. Guess if you must, then correct them as you search.
  3. Where the founder can realistically look: Reddit, X, LinkedIn, Indie Hackers, Hacker News, Discord servers, niche forums, GitHub, Product Hunt comments.

Steps

  1. Describe the exemplar. In two sentences, the person who would love this most. Not a segment. One person, with a situation.
  2. Write search phrases in their words. What would that person post the week the problem bites? "I launched and got zero signups", "how do you find your first customers", "built a tool for X, no idea how to market it". Write eight to twelve, mixing complaints, questions and requests for recommendations.
  3. Search where they talk, not where they're listed. Search each phrase on the places they actually spend time, using that site's own search plus Google with site:. Prefer posts from the last few weeks. A recent complaint is worth ten old ones.
  4. Pick the one. Choose the single person whose own words show the problem most clearly and most recently. Check they're a buyer, not someone selling a similar service or giving advice about it.
  5. Find four more like them. Look at who replied to their post, who they follow, which communities they post in, and run your phrases there.
  6. Plan the first touch for each. Start where they are. Reply usefully to what they posted, connect, or follow and engage before any direct message. Every honest public interaction also builds your own presence on that platform. Save cold email for later: it's the hardest place to start.

Output

The exemplar: <two sentences>

Search phrases (their words):
- "<phrase>"

The one:
Who: <handle and platform>
What they said: <paraphrase plus link>
Why them: <fit, recency, and evidence they'd buy rather than sell>
First move: <the specific reply or interaction>

Four more like them:
1. <handle> · <platform> · <what they said> · <first move>

Next places to look: <communities these five share>

Rules

  • Recent beats impressive. Someone with forty followers who posted the problem yesterday beats a well-known name who mentioned it last year.
  • Be respectful. Don't dig through someone's life to surprise them; it reads as surveillance.
  • Never pretend to be a customer, and never fake a shared experience.
  • If you can't find a single person describing the problem anywhere, that is important information. Either the words are wrong or the problem is.
  • No magic numbers. Don't aim for "40 conversations". Aim to start one good one today and do it again tomorrow.

Why one person works

Speaking to one specific person reaches more people than speaking to everyone. When your first message, your post or your homepage is written for one clear person, others who share most of their situation recognise themselves in it. A vague message gives nobody anything to hold onto.

With MyPip (coming)

This is the job MyPip does every day. When the MyPip MCP is live, this skill will be able to pull the people MyPip found for you today, already checked for fit and recency, instead of you searching by hand.

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.