agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/research-audience-score-segment-qa/SKILL.md

research-audience-score-segment-qa

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the research-audience playbook: scores and tiers list rows, groups them into segments with an angle each, runs the pre-handover checks and writes the list files. Run research-audience instead; not for direct use.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about athina-ai/goose-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    no duplicate people or domains.

    line 22
  2. Distinctive:

    all exclusions applied (customers, open deals, ledger, competitors, do-not-contact, own staff).

    line 23
  3. Distinctive:

    every title seen within 90 days.

    line 24
  4. Distinctive:

    If fewer rows pass than asked, deliver what passed and state why (thin universe, no contact routes, heavy exclusions).

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

score-segment-qa

Reads: account table, people rows, signals; ../research-audience/references/fit-and-scoring.md; ../research-audience/references/output-format.md; ../research-audience/references/contacts-and-compliance.md.

Does:

  1. Score: gates already passed; add points by block, each with its cited reason in fit_reason. Tier A/B; C to dropped.csv. Set the value tier (V1/V2/V3) with its evidence for account-based lists; rank by tier and value together.
  2. Segment by angle × signal (e.g. "new leader", "hiring for the pain", "fit, no signal"), 3–6 segments, each with a three-line angle: pain (the situation in the buyer's terms, from the signals), proof (one signed-off claim, verbatim, cleared through the claims-gate skill (../claims-gate/SKILL.md) — or "you'd need proof of <X> first", which the message offers to sign off), ask (one low-friction next step). Never an invented result or number. Then For you per segment: does it fit us (yes/no and why, from our product, pricing and customers); what to send first and to whom (V1 accounts first); then offer, as a closing decision, the messages written for this list (write-outreach reads list.csv and these angles). Don't follow the herd: if every rival pitches this segment the same way, say so and offer a different angle from what buyers say (this playbook's quote bank, research/audience/voc-bank.md). You vs them: accounts where a rival is in use (from job posts naming the tool, case studies, integration pages) — where we're ahead (say it louder), behind, and where everyone sounds the same.
  3. Rank: tier, then score, then warm path.
  4. QA checklist — every item, every run:
    • domain is the current company's live site, not a parent or old brand;
    • no duplicate people or domains; concentration cap held;
    • all exclusions applied (customers, open deals, ledger, competitors, do-not-contact, own staff);
    • every title seen within 90 days; every signal inside its window;
    • email filled only for verified-by-tool rows — every published or pattern-built address is in email_candidate; no verified label without a checker result; pattern-guesses have cited evidence; account-level rows (chains, independents) carry a published route;
    • no banned hook topics; region flags set; no Canadian or AU/NZ pattern-guess left as an email route; no UK-soletrader row has an email or DM route (visit, letter, or phone with a recorded TPS check); EU rows say "check the national rule"; other: rows say "check the local rule";
    • five random rows re-checked by hand against their sources — fix or drop any that fail, and say how many failed.
  5. If fewer rows pass than asked, deliver what passed and state why (thin universe, no contact routes, heavy exclusions). Never pad.

Writes: report.md, list.csv, dropped.csv (tier C included, with reason) in the output format, and segments.csv (segment, name, pain, pain_source_url, proof, ask, default_opener, rows) — the angles write-outreach reads; pain comes from the quote bank, or with no bank from the rows' own signals ("hiring two AP specialists"), labelled so. Ledger rows for everything shown.

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.