agentleFS
UsermuseUsermuse/em-plugin/skills/ideal-customer-profile/SKILL.md

ideal-customer-profile

Skill0 starsChanged 3 months agoMITView on GitHub

Build an Ideal Customer Profile from your real won-and-happy customers — firmographics, behaviors, jobs-to-be-done, and pains drawn from actual conversations with the accounts that bought and stayed. Use when the user says 'define our ICP', 'who is our ideal customer', 'who are our best customers', 'who should we sell to', 'build a customer profile', or 'who retains and expands'. Trigger terms: ICP, ideal customer profile, best customers, target customer, who to sell to, firmographics, JTBD, disqualification criteria. Not for picking a single first market — use beachhead-segment for that.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 7 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.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 6 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 6 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 6 projects that use this

  • +6 more from skytiger6724

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Required — one parallel batch of searches: Verify the product (Rule 1), then fire in a single parallel batch:

    line 29
  2. Distinctive:

    If only a handful of happy accounts exist, say so — the ICP is a hypothesis from N accounts, not a law.

    line 78
  3. Very specific:

    After saving, offer: "Position for this ICP?" (/evermuse:positioning-and-messaging), "Plan the launch?" (/evermuse:gtm-strategy), or …

    line 81

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

Ideal Customer Profile

Define the customer most likely to find value, retain, and expand — but build it from real won-and-happy customers in the corpus, not an idealized composite. The Evermuse twist: you identify the accounts that actually bought and stayed, read their conversations for why, and let the patterns across them define the ICP with quotes attached.

Step 0 — Relevance & availability

Confirm this is an ICP / targeting task and Evermuse is connected. If the tools aren't present, produce a framework-only ICP labeled ⚠ ungrounded — Evermuse not connected and tell the user to authorize the MCP. See ${CLAUDE_PLUGIN_ROOT}/skills/using-evermuse/SKILL.md Step 0.

Evermuse Grounding (required)

Follow ${CLAUDE_PLUGIN_ROOT}/skills/using-evermuse/SKILL.md.

Required — one parallel batch of searches. Verify the product (Rule 1), then fire in a single parallel batch:

  • 3–4 evidence searches, each worded from a different angle (limit up to 50). Evidence comes back rich and varied — expect large, useful result sets.
  • one guidance search and one context search (limit up to 50). These are usually sparse or empty; run them anyway and note when they're thin.

Read each response's digest — it reports how many more results exist. Use judgment on whether a query is worth pulling deeper (raise limit toward the 100 max and/or page with next_offset to avoid repeats), weighing payload size, remaining context, task complexity, and the value of the data. For deep pulls, consider spawning sub-agents — instruct them to return every citation with the same metadata the tools return (url, who_said_it, meeting_name, created_at) so you can still cite.

Optional — considered use. Once grounded, reach for the other tools only when they add value: a quote-angled search for verbatim voice, read_source for a single deep dive, inline citations (references/citations.md), and add_source to save the deliverable. Sources, citations, and saving are optional — not required.

Instructions

You are defining the ICP for $ARGUMENTS. Where the source method reaches for "PMF survey data / win-loss / interviews," use the Evermuse corpus of real customer conversations as the primary source — start from accounts that actually won and stayed, and read their words.

Step 1 — Find the real best customers

Segment the accounts in the corpus by value signal: bought and renewed, expanded, fastest time-to-value, most enthusiastic, best reference potential. These accounts — not a hypothetical persona — are the raw material.

Step 2 — Extract the four ICP components (each cited)

For the best-customer cohort, synthesize patterns and attach quotes:

  • Firmographics — company size, industry/vertical, geography, buyer's role/department, company stage. Note the actual common denominators, including non-obvious outliers that are high-value.
  • Behaviors — how they discovered the product, evaluation process and timeline, who was in the buying committee, adoption speed and breadth, support needs. (Discovery channel is gold for GTM — cite it.)
  • Jobs to Be Done — the functional job, plus emotional ("how they want to feel") and social dimensions, and their own success metrics — in their words.
  • Needs & pains — the before-state frustrations and the after-state they got, quantified where the evidence allows (cost/time of the problem).

Step 3 — Sharpen the edges

  • Ideal-of-the-ideal: the tightest sub-pattern that predicts the best outcomes.
  • Disqualification criteria: who is NOT a fit — grounded in accounts that looked similar but churned, stalled, or never activated. This is where evidence prevents an over-broad ICP.
  • GTM implications: what the ICP means for messaging and channels (hand off to /evermuse:positioning-and-messaging or /evermuse:gtm-strategy).

Deliverable format

# Ideal Customer Profile — [product]

**Built from:** [N] won-and-happy accounts in the corpus ([examples]).

**Firmographics:** [size / industry / geo / role / stage] — pattern evidenced by [`1`](URL).
**Behaviors:** discovered via [channel] [`2`](URL); buying committee [who]; adoption [speed].
**Jobs to Be Done:** functional — [job]; emotional — [feeling]; social — [status]. > "[JTBD quote]" — [attribution] [`3`](URL)
**Top pains → outcomes:**
| Before (pain) | After (outcome they got) | Evidence |
|---|---|---|
| [pain] | [outcome] | > "[quote]" — [attribution] [`4`](URL) |

**Ideal-of-the-ideal:** [tightest high-value sub-pattern].
**Disqualification (NOT a fit):** [traits] — grounded in [churned/stalled accounts] [`5`](URL).
**GTM implications:** [messaging + channel notes].

Honesty when evidence is thin

If only a handful of happy accounts exist, say so — the ICP is a hypothesis from N accounts, not a law. Flag where more won-customer conversations would sharpen it.

Save & hand off

After saving, offer: "Position for this ICP?" (/evermuse:positioning-and-messaging), "Plan the launch?" (/evermuse:gtm-strategy), or "Narrow to a first beachhead?" (/evermuse:beachhead-segment).


Further reading

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.