CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestration skill body with an exceptionally clear sequenced workflow, explicit validation gates, and well-annotated one-level references. Its main weaknesses are repetition of the registry/scope-guard disclaimers across three sections and delegation of the registry-proposal mechanics to out-of-bundle references without any inline example.

Suggestions

State the registry propose rule once (e.g., in Save Results or the Skill Contract Writes bullet) and have the intro scope guard simply link to launch-registry, cutting the near-verbatim repetitions that cost conciseness.

Show one concrete minimal example of the `operation: propose` request to `registry-events.py` (or the `memory/events/launches.ndjson` payload shape) inline so step 7 is executable without chasing external references.

Collapse the triple-listing of roi-calculator / report-generator / performance-analyzer (intro scope guard, Reference Materials, Next Best Skill) into a single Scope/Reference section, and verify that `scripts/connectors/*.py` paths actually resolve from the deployed bundle.

DimensionReasoningScore

Conciseness

Mostly efficient — no explanations of concepts Claude already knows and dense, information-bearing prose — but noticeably repetitive: the registry disclaimer ("never writes memory/launch-registry/ records directly... submits the outcome snapshot... via an authorized operation: propose request to registry-events.py") appears nearly verbatim in the intro, the Writes bullet, and Save Results, and roi-calculator / report-generator / performance-analyzer / momentum-planner are each re-linked three times (intro scope guard, Reference Materials, Next Best Skill). This is more than the minor trimmable instances of the level-4 anchor, fitting "could be tightened" at level 3.

3 / 5

Actionability

For an instruction-only skill the guidance is largely executable: 8 concrete numbered steps, exact save paths (`memory/launch/launch-retro-analyzer/YYYY-MM-DD-<launch-or-product>-retro.md`), explicit output schemas (truth vs reference columns, Measured/User-provided/Estimated labels, `retro_status: PROVISIONAL | NEEDS_INPUT`), and ready-to-use Quick Start prompts. Minor gaps keep it below 5: the registry proposal is never shown concretely — the actual `registry-events.py` invocation or ndjson payload shape is delegated entirely to references — so the reader cannot execute step 7 without chasing them.

4 / 5

Workflow Clarity

The 8-step sequence has explicit validation checkpoints and feedback loops: step 1 gates on complete receipts ("Missing or partial receipts keep the launch join open and the retro provisional"), step 5 emits provisional recommendations when evidence is incomplete, step 7 notes registry acceptance "does not manufacture missing receipts", and step 8 blocks progression until the retro is terminal, otherwise routing the missing-receipt list back to launch-monitor. The "Done when" contract and explicit PROVISIONAL/NEEDS_INPUT statuses act as a checklist, matching the level-5 anchor; the writes are proposals gated on user confirmation, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Good structure: a Reference Materials section signals each external file with a one-line purpose annotation, references are one level deep, and sibling-skill hand-offs are clearly labeled. It falls short of the level-5 anchor: no bundle files exist in this skill's directory, yet the body references paths like `scripts/connectors/hn.py` and deeply relative repo paths (`../../../references/...`, `../../../CONNECTORS.md`) that live outside the bundle, so navigation depends on unverifiable external structure; the connector details in Data Sources could also live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete deliverables, explicit quoted triggers, and explicit hand-off boundaries that deconflict sibling skills. The only gap is modest synonym coverage of natural trigger phrasing, which is already strong thanks to the quoted scenarios and bilingual keywords.

DimensionReasoningScore

Specificity

The description lists multiple concrete, specific outputs — "a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column... 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", and "an outcome snapshot submitted to the launch registry" — comprehensively covering the skill's actions, matching the level-5 anchor. Not a 4 because coverage is complete rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: the "what" is the enumerated D1/W1/M1 retrospective deliverables, and the "when" opens with "Use when the user asks to..." followed by three quoted scenarios — mirroring the level-5 anchor example. Not a 4 because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Quoted natural phrases a user would actually say — "run a launch retro / post-mortem", "compare launch results vs targets by channel", "decide what to keep or kill for the next launch" — plus a bilingual keyword tail (发布复盘/渠道归因). It falls short of the level-5 anchor's comprehensive synonym coverage: common variants like "retrospective", "lessons learned", or "what worked / what didn't" are absent, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (post-launch retro) with distinct triggers and explicit negative boundaries — "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" — which actively routes away from adjacent skills, giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 29 suspicious

Warning

referenced_paths_exist

Referenced path issues: 4 missing, 4 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/prove/launch-retro-analyzer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.