BC go-to-market-playbook
You're two weeks from launch and still can't say, in one sentence, who this is for and why they'd switch. That's not a copywriting problem — it's a missing GTM spine. This reusable template forces positioning, ICP, and channel choice into place before you spend a dollar, for B2B or B2C. What's inside: • Positioning canvas — define your category, differentiator, and value prop • ICP worksheet — identify and prioritize your ideal customer profiles • Messaging framework — headlines, elevator pitches, and objection handling • Channel-market fit matrix — match distribution channels to your buyer journey • Competitive battle cards — positioning against the alternatives buyers already know A fill-in template, not a lecture — refined across 150+ startup consultations. 🇨🇳 GTM 策略模板 — 定位画布+ICP+渠道-市场匹配+竞品对比卡，B2B/B2C 通用，发布前把打法钉死。 🇯🇵 GTM戦略テンプレート — ポジショニング、ICP、チャネル選定、競合バトルカード。B2B/B2C両対応。 🇰🇷 GTM 전략 템플릿 — 포지셔닝, ICP, 채널 선택, 경쟁 배틀카드. B2B/B2C 겸용. Triggers: "go to market" | "GTM" | "GTM strategy" | "go-to-market plan" | "positioning" | "product positioning" | "ICP" | "ideal customer profile" | "messaging framework" | "channel strategy" | "launch strategy" | "competitive analysis" | "市场进入" | "定位" | "GTM 战略" | "市場投入" | "포지셔닝"
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1233 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 892 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1232: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 48.