Menu

Individual skill

research-audience-score-segment-qa

0upvotes

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.

skills/marketing/research-audience-score-segment-qa/SKILL.md

Read pinned source

Source commit df8298140d434a6363de0c265eb6af2e571d97a5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,315
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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);
Back to top