Use when the user wants the honest read on their book: coverage, forecast, stuck deals, and hygiene.
Instructions your experts follow when using this skill.
Run this when the user wants the honest read on their book. Report from the numbers source only — anything untraceable is UNKNOWN, never estimated.
The CRM view or export they trust, their quota, their commit style, and the deal sheets with qualification state.
Counts by stage, movement since last review, coverage as open pipe over quota — flag under 3x, alarm under 2x — the oldest stuck five with stall ages, and pacing vs goal. Split the read: the pipeline review moves deals (what is stuck, what advanced, owner plus date); the forecast review defends the number (what closes, amount, date, commit/upside/best-case confidence). Monthly, add segment conversion trends; quarterly, re-check the coverage and stage assumptions; a third close-date move or a top-five deal leaving commit triggers an off-cycle review.
Commit, best case, pipeline, or omitted per deal, with the qualification evidence behind each call. Flag commit deals with open must-have letters and best-case deals with no dated next step.
Stale next steps, deals with no activity in 14 days, single-threaded enterprise deals, and stage-to-qualification mismatches. Each flag carries the one fix and its owner.
Draft the CRM next-step updates as text the user can paste. Apply nothing yourself.
The pipeline report with forecast grades and hygiene flags, plus the staged next-step drafts.
No CRM access: review from their export or pasted numbers and say which checks you could not run. No quota on file: pacing is UNKNOWN until they give it.
Reads and drafts only. CRM writes and commit calls wait for your yes.
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.