Agent skill

Audience Research

by social-media-skills in social-media-skills/skills

A skill your agent uses to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically.

MITAuto-check passedMarketing & SEO

Install Audience Research

skills CLI
$ npx skills add social-media-skills/skills --skill audience-research -a claude-code

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

GitHub CLI
$ gh skill install social-media-skills/skills audience-research --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/social-media-skills/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/audience-research .claude/skills/audience-research && 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-research
GitHub stars
134
Token cost
~1.8k tokens
SKILL.md length
874 words
Files
6 (incl. references)
Skills in repo
106
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically.

  • Works in 6 steps: Read the foundation first → Gather evidence (don't invent) → Define sharp segments (1–3), and buyer… → …
  • Usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically
  • SKILL.md covers When to use this, Step 0 — Read the foundation…, Step 1 — Gather evidence… and Step 2 — Define sharp segments…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audience Research is an agent skill from social-media-skills/skills. Use to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically. Run when the user says "who's my audience," "audience research," "target audience," "build a persona," "customer profile," "ideal customer profile" / "ICP," "who am I talking to," "understand my followers," or before content work that needs more audience depth than the brand-profile sketch. Reads brand-profile first and goes deeper: jobs-to-be-done, pains…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/audience-template.md` and `references/examples.md`).

It sits in Marketing & SEO, covering Market research and Content strategy. It works with Reddit. The repository describes itself as: 106 social media skills for AI agents - strategy, writing, video, design, platform growth, publishing, and analytics. Works with Claude, Cursor, OpenClaw, Hermes & 40+ agents. The licence is MIT.

When your agent uses it

  • Usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically
  • Says whos my audience
  • Audience research
  • Target audience

Example prompts

  • “s my audience,”
  • “audience research,”
  • “target audience,”
  • “/audience-research”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read the foundation first
  2. Gather evidence (don't invent)
  3. Define sharp segments (1–3), and buyer vs follower
  4. Capture the content-relevant dimensions
  5. Build the language bank
  6. Write the artifact

What it can do on your machine

Read from SKILL.md and the folder at commit 6e30eeb. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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 Research loads about 1.8k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 196 tokens; SKILL.md has 874 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~196
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

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 social-media-skills/skills at commit 6e30eeb, republished under its MIT licence (© social-media-skills). 874 words, ~1,805 tokens.

Download SKILL.mdSave it as .claude/skills/audience-research/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
audience-research
description
Use to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically. Run when the user says "who's my audience," "audience research," "target audience," "build a persona," "customer profile," "ideal customer profile" / "ICP," "who am I talking to," "understand my followers," or before content work that needs more audience depth than the brand-profile sketch. Reads brand-profile first and goes deeper: jobs-to-be-done, pains, objections, and the audience's ACTUAL language (voice-of-customer), grounded in real sources where possible — never demographic theater. Produces an audience.md that content-pillars, batch-content-plan, and the content skills read. Works for any business.
metadata.version
1.0.0
license
MIT

Audience Research

Knowing the audience deeply is the highest-leverage input to good content. You can have perfect voice and clean mechanics and still get ignored if the content doesn't speak to what the audience actually wants, in words they actually use. This skill builds that understanding — and writes it down so every other skill can use it.

It goes deeper than the audience sketch in brand-profile. Two ideas drive it:

  1. Jobs-to-be-done beat demographics. "35-year-old marketing manager, urban, likes coffee" tells you nothing about what to post. "Wants to stop feeling stupid in budget meetings" tells you everything. Capture what the audience is trying to do, not what census box they tick.
  2. Mirror their language, not your jargon. The single biggest lever in copy is using the audience's own words for their problem. So this skill collects the voice of the customer — real phrases from real sources — and builds a language bank the content skills draw from.

When to use this

  • After brand-profile, when content needs to land harder and the audience sketch isn't enough.
  • Before content-pillars or a big batch-content-plan (audience pains feed both).
  • When the user isn't sure who they're really talking to, or content keeps missing.

When NOT to use it: if a current audience.md exists, load it, summarize it, and move on unless the user wants to revisit.

Step 0 — Read the foundation first

Load brand-profile.md. It has the positioning, the audience sketch, and the POV. This skill expands that sketch into something operational. If there's no brand profile, run it first.

Step 1 — Gather evidence (don't invent)

The difference between research and guessing is evidence. Mine the audience's real words and problems from whatever sources are available (see references/voice-of-customer.md):

  • The brand's and competitors' reviews; social comments and replies.
  • Reddit / forums / communities where the audience actually talks (to act on subreddit findings → reddit-marketing).
  • Support tickets, FAQs, sales-call notes, DMs — the friction and objections, verbatim.
  • Search queries / "people also ask" — how they phrase what they want.

Use what the user provides; if the agent can access public sources, mine those too. Where evidence is thin, flag the gap and mark assumptions as hypotheses to validate — never fabricate audience language or pains.

Step 2 — Define sharp segments (1–3), and buyer vs follower

Pick the 1–3 segments that matter most — not "everyone." For each, separate two roles when they differ (especially in B2B):

  • Buyer — who decides/pays.
  • Follower — who actually follows, shares, and champions on social.

They're often different people with different needs; content usually leads with the follower. See references/jobs-to-be-done.md.

Step 3 — Capture the content-relevant dimensions

For each segment, capture only what changes how you'd create content:

  • Jobs-to-be-done — functional, emotional, and social jobs.
  • Pains (what blocks the job) and desires (the outcome they want).
  • What they already believe — so content can meet or challenge it.
  • Objections — why they hesitate; great content answers these pre-emptively.
  • Where they are — platforms + mindset on each.
  • Who/what they follow and what content they engage with.
  • Sophistication level — beginner vs expert (changes vocabulary and depth).

Demographics only if they genuinely change the content (e.g., region for a local business).

Show full SKILL.md (359 more words)Show less

Step 4 — Build the language bank

From the evidence, collect the audience's actual phrases — how they describe the problem, the desired outcome, and their objections — in their words, not paraphrased into marketing-speak. This bank is what makes copy feel like it gets them. See references/voice-of-customer.md.

Step 5 — Write the artifact

Produce audience.md using references/audience-template.md. Flag the primary segment and the core transformation (before → after). Summarize back and invite edits. Content skills read this on every task.

Quality bar — self-check

  • Is it built on jobs-to-be-done and real language, not demographic theater?
  • Is the language bank made of the audience's actual words, grounded in sources (or honestly flagged as assumption)?
  • Are there 1–3 sharp segments, each usable — not "everyone"?
  • Is buyer vs follower separated where they differ?
  • Does every captured dimension actually change how you'd write?
  • Could a writer who's never met this audience picture a real person and write to them?

If a field wouldn't change a single post, cut it. If you couldn't source a claim, flag it.

Edge cases

  • No data / no access → research what public sources you can; otherwise build a structured hypothesis from the brand profile and clearly label it as to-be-validated. Don't present guesses as findings.
  • B2B buyer ≠ user/follower → capture both; note which content targets which.
  • Multiple distinct audiences (e.g., nonprofit: beneficiaries + donors) → separate segments with different jobs and language.
  • Niche / technical audience → sophistication and insider language matter most; get the jargon right (or right to avoid).
  • "Everyone is my audience" → push for the one segment that moves the business most now; build for them first.
  • Aspirational audience (who they want vs who they have) → note both; don't write to a fantasy audience that isn't there yet without saying so.
  • brand-profile — read first; supplies the audience sketch and positioning.
  • content-pillars — audience pains/jobs become content pillars.
  • batch-content-plan, the content skills — use segments, pains, and the language bank.
  • voice-builder — the brand's voice (distinct from the audience's language captured here).

References

  • references/jobs-to-be-done.md — the JTBD lens, pains/desires/objections, why it beats personas.
  • references/voice-of-customer.md — mining real sources for the audience's language (the core).
  • references/audience-template.md — the audience.md output schema.
  • references/examples.md — audience profiles across business types vs the useless generic persona.

© social-media-skills, 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 (references) in skills/audience-research of social-media-skills/skills.

  • SKILL.md
  • evals/evals.json
  • references/audience-template.md
  • references/examples.md
  • references/jobs-to-be-done.md
  • references/voice-of-customer.md

Open the folder on GitHubat commit 6e30eeb

Compare with similar skills

Audience Research 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 Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audience Research this skillsocial-media-skills/skills134—~1.8kAutomated safety check: PassMIT
Content Opportunity Briefunifapi-agent/agents589—~2.3kAutomated safety check: PassMIT
Customer ResearchNexus-JPF/note-companion8706 repos~3.2kAutomated safety check: PassMIT
Customer Researchunifapi-agent/agents589—~2.1kAutomated safety check: PassMIT
Reddit Competitor Analysis API Skillbrowser-act/skills6.1k1 repos~1.7kAutomated safety check: PassMIT
Blog StrategyAgriciDaniel/claude-blog2.3k—~4.4kAutomated safety check: PassMIT

Similar skills

  • Content Opportunity Brief

    unifapi-agent/agents

    When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand.

    589 GitHub stars~2.3k tokensUpdated 1 mo ago
    Writing & ContentAuto-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
  • Customer Research

    unifapi-agent/agents

    When the user wants to research customers from public communities, or synthesize customer language, pains, and objections.

    589 GitHub stars~2.1k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • This skill helps users extract structured data from Reddit posts and comments via BrowserAct API.

    6.1k GitHub starsUsed in 1 repo~1.7k tokens
    Marketing & SEOAuto-check passed
  • Blog Strategy

    AgriciDaniel/claude-blog

    Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…

    2.3k GitHub stars~4.4k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • Reddit Research

    lignertys/reddit-research-skills

    Researches what people say on Reddit through semantic search on reddapi.dev: pain points, product validation, competitor research and subreddit trends.

    14 GitHub stars~3.8k tokensUpdated 26 days ago
    Marketing & SEOAuto-check: warnings

More from social-media-skills/skills

All 106 skills in this repo
  • AI Image Editing

    social-media-skills/skills

    The AI image-editing router — inpainting/object removal, background removal, upscaling, outpainting, old-photo restoration, and retouch, routed task-first to the right engine.

    134 GitHub stars~2.1k tokensUpdated 9 days ago
    Auto-check passed
  • AI Music And Sound

    social-media-skills/skills

    The AI music + sound-design skill for social -- original/licensed audio beds and sound design for Reels/TikToks/Shorts/videos.

    134 GitHub stars~1.9k tokensUpdated 9 days ago
    Auto-check passed
  • AI Search Optimization

    social-media-skills/skills

    A skill your agent uses to get a brand and its content CITED and RECOMMENDED by AI answer engines — the GEO (Generative Engine Optimization) / AI-search-visibility skill.

    134 GitHub stars~2k tokensUpdated 9 days ago
    Auto-check passed
  • AI Video

    social-media-skills/skills

    The model-agnostic AI-video router and brief — the counterpart to image-prompt.

    134 GitHub stars~1.3k tokensUpdated 9 days ago
    Auto-check passed
  • AI Voiceover

    social-media-skills/skills

    The AI narration / voiceover mini-skill (ElevenLabs-led). An agent skill from social-media-skills/skills.

    134 GitHub stars~1.1k tokensUpdated 9 days ago
    Auto-check passed
  • Analytics And Reporting

    social-media-skills/skills

    Social media analytics and reporting — read native platform data honestly and turn it into next actions.

    134 GitHub stars~1.4k tokensUpdated 9 days ago
    Auto-check passed

Works with

Questions about Audience Research

What does Audience Research do?

A skill your agent uses to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically. Audience Research is an agent skill from social-media-skills/skills. Use to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically.

When should I use Audience Research?

Audience Research fits situations like: usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically; says whos my audience; audience research; target audience.

How do I install Audience Research in Claude Code?

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

How do I install Audience Research in Codex?

Run `npx skills add social-media-skills/skills --skill audience-research -a codex`. Or copy the skill folder (skills/audience-research in social-media-skills/skills) into .agents/skills/audience-research in your project. Codex loads it when a task matches its description.

Can I use Audience Research 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 social-media-skills/skills --skill audience-research -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-research, .gemini/skills/audience-research, .github/skills/audience-research and .opencode/skills/audience-research in your project.

What does Audience Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Audience Research is instructions for the agent only.

Does Audience Research 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 Research 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 Research use?

Audience Research is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audience Research use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.

What are the alternatives to Audience Research?

Skills that share tags, products or a category with Audience Research: Content Opportunity Brief (unifapi-agent/agents, 589 stars), Customer Research (Nexus-JPF/note-companion, 870 stars), Customer Research (unifapi-agent/agents, 589 stars) and Reddit Competitor Analysis API Skill (browser-act/skills, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audience Research?

social-media-skills (a GitHub organization) maintains it in social-media-skills/skills, which has 134 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on October 1, 2026.

Source: social-media-skills/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.