agentleFS
mypip-iomypip-io/skills/readiness-check/SKILL.md

readiness-check

Skill1 starsChanged 25 days agoMITView on GitHub

Reads a public post, comment or profile and judges whether that person is ready to buy what a founder sells now, might be later, or isn't a customer at all, with a plain reason. Use when a founder pastes a Reddit post, tweet, LinkedIn post or forum thread and asks \"is this person worth contacting\", wants to spot buying signals, or needs to decide who to talk to first.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    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:

    When they posted it, if you know.

    line 16
  2. Distinctive:

    Decide, and say why: Put them in one of three groups:

    line 28
  3. Distinctive:

    Never fill gaps with guesses.

    line 47

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

Readiness check

Anyone can find people who might buy. The useful question is who's ready now.

In most markets only about 5 in 100 people are ready to buy at any given moment. The other 95 aren't wrong for you. They just aren't looking yet. A founder with a few minutes a day should spend them on the five, and this skill helps you tell them apart from what people actually wrote.

What you need

  1. A short description of who your customer is and what you sell. The who-buys-from-me skill gives you one.
  2. The person's post, comment or bio, with a link.
  3. When they posted it, if you know.

Steps

  1. Read what they said, not what the thread is about. A comment under a post about a problem isn't the same as having the problem. Judge the person by their own words.
  2. Ask whether they'd buy this or sell it. Plenty of people talking about a topic are consultants, agencies or founders with a competing product. They can be great to know. They aren't customers.
  3. Look for movement. Readiness shows up as someone doing something about the problem: asking for a recommendation, comparing options, saying they've tried something that didn't work, mentioning a deadline or a budget. Someone who only fits the description, without any of that, is a "later".
  4. Check the date. A post from this week is a conversation you can join. A post from last year tells you about the kind of person they are, not what they need today.
  5. Decide, and say why. Put them in one of three groups:
    • Ready now: right person, doing something about the problem, recently.
    • Later: right person, no sign they're looking yet. Worth following, not messaging.
    • Not a customer: wrong person, or on the selling side.

Output

Verdict: <ready now / later / not a customer>
Why: <one or two sentences, based on what they wrote>
What they're doing about it: <their own action, if any>
Worth responding to: <the part of their post you could genuinely help with>
Next step: <reply in public / follow / skip>

For several people, list the "ready now" group first and keep it short. If nobody is ready today, say so.

Rules

  • Never fill gaps with guesses. If the post doesn't say, you don't know.
  • "Ready now" is a reason to be helpful, not a reason to pitch.
  • Be honest about the ratio. Most people you check won't be ready, and that's what makes the ones who are worth your time.

Example

You sell: a tool that helps solo founders find their first customers.

Post: "Shipped my habit tracker three weeks ago. Product Hunt gave me 40 upvotes and 3 downloads. Is it the product or am I just bad at marketing? What did you do to get your first 100 users?"

Verdict: ready now
Why: A solo founder who launched recently, tried one thing that didn't work, and is asking how others found users.
What they're doing about it: asking for approaches after a launch that didn't bring users
Worth responding to: the gap between upvotes and downloads
Next step: reply in public with something useful

With MyPip (coming)

Finding the people who are ready, across thousands of communities, is MyPip's whole job. When the MyPip MCP is live, this skill will be able to start from the people MyPip found for you today.

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.