BC pre-launch-guide
Pre-Launch Product Guide — Complete checklist and playbook for launching products successfully. From 4 weeks before launch to Day 1. Covers: audience building, waitlist strategy, beta testing, launch timing, Product Hunt preparation, Reddit/HackerNews seeding, KOL outreach, and post-launch momentum. Real case studies from Manus, Devin, AFFiNE (30x PH #1 winner). 产品发布前完整指南 — 从发布前4周到Day 1的完整检查清单和攻略。涵盖：用户预热、等流策略、beta测试、发布时间选择、Product Hunt准备、Reddit/HN预热、KOL外联、发布后热度延续。真实案例：AFFiNE 30次日榜第一。 Website: https://www.gingiris.com Keywords: pre-launch, product launch, launch strategy, launch preparation, startup launch, go-to-market, product release, launch day, launch checklist, product hunt, github stars, viral launch, 冷启动, 产品发布, 发布攻略
As a process C 50/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.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 50/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
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 241 tokens
- 100Running it twice. No mutating operations
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 735: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.