Agent skill

Audience Intelligence

by indranilbanerjee in indranilbanerjee/digital-marketing-pro

Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle…

MITAuto-check passedProduct & Project Management

Install Audience Intelligence

skills CLI
$ npx skills add indranilbanerjee/digital-marketing-pro --skill audience-intelligence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install indranilbanerjee/digital-marketing-pro audience-intelligence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/audience-intelligence .claude/skills/audience-intelligence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audience-intelligence
GitHub stars
859
Used in
1 other repo
Token cost
~3.8k tokens
SKILL.md length
1,727 words
Files
6
Skills in repo
162
Repo updated
First seen
Licence
MIT

At a glance

Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle…

  • Works in 9 steps: Check session context — The active brand… → If you need the full profile, read:… → Apply brand voice — Formality, energy,… → …
  • /digital-marketing-pro:audience-intelligence
  • SKILL.md covers When to Use This Skill, Brand Context (Auto-Applied), Required Context and Capabilities, plus 5 more sections
  • Calls python

What it does

Audience Intelligence is an agent skill from indranilbanerjee/digital-marketing-pro. Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and lookalike seed specs. Triggers on "/digital-marketing-pro:audience-intelligence", "who are our customers", "build buyer personas", "segment our audience", "run a JTBD analysis". Reads the brand profile, industry benchmarks, and campaign…

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `customer-research-methods.md`, `jtbd-framework.md` and `persona-builder.md`).

It sits in Product & Project Management, covering User stories and Market research. The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.

When your agent uses it

  • /digital-marketing-pro:audience-intelligence
  • Who are our customers
  • Build buyer personas
  • Segment our audience

Example prompts

  • “/digital-marketing-pro:audience-intelligence”
  • “who are our customers”
  • “build buyer personas”
  • “/audience-intelligence”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels…
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before…
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best…
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for…

What it can do on your machine

Read from SKILL.md and the folder at commit 3343924. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audience Intelligence loads about 3.8k tokens when it runs. Until then it costs about 191 tokens; SKILL.md has 1,727 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~191
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 3343924, republished under its MIT licence (© indranilbanerjee). 1,727 words, ~3,804 tokens.

Download SKILL.mdSave it as .claude/skills/audience-intelligence/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
audience-intelligence
description
Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and lookalike seed specs. Triggers on "/digital-marketing-pro:audience-intelligence", "who are our customers", "build buyer personas", "segment our audience", "run a JTBD analysis". Reads the brand profile, industry benchmarks, and campaign history, and works from CRM/survey/analytics data when supplied — or labels hypothesis personas explicitly when data is thin. For a single quick persona document, /digital-marketing-pro:audience-profile is the lighter sibling.

Audience Intelligence

When to Use This Skill

Activate this module when the user's request involves any of the following:

  • Buyer Persona Creation: Building detailed profiles of ideal customers for marketing and product decisions
  • Audience Research: Understanding who a brand's customers or prospects are at a demographic, psychographic, and behavioral level
  • Segmentation Strategy: Dividing an audience into meaningful groups for targeted marketing
  • Jobs-to-Be-Done (JTBD) Analysis: Identifying the functional, social, and emotional jobs customers hire a product to do
  • Psychographic Profiling: Understanding audience values, attitudes, interests, lifestyles, and motivations
  • Anti-Persona Definition: Defining who is NOT the target customer to prevent wasted spend
  • Audience Sizing & TAM Estimation: Estimating the size of addressable audience segments

Trigger phrases: "buyer persona," "target audience," "who are our customers," "customer profile," "segmentation," "audience segments," "Jobs-to-Be-Done," "JTBD," "psychographic," "ideal customer profile," "ICP," "anti-persona," "lookalike audience," "audience research," "buying committee," "customer avatar"

Brand Context (Auto-Applied)

Before producing any marketing output from this module:

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before planning new work
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices."
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for banned words, restricted claims, and mandatory disclaimers; channel-styles.md for channel-specific tone overrides (may differ from base voice); messaging.md for approved key messages, taglines, and positioning language; voice-and-tone.md for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.

Do not ask the user for information that already exists in their brand profile.

Required Context

Before executing audience intelligence work, gather:

  1. Business Description: What does the company sell, to whom, and what problem does it solve?
  2. Existing Customer Data: Any analytics, CRM data, survey results, or customer interviews available
  3. Product/Service Details: Features, pricing, positioning, and key differentiators
  4. Current Audience Assumptions: Who does the team think their customers are today?
  5. Market Context: Industry, competitive landscape, market maturity
  6. Geographic Scope: Local, regional, national, or global audience
  7. Business Model: B2B, B2C, B2B2C, D2C — this fundamentally shapes persona structure
  8. Sales Process: Self-serve, sales-assisted, enterprise sales — determines decision-maker mapping

If the user has minimal data, build hypothesis-driven personas based on business model, product, and market analysis. Label these clearly as hypotheses to be validated.

Capabilities

  • Multi-Dimensional Persona Building: Personas built across six dimensions:
    • Demographic: Age, gender, location, income, education, job title, company size
    • Psychographic: Values, attitudes, lifestyle, personality traits, motivations
    • Behavioral: Purchase patterns, channel preferences, content consumption, decision-making style
    • Need-State: Current pain points, unmet needs, desired outcomes, urgency level
    • Information: Where they research, who they trust, content format preferences, information journey
    • Decision: Decision criteria, objections, influencers, timeline, risk tolerance
  • JTBD Framework: Mapping functional jobs (what they need done), social jobs (how they want to be perceived), and emotional jobs (how they want to feel) with outcome-driven innovation metrics
  • RFM Segmentation: Recency, Frequency, Monetary value analysis for customer base segmentation
  • Behavioral Segmentation: Grouping by usage patterns, engagement levels, and purchase behavior
  • Value-Based Segmentation: Grouping by customer lifetime value and profitability potential
  • Lifecycle Segmentation: Grouping by customer lifecycle stage (prospect, new, active, at-risk, churned, win-back)
  • Lookalike Audience Guidance: Defining seed audience characteristics for platform-based lookalike targeting
  • Anti-Persona Definition: Explicitly defining who should be excluded from targeting to prevent wasted spend and misaligned messaging
  • Buying Committee Mapping: For B2B, mapping all roles involved in purchase decisions with their individual motivations and objections

Process

Primary Workflow: Persona Development & Segmentation

  1. Discovery & Data Collection

    • Gather all available customer data (analytics, CRM exports, survey results, interview transcripts)
    • Review existing marketing materials, landing pages, and ads for implicit audience assumptions
    • Analyze competitor targeting (who are they going after? what messaging do they use?)
    • If no data exists, conduct a market analysis to build hypothesis personas
    • Document the data quality level: data-rich, data-limited, or hypothesis-only
  2. JTBD Analysis

    • Identify the core job the customer is hiring the product to do
    • Map functional jobs: What task needs to be accomplished?
    • Map social jobs: How does the customer want to be perceived by others?
    • Map emotional jobs: How does the customer want to feel?
    • Identify the "struggling moment" — what triggers the search for a solution?
    • Document competing solutions (including non-consumption and manual workarounds)
    • Define desired outcomes and how customers measure success
  3. Persona Construction

    • Build 3-5 primary personas (avoid persona proliferation)
    • For each persona, complete all six dimensions:
      • Demographic profile: Concrete characteristics with ranges, not single points
      • Psychographic profile: Values, beliefs, lifestyle factors that influence purchase decisions
      • Behavioral profile: How they buy, where they spend time, what content they consume
      • Need-state profile: Specific pain points, urgency drivers, and desired outcomes
      • Information profile: Research behavior, trusted sources, content preferences
      • Decision profile: Criteria, objections, influencers, and timeline
    • Give each persona a memorable name and narrative (but avoid stereotyping)
    • Assign estimated segment size and revenue potential
    • Prioritize personas by business impact
  4. Anti-Persona Development

    • Define 1-3 anti-personas: people who may seem like targets but are poor fits
    • Common anti-persona types: price-sensitive bargain hunters (for premium brands), feature-seekers who will never buy (tire kickers), wrong company size or industry
    • Document specific signals that identify anti-personas in your data
    • Create exclusion criteria for ad targeting and lead qualification
  5. Segmentation Strategy

    • Select the segmentation approach based on available data and business needs:
      • RFM: When transaction data is available — score by recency, frequency, monetary value
      • Behavioral: When usage/engagement data exists — group by behavior patterns
      • Value-based: When LTV data is available — prioritize high-value segments
      • Lifecycle: When customer journey stage data exists — customize by stage
      • Needs-based: When qualitative research is available — group by pain point
    • Define segment boundaries and naming conventions
    • Map segments to personas (segments are data-driven groups; personas are the human stories within them)
    • Assign channel and messaging strategies per segment
  6. Activation Planning

    • For each persona/segment, define:
      • Priority channels for reaching them
      • Messaging themes and value propositions that resonate
      • Content types and formats they prefer
      • Lookalike audience seed criteria for paid platforms
      • Lead scoring rules based on persona fit
    • Create a persona-to-campaign mapping guide
    • Build a validation plan to test persona hypotheses with real campaign data
Show full SKILL.md (620 more words)Show less

Reference Files

  • persona-builder.md — Six-dimension persona template, persona interview guide, data-to-persona methodology, and persona validation framework
  • jtbd-framework.md — Jobs-to-Be-Done analysis methodology, job mapping canvas, outcome-driven innovation scoring, and competing solutions analysis
  • segmentation.md — RFM scoring model, behavioral segmentation framework, lifecycle segmentation definitions, and segment-to-action mapping
  • psychographic-profiling.md — Values and attitudes framework, lifestyle analysis, motivation mapping, and psychographic data collection methods
  • customer-research-methods.md — Quantitative and qualitative research methods: survey design, interview techniques, voice-of-customer programs, and synthesis methods with budget guidance

Output Formats

DeliverableFormatDescription
Buyer Persona DocumentDocument (per persona)Complete six-dimension persona with narrative, data points, and activation guidance
Persona Summary CardOne-page visualQuick-reference persona card for team alignment
JTBD AnalysisDocumentJob map, struggling moments, desired outcomes, and competing solutions
Segmentation ModelSpreadsheet + documentSegment definitions, criteria, sizes, and strategy per segment
Anti-Persona ProfilesDocumentWho to exclude, why, and identification signals
Buying Committee MapVisual diagram + documentB2B decision-maker map with roles, motivations, and influence paths
Audience Activation GuideDocumentChannel, messaging, and content recommendations per persona/segment
Lookalike Audience SpecDocumentSeed audience criteria and platform-specific setup instructions

Edge Cases

B2B Buying Committees (Multiple Personas per Deal)
  • Situation: Enterprise B2B purchases involve 6-10 decision-makers with different roles, motivations, and objections
  • Approach: Build individual personas for each buying committee role: Champion (internal advocate), Economic Buyer (controls budget), Technical Evaluator (assesses capabilities), End User (daily user), Legal/Procurement (risk and compliance), Executive Sponsor (strategic alignment). Map influence relationships between roles. Design content and messaging specific to each role's concerns. Create a "buying committee journey" that shows how roles engage at different stages. Note that the Champion persona is usually the most critical — they sell internally on your behalf.
Two-Sided Marketplace Audiences
  • Situation: Platform serves both supply side (sellers, creators, providers) and demand side (buyers, consumers)
  • Approach: Build completely separate persona sets for each side. Map the interdependencies — how does the supply-side experience affect demand-side personas, and vice versa? Identify the "chicken and egg" constraint: which side must be built first? Create cross-side personas that exist on both sides (e.g., a seller who also buys). Design distinct messaging, channels, and value propositions for each side.
Limited Data Environments
  • Situation: Startup or new market entry with no customer data, no CRM, no analytics history
  • Approach: Build hypothesis personas using market research, competitor analysis, industry reports, and founder/team domain knowledge. Label all personas explicitly as "Hypothesis — Version 1" to set expectations. Design a rapid validation plan: run small targeted campaigns to test persona assumptions. Define specific signals that would confirm or invalidate each persona. Plan to iterate personas after 30-60 days of market data. Use JTBD analysis (which can be done through market observation) as the primary framework when demographic data is unavailable.
Global Audiences with Cultural Differences
  • Situation: Audience spans multiple countries, cultures, and languages with fundamentally different values and behaviors
  • Approach: Do NOT create a single global persona. Build regional persona variants that share a core structure but diverge on cultural dimensions: communication style, decision-making process, trust signals, channel preferences, and value hierarchy. Research cultural dimensions (Hofstede framework as a starting point) for key markets. Flag markets where the product positioning may need fundamental reframing, not just translation. Recommend local market validation before scaling campaigns internationally. Be explicit about the limits of cultural generalization — personas are starting points, not stereotypes.
  • Funnel Architect — For mapping personas to funnel stages and designing stage-appropriate touchpoints for each audience segment
  • Content Engine — For creating persona-specific content, messaging, and creative assets
  • Campaign Orchestrator — For targeting personas through campaigns and allocating budget by segment priority
  • Analytics & Insights — For validating persona hypotheses with behavioral data and refining segments over time
  • AEO/GEO Intelligence — For understanding what AI platforms tell your audience about your brand and optimizing for their AI-powered research behavior

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skills/audience-intelligence of indranilbanerjee/digital-marketing-pro.

  • SKILL.md
  • customer-research-methods.md
  • jtbd-framework.md
  • persona-builder.md
  • psychographic-profiling.md
  • segmentation.md

Open the folder on GitHubat commit 3343924

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Audience Intelligence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audience Intelligence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audience Intelligence this skillindranilbanerjee/digital-marketing-pro8591 repos~3.8kAutomated safety check: PassMIT
China Customer Researchlintendo/Axhub-Skills130—~607Automated safety check: PassMIT
09 Customer Insight Globalminhnv0807/ai-business-skills610—~3.6kAutomated safety check: PassMIT
Product Discoverymajiayu000/spellbook287—~3.3kAutomated safety check: PassMIT
09 Insight Khach Hangminhnv0807/ai-business-skills610—~5.5kAutomated safety check: PassMIT
Developer Docs Audience Researchhashgraph-online/awesome-codex-plugins1.3k—~913Automated safety check: PassMIT

Similar skills

  • China Customer Research

    lintendo/Axhub-Skills

    A skill your agent uses when 需要在中国、海外或跨市场场景中开展客户研究、用户研究、VOC、ICP、JTBD、Persona、竞品口碑、购买或流失原因分析,或从访谈、问卷、工单、社区与评论中为需求分析和 PRD 建立客户证据。

    130 GitHub stars~607 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • 09 Customer Insight Global

    minhnv0807/ai-business-skills

    A skill your agent uses when the user needs to understand customers deeply enough to write copy and pick targeting — consumer versus shopper, JTBD, layered persona, internal monologue, pain map…

    610 GitHub stars~3.6k tokensUpdated 27 days ago
    Product & Project ManagementAuto-check passed
  • Product Discovery

    majiayu000/spellbook

    Product discovery and market research expert. An agent skill from majiayu000/spellbook.

    287 GitHub stars~3.3k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • 09 Insight Khach Hang

    minhnv0807/ai-business-skills

    Dung khi can hieu khach hang du sau de viet duoc content va chon duoc tep — persona 3 tang, cau noi noi tam, pain map, objection list va ngan hang ngon ngu khach hang lay tu review va inbox that.

    610 GitHub stars~5.5k tokensUpdated 27 days ago
    Product & Project ManagementAuto-check passed
  • Developer Docs Audience Research

    hashgraph-online/awesome-codex-plugins

    Research developer documentation audiences by mapping user goals, learning objectives, business goals, developer traits, user questions, personas, user stories, journey maps, and friction logs.

    1.3k GitHub stars~913 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Marketing & SEOAuto-check passed

More from indranilbanerjee/digital-marketing-pro

All 162 skills in this repo
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant (absolute vs relative MDE via…

    859 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Aeo Audit

    indranilbanerjee/digital-marketing-pro

    Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with…

    859 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Agent Readiness Audit

    indranilbanerjee/digital-marketing-pro

    Audit whether AI agents and AI crawlers can actually use a site — robots.txt rules per AI crawler token (OpenAI, Anthropic and Perplexity bots, Google-Extended, Applebot-Extended)…

    859 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Backlink Gap

    indranilbanerjee/digital-marketing-pro

    Find referring domains that link to your competitors but not to you, ranked by an outreach-priority score (0.40 DR + 0.25 link-overlap + 0.20 traffic + 0.15 topical relevance) — outputs a four-gate…

    859 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • C2pa Metadata

    indranilbanerjee/digital-marketing-pro

    Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file…

    859 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Audit

    indranilbanerjee/digital-marketing-pro

    Inventory and score everything currently running for a brand across paid search, paid social, email, organic, SEO, AEO/GEO, CRM, and analytics — produces a dated audit document with a 4-tier triage…

    859 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check: notes

Questions about Audience Intelligence

What does Audience Intelligence do?

Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle…. Audience Intelligence is an agent skill from indranilbanerjee/digital-marketing-pro. Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and lookalike seed specs.

When should I use Audience Intelligence?

Audience Intelligence fits situations like: /digital-marketing-pro:audience-intelligence; who are our customers; build buyer personas; segment our audience.

How do I install Audience Intelligence in Claude Code?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill audience-intelligence -a claude-code`. Or copy the skill folder (skills/audience-intelligence in indranilbanerjee/digital-marketing-pro) into .claude/skills/audience-intelligence in your project. Claude Code loads it when a task matches its description.

How do I install Audience Intelligence in Codex?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill audience-intelligence -a codex`. Or copy the skill folder (skills/audience-intelligence in indranilbanerjee/digital-marketing-pro) into .agents/skills/audience-intelligence in your project. Codex loads it when a task matches its description.

Can I use Audience Intelligence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill audience-intelligence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audience-intelligence, .gemini/skills/audience-intelligence, .github/skills/audience-intelligence and .opencode/skills/audience-intelligence in your project.

What does Audience Intelligence need to run?

Going by SKILL.md and its folder, Audience Intelligence needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Audience Intelligence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Audience Intelligence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audience Intelligence use?

Audience Intelligence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audience Intelligence use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Audience Intelligence?

Skills that share tags, products or a category with Audience Intelligence: China Customer Research (lintendo/Axhub-Skills, 130 stars), 09 Customer Insight Global (minhnv0807/ai-business-skills, 610 stars), Product Discovery (majiayu000/spellbook, 287 stars) and 09 Insight Khach Hang (minhnv0807/ai-business-skills, 610 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audience Intelligence?

indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 859 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 4, 2026.

Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.