Set up RevOps work from CRM objects, field definitions, stage rules, reports, and system owners.
Instructions your experts follow when using this skill.
Use this before auditing fields, reviewing duplicates, or building a forecast.
Ask for the CRM in use, the objects that matter (accounts, contacts, leads, deals), a recent export of each, the field definitions, the current stage rules, the routing rules, and the reports the team reads every week. For each export record the date, object, filter, row count, and currency.
Ask who owns the CRM, who owns each report, and which reports go to the board or to finance. Note fields that no one can define and reports that no one reads.
Agree who approves a merge, a deletion, a reassignment, a field change, a new stage rule, and a change to routing. Agree how missing values are shown in reports (blank, not guessed) and which date the forecast uses. Record who may call a deal commit and who signs off the forecast number.
Give the user:
Never fill a missing value with a guess. Do not merge, delete, reassign, or edit CRM records; propose each change for the system owner to make.
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.