agentleFS
teachskillofskills-aiteachskillofskills-ai/DigitalMarketingPro-techshu/skills/audience-profile/SKILL.md

audience-profile

Skill0 starsChanged 9 months agoMITView on GitHub

Build a named, narrative buyer persona document — demographic snapshot, psychographic drivers, jobs-to-be-done, day-in-the-life scenario, buyer journey map, objections with counter-messaging, and content/channel preferences — for the 2-4 personas a brand actually needs. Triggers on \"/digital-marketing-pro:audience-profile\", \"create a buyer persona\", \"profile our target customer\", \"who is our ideal customer\", \"map the buyer journey for this segment\". Reads the brand profile, guidelines, and any customer data supplied (surveys, CRM exports, analytics demographics); run by the marketing-strategist agent. For the deeper research module — segmentation, anti-personas, buying committees — see /digital-marketing-pro:audience-intelligence.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document the buyer journey: trigger events, research process, evaluation criteria, decision influencers

    line 32

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

/digital-marketing-pro:audience-profile

Purpose

Build a rich, actionable buyer persona that goes beyond basic demographics. Captures psychographic drivers, behavioral patterns, jobs-to-be-done, objections, and content consumption preferences to inform all marketing activities.

Input Required

The user must provide (or will be prompted for):

  • Product/service: What the brand offers
  • Customer type: B2B buyer, B2C consumer, or both
  • Existing data: Any customer research, survey data, analytics demographics, CRM data, or interview insights
  • Number of personas: How many distinct personas to create (recommend 2-4)
  • Hypothesis: Who the user thinks their ideal customer is (starting point)

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Gather inputs through structured questions if data is limited
  3. Build demographic profile: age range, role/title, company size (B2B), income range, geography, education
  4. Develop psychographic profile: values, motivations, fears, aspirations, identity markers
  5. Map behavioral patterns: where they spend time online, content formats preferred, purchase behavior, decision-making process
  6. Define jobs-to-be-done: functional, emotional, and social jobs the product helps accomplish
  7. Identify objections and barriers to purchase with counter-messaging
  8. Document the buyer journey: trigger events, research process, evaluation criteria, decision influencers
  9. Specify content preferences: platforms, formats, tone, topics they engage with
  10. Give the persona a name and narrative summary for team alignment

Output

A structured buyer persona document containing:

  • Persona name and one-paragraph narrative
  • Demographic snapshot
  • Psychographic profile with motivations and values
  • Jobs-to-be-done framework (functional, emotional, social)
  • Day-in-the-life scenario
  • Buyer journey map with touchpoints and decision criteria
  • Objections and counter-messaging guide
  • Content and channel preferences
  • Messaging do's and don'ts for this persona

Agents Used

  • marketing-strategist — Persona development, JTBD framework, buyer journey mapping, audience segmentation

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.