mcpbeat Sign in

Audience Profile Skill for Claude

Build detailed buyer personas. Use when: demographics, psychographics, behaviors, JTBD, content preferences.

753 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
694
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill audience-profile

The instruction itself

6 sections, as written by the author

/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

  • 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.
  • Gather inputs through structured questions if data is limited
  • Build demographic profile: age range, role/title, company size (B2B), income range, geography, education
  • Develop psychographic profile: values, motivations, fears, aspirations, identity markers
  • Map behavioral patterns: where they spend time online, content formats preferred, purchase behavior, decision-making process
  • Define jobs-to-be-done: functional, emotional, and social jobs the product helps accomplish
  • Identify objections and barriers to purchase with counter-messaging
  • Document the buyer journey: trigger events, research process, evaluation criteria, decision influencers
  • 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

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take indranilbanerjee/audience-profile from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.