BF launch-retro-analyzer
Use when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported numbers as reference, every figure labeled Measured / User-provided / Estimated), a 5-Whys chain on the single largest miss, keep / kill / change decisions per channel, 3-5 actionable learnings for the next launch, and an outcome snapshot submitted to the launch registry. Not for return math (CPA / ROI) — use roi-calculator; not for the stakeholder-facing report writeup — use report-generator; not for a metric deep-dive — use performance-analyzer. 发布复盘/渠道归因/5-Whys/keep-kill
produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported…
As a process F 47/100 · Will not run — References files that are not bundled: ../../../references/ramp-benchmark.md, ../../mobilize/launch-readiness-auditor/SKILL.md, ../../../influencer/report/roi-calculator/SKILL.md
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 800 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../../../references/ramp-benchmark.md - warning
missing-refreference to a missing file: ../../mobilize/launch-readiness-auditor/SKILL.md - warning
missing-refreference to a missing file: ../../../influencer/report/roi-calculator/SKILL.md - warning
missing-refreference to a missing file: ../../../influencer/report/report-generator/SKILL.md - warning
missing-refreference to a missing file: ../../../influencer/report/performance-analyzer/SKILL.md - warning
missing-refreference to a missing file: ../launch-monitor/SKILL.md - warning
missing-refreference to a missing file: ../launch-feedback-synthesizer/SKILL.md - warning
missing-refreference to a missing file: ../../../protocol/launch-registry/SKILL.md - warning
missing-refreference to a missing file: ../momentum-planner/SKILL.md - warning
missing-refreference to a missing file: ../../../references/skill-contract.md - warning
missing-refreference to a missing file: ../../../CONNECTORS.md - warning
missing-refreference to a missing file: ../../../SECURITY.md - warning
missing-refreference to a missing file: ../../research/launch-tier-planner/SKILL.md - warning
missing-refreference to a missing file: ../../../protocol/memory-management/SKILL.md - warning
missing-refreference to a missing file: scripts/connectors/hn.py - warning
missing-refreference to a missing file: scripts/connectors/producthunt.py - warning
missing-refreference to a missing file: scripts/connectors/appstore.py - warning
missing-refreference to a missing file: scripts/connectors/gdelt.py - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 47/100
- 0Tools and files. 18 referenced file(s) missing: ../../../references/ramp-benchmark.md, ../../mobilize/launch-readiness-auditor/SKILL.md, ../../../influencer/report/roi-calculator/SKILL.md
- 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
- 40Result and completion. Does not say what the result is
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 25 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2758 tokens
- 100Running it twice. No mutating operations
- 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 800: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.