audience-profile
Build detailed buyer personas. Use when: demographics, psychographics, behaviors, JTBD, content preferences.
What this skill does
# /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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.