Use when the user asks how GTM is doing, hands over funnel or pipeline numbers, or wants KPIs and targets defined: the scorecard with movers, causes, and the forecast read.
Instructions your experts follow when using this skill.
Use this when the user asks how go-to-market is doing, hands over funnel or pipeline numbers, or wants GTM metrics and targets defined. This is the commercial engine read — how leads become pipeline, pipeline becomes revenue, and revenue retains — not the operations scorecard. Start from this period's and last period's numbers (HubSpot, Amplitude for activation and adoption, a sheet, or a pasted export), the targets, and the currency.
Say the days you are scoring and the days you compare against out loud, and never compare a partial period to a full one. Then name the funnel stages the numbers actually use — lead, MQL, SAL, SQL, opportunity, won — and which source covers which stage. A stage with no source gets named, never dropped quietly.
Define each once with its formula and denominator, then score it against target red, yellow, or green:
Money rounds to whole units, rates to one decimal. When a rate's denominator is zero, report N/A with the absolute counts instead of a percentage.
Biggest miss first, biggest gain next. Break each move into its funnel drivers — volume in at the top, conversion between stages, deal size, cycle time — and tie it to something visible: a segment that shifted, a campaign that landed, a competitor that moved, a rep who left. A move you cannot explain gets one line saying so and the one thing you would need.
Fewer than about 30 observations behind a rate means the move sits inside the noise — say so, and never manufacture a trend from it.
Beside the scorecard: Commit, Best-Case, and Pipeline grades with the evidence behind each, the hygiene flags (past close date, stale next step, amount and stage mismatch, single-threaded enterprise deals), and the backward funnel math from the target to the pipeline it needs at the current conversion rates.
The scorecard table, the top movers with their drivers, the forecast read, what to look at next, and the two or three interventions worth doing, each with the metric that justifies it, an owner, and a date. Save the scorecard dated and write the period's figures to the metrics history — a sheet the team edits when Sheets is connected. You diagnose and recommend; CRM hygiene stays with sales ops and finance reporting with finance.
No targets means you propose them from history and mark every target UNKNOWN. One source only means you build the read for that stage and name what is missing. Label each line FACT, INFERENCE, or UNKNOWN, and never invent a rate, a count, or a cause.
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.