Use when the user first says who they sell to, hands you companies or an export, or wants names added to or cut from the prospect list.
Instructions your experts follow when using this skill.
Every prospecting step after this one reads these rows, so build the list narrow and right before you build it big.
If all you have is an ideal customer, seed 10 to 20 fitting companies from the public web and cite the page that surfaced each one. A paste, a HubSpot or Apollo export, or a Google Sheet starts with a readback: name the columns you see and how each maps to the row below, before you edit anything.
One person per row. Other skills read these exact names:
Statuses go new, enriched, drafted, approved, sent, replied, meeting, qualified; no or on hold closes a row. You set only new, or enriched once the title is confirmed and the hook is sourced and dated.
Mark each company strong, maybe, or weak with a one-line reason in notes, naming the trigger when there is one: funding, a hiring burst, a new buying leader, a switch off a tool you replace. Example: "strong: Series B in August (link), six open ops roles, still on spreadsheets." Fit with no trigger is a maybe; a trigger never makes a poor fit strong. Keep weak companies off unless they ask.
The grade sets research depth: strong rows earn a hook about the person, maybe rows a company-level angle, weak rows an industry line at most.
Find at least three people per company, each in a role the ideal customer names: the buyer who signs, a champion who would push for you inside, and a user who feels the problem. Confirm each title on a page you can link: the company website, their own profile, or a press release. An unconfirmed title stays empty and holds the row at new. Name any empty seat rather than stretch a nearby title.
Never build an email from a naming pattern or guess a profile URL from a name. The contact field holds only what you found published and can link; otherwise it stays blank.
Collapse duplicates by person and company first, then by company URL. Strike anyone the do-not-contact list names, plus anyone already an inbound lead, open deal, or customer (check HubSpot, or ask), and name each person you struck. Show ten rows with fit reasons, let them edit once, then save. Nothing sends or reaches the CRM without their yes. Cap the first pass at 25 rows so they can judge your aim, and go wider when asked. Later adds and drops land in the same turn.
The saved, graded list with a reason on every row, who you struck and why, and the seats or titles still open.
An export you cannot read cleanly: ask for a paste. No public team page: the row stays new and you ask them who holds the seat. Under ten matches: show them and name the constraint to loosen. No do-not-contact list given: ask once before saving.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.