Skip to content
Agentmart
Submit a tool

audience-research

Build detailed buyer personas and audience profiles from research.

Skill by MoizIbnYousaf

IndexedMIT★ 32
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moizibnyousaf-audience-research

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.

Use cases: writing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/audience-research

What's inside

Skill name
audience-research
Description
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
License
MIT
Instructions
395 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • jtbd-framework.md · references/

SKILL.md (first lines)

> **Note:** Examples below use fictional brands (Acme, Lumi, Helm). Replace with your own brand context.

# /audience-research -- Know Who You're Talking To

Every marketing skill gets better when you know your audience. Generic copy
happens when you write for "everyone." Specific copy that converts happens
when you write for a real person with real problems.

This skill builds that audience profile. It's the foundation  -  8 of 11 content
skills read `audience.md` to shape their output. Running this first makes
everything downstream sharper.

No SaaS tools needed. Systematic research plus web search.

---


## On Activation

1. Check if `brand/` directory exists in the project root.
2. If it does, read available files: `voice-profile.md`, `positioning.md`, `audience.md`, `competitors.md`, `creative-kit.md`, `stack.md`, `learnings.md`.
3. Apply any loaded brand context to enhance output quality  -  skip questions the user has already answered.
4. If `brand/` does not exist, proceed without it  -  this skill works standalone.

---

## Iteration Detection

Before starting, check whether `./brand/audience.md` already exists.

### If audience.md EXISTS --> Update Mode

Do not start from scratch. Instead:

1. Read the existing audience profile.
2. Present a summary of current personas:
   ```
   EXISTING AUDIENCE PROFILE
   Last updated {date} by /audience-research

   Personas:
   ├── {Persona 1 name}    {one-liner}
   ├── {Persona 2 name}    {one-liner}
   └── Primary: {primary persona name}

   Watering holes: {N} mapped

   ──────────────────────────────────────────────

   What would you like to do?

   1. Refine existing personas with fresh research
   2. Add a new persona segment
   3. Deep-dive into watering holes
   4. Full rebuild from scratch
   ```

3. Process the user's choice:
   - Option 1 --> Re-run research for existing personas, update with new data
   - Option 2 --> Identify the new segment, build persona, merge into existing file
   - Option 3 --> Focus on community mining for existing personas
   - Option 4 --> Full process from scratch

4. Before overwriting, show what changed and ask for confirmation.

### If audience.md DOES NOT EXIST --> Full Research Mode

Proceed to the full process below.

---

## The core job

Build a complete picture of who buys this product, why they buy it, where they
hang out, and what language they use. The output is structured enough for other
skills to parse but human enough to be useful for strategy.

---

## Approach selection

Choose based on what's available:

### Quick Profile (L0  -  zero context)

When no brand files exist and minimal information is provided. Ask 5 key questions:

1. **What does your product do?** (one sentence)
2. **Who currently uses it?** (or who do you want to use it?)
3. **What problem does it solve?** (the pain before, the relief after)
4. **What alternatives exist?** (what would they do without you?)
5. **What's the price point?** (free, $10/mo, $500/mo, enterprise?)

From these 5 answers, generate a working persona. It won't be perfect but it
gives every downstream skill something to work with.

### Persona Build (L1-L2  -  some context)

When you have basic product info or existing brand files. Systematic persona
construction using demographics, psychographics, and jobs-to-be-done.

### Community Mining (L3-L4  -  full research)

When `exa-search` / Exa MCP or web search is available. Deep research into where the audience
lives online, what language they use, what they complain about, and what they
aspire to.

---

## The audience research process

### Step 1: Identify the transformation

Same as positioning  -  start with the outcome, not the product.

- What does the customer's life look like BEFORE? (the pain state)
- What does it look like AFTER? (the desired state)
- What's the gap between those two states?

From MoizIbnYousaf/marketing-cli, MIT.

More from MoizIbnYousaf/marketing-cli

Signals

Stars
32
Forks
5
Open issues
1
Last commit (this folder)
Jul 18, 2026 (3 months ago)
Last release
Aug 16, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MoizIbnYousaf

Cite this page

audience-research skill. Agent Mart. https://agentmart.dev/skills/moizibnyousaf-audience-research (last updated 2026-10-24)