agentleFS
moses607moses607/socialforge/skills/audience-bullseye/SKILL.md

audience-bullseye

Skill3 starsChanged 4 months agoMITView on GitHub

Builds a hyper-precise audience persona from psychographics and jobs-to-be-done — the painful problem, secret desire, fear/objection, the conversation already running in their head, the aspirational identity, where they gather, and the exact words they use — not age/gender/income demographics. Outputs a bullseye persona plus resonant content angles and hooks derived directly from those pains and desires. Use when the user asks about their audience, persona, ICP, "who am I talking to", or targeting. Trigger on any audience-definition or targeting intent. Works with any capable model.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every objection is a content piece and every desire is a hook — the persona is a backlog, not a poster.

    line 55
  2. Distinctive:

    If it doesn't make one person feel seen, it won't make anyone act.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audience Bullseye

Demographics tell you who can buy; psychographics tell you why they scroll, save, and share. "Women 25-40" have nothing in common on a feed — but "anyone who feels like a fraud in meetings they're qualified to lead" will stop, feel seen, and follow. The whole game is finding the one specific person and the raw sentence running through their head, then writing to that sentence. Content that tries to speak to everyone lands on no one. Go so narrow it feels risky; the paradox of reach is that the narrowest, most specific post travels furthest because it earns the share ("this is literally me").

Method: excavate the psychographic core

Work these seven in order — each feeds the next. Answer in the audience's own words, not marketer-speak.

  1. The painful problem. The concrete, daily friction they'd pay to end. Get to the felt symptom, not the category ("I rewrite the same email six times" beats "communication struggles").
  2. The secret desire. What they want but won't say out loud — status, ease, revenge, being right, being chosen. This is the engine; hooks that touch it convert.
  3. The fear / objection. What stops them acting — "I'll look stupid", "I've tried and failed", "it's too late for me". Every objection is a future piece of content.
  4. The conversation in their head. The exact sentence they're already thinking before they see your post. You don't start a new conversation — you enter this one mid-stream.
  5. The aspirational identity. Who they're trying to become. People don't buy outcomes, they buy a new self-image. Name the identity they'd upgrade to.
  6. Where they hang out. Specific subreddits, creators they follow, hashtags, group chats, physical places. This is where you validate language and study competitors.
  7. Their exact language. Steal real phrasing from comments, reviews, and DMs. The persona's vocabulary becomes your hook vocabulary.

Method: mine language from the wild

  1. Pull 20-30 real phrases from where they gather — top comments, 1-3 star reviews (gold: the gap between expectation and reality), Reddit threads, DMs, and search autocomplete.
  2. Cluster them into pains, desires, and objections. Note the emotional temperature — the phrases with heat (frustration, longing, sarcasm) are your best raw hook material.
  3. Convert each cluster into an angle: pain → "the real reason you [problem]"; desire → "what [aspirational identity] does differently"; objection → "you're not [feared thing], you're [reframe]".

Output template

=== BULLSEYE PERSONA ===
The one person: <a single named archetype in one vivid sentence>
Painful problem: <felt, daily symptom in their words>
Secret desire: <the unspoken want>
Fear / objection: <what stops them>
Conversation in their head: "<the exact sentence they're already thinking>"
Aspirational identity: <who they're becoming>
Where they gather: <specific platforms / communities / creators>
Their words: <8-12 stolen real phrases>

RESONANT ANGLES (from pains/desires):
1. <angle> → hook: "<hook>"
2. <angle> → hook: "<hook>"
3. <angle> → hook: "<hook>"
4. <angle> → hook: "<hook>"
5. <angle> → hook: "<hook>"
=== END PERSONA ===

Platform variants

  • TikTok/Reels: the "conversation in their head" IS the first line of the video. Lead with their sentence, not yours.
  • LinkedIn: frame pains around professional identity and status among peers; the fear is usually being seen as behind or replaceable.
  • X: lean on the contrarian objection — the reframe that makes them feel smart for agreeing.
  • Pinterest/Instagram: desire and aspirational identity carry more weight than pain; sell the after-state visually.

Rules

  • One specific person beats a broad segment every time — if the persona could describe 5 million people, it's not done.
  • Steal their exact words; never sanitize audience language into marketer-speak. "Broke and burnt out" is not "financially constrained and fatigued".
  • Every objection is a content piece and every desire is a hook — the persona is a backlog, not a poster.
  • If it doesn't make one person feel seen, it won't make anyone act. Test each angle against a real human you can picture.
  • Psychographics over demographics, always — age and income don't predict a save; a felt problem does.
  • Anchor to a real source (comments, reviews, DMs); a persona invented from imagination inherits your blind spots, not their reality.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.