본문으로 건너뛰기
cccskills
무료GitHub에 공개

gtm-performance-diagnostics

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

GTM performance diagnostics

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.

Fix the period and the funnel first

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.

The GTM metric set

Define each once with its formula and denominator, then score it against target red, yellow, or green:

  • Pipeline created in the period, and coverage: open qualified pipeline over the remaining target — 3x is the usual flag line, 2x the alarm, adjusted to the historical win rate.
  • Win rate: won over won plus lost, by segment and by source, on closed deals only. Open deals are not a denominator.
  • Deal velocity: opportunities times win rate times average deal size, over the average cycle in days — and deal age against that cycle.
  • Stage conversion: each stage into the next, against last period.
  • Activation and adoption for product-led or free-tier motions.
  • Expansion and retention: net revenue retention where the cohort supports it, and logo churn where it does not.
  • Forecast accuracy: last period's commit against what actually closed.
  • Revenue influenced by each motion, with the attribution rule stated.

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.

Rank the movers and decompose them

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.

Call a thin sample what it is

Fewer than about 30 observations behind a rate means the move sits inside the noise — say so, and never manufacture a trend from it.

The forecast read

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.

What you hand back

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.

Fallbacks

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고