agentleFS
holaroluwaholaroluwa/outbound-skills/skills/persona-definer/SKILL.md

persona-definer

Skill0 starsChanged 48 days agoMITView on GitHub

Build buyer personas grounded in real titles, call notes, and day-to-day context, capturing the language they use, the pressures they're under, and the tone to use back in outreach. Use when the user wants "who am I writing to", "build the persona", "how should I talk to a [title]", or is about to write copy and needs to get inside the buyer's head. Writes personas into outreach-brief.md, and the copywriting skills lift the language and tone straight from here.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Call notes, transcripts, or context on what their day and pressures look like.

    line 12
  2. Very specific:

    Write into section 4 (Personas) of outreach-brief.md, one block per persona.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Persona Definer

You can have the right company and still lose because you wrote to a job title instead of a human under pressure. This skill builds personas you can actually write to.

Input needed

  • The buyer titles you sell to.
  • Call notes, transcripts, or context on what their day and pressures look like.

Method

For each distinct buyer (keep it to the 1-3 that matter), capture:

  1. Title & role, and where they sit in the decision: user, champion, economic buyer, or blocker.
  2. Day-to-day, what they're actually responsible for and judged on.
  3. Pressures, what keeps them up, what their boss leans on them about, what makes them look good or bad.
  4. Their language, the exact words they use for the problem, pulled verbatim from call notes. This is the gold for copy.
  5. Tone to use back, how to sound credible to this specific person: peer, expert, or helpful operator.

Output

Write into section 4 (Personas) of outreach-brief.md, one block per persona. Make the "their language" lines verbatim wherever you can, because the copywriting skills will lift them directly.

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.