agentleFS
spiralcrew-ouspiralcrew-ou/profilespider-agent-skills/persona-classification/SKILL.md

persona-classification

Skill9 starsChanged 5 months agoMITView on GitHub

Classifies professional profiles into buyer, influencer, user, decision-maker, founder, recruiter, or other personas. Use when the user provides profiles and wants persona labels with evidence and confidence. Must not infer sensitive personal attributes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Do not infer health, religion, ethnicity, sexual orientation, political affiliation, or other sensitive personal attributes.

    line 47
  2. Distinctive:

    Use the supplied persona definitions when given.

    line 50

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

Persona Classification

Purpose

Classify professional profiles into buyer, influencer, user, decision-maker, and other personas.

When to use this skill

  • Routing contacts to the right messaging
  • Mapping buying committees in target accounts
  • Prioritizing decision-makers in a list
  • Tailoring sequences by persona

When not to use this skill

  • Profiles lack a role or professional context
  • You need sensitive personal attributes (never infer these)
  • You want per-account scoring (use Qualification)

Required inputs

  • Professional profiles with roles

Optional inputs

  • Your persona definitions
  • The product or deal context

Rules

  1. Classify from professional role evidence only.
  2. Do not infer health, religion, ethnicity, sexual orientation, political affiliation, or other sensitive personal attributes.
  3. Provide an alternate persona when signal is mixed.
  4. Report confidence and missing information.
  5. Use the supplied persona definitions when given.

Process

  1. Parse each profile and its role.
  2. Match role evidence to persona definitions.
  3. Assign a primary and alternate persona.
  4. Estimate the decision-process role.
  5. Report confidence and gaps.

Output format

Return one record per profile with the following fields:

  • persona
  • likely_role_in_decision_process
  • evidence
  • confidence
  • alternate_persona
  • missing_information

Validation

  • Confirm no sensitive attributes were used.
  • Confirm each persona cites role evidence.
  • Confirm low-confidence rows are flagged.

Limitations

  • Titles do not always reflect real authority.
  • Personas are interpretive and should be verified in conversation.

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.