launch-metrics

Set up measurement and tracking for product launches, run post-launch retros with data, and build a launch analytics system. Use this skill whenever someone asks to track a launch, set up UTM parameters, measure launch performance, run a launch retro, analyze launch results, or build a dashboard for a product release. Also trigger for "how do we know if the launch worked," "what should we track for this launch," "set up UTMs for the announcement," or any request about measuring or evaluating a product launch. Covers pre-launch tracking setup, UTM conventions, per-tier KPIs, benchmark expectations, and retro frameworks.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is a well-structured, actionable measurement guide with concrete conventions, tables, and benchmarks. Its weaknesses are mild motivational verbosity and a monolithic single-file structure that does not progressively disclose detail into separate reference files.

Suggestions

Tighten or remove motivational framing (e.g., "Without consistent measurement, launches are guesswork. With it, each launch informs the next.") and other prose to improve token efficiency.

Move the large benchmark-expectations and per-tier KPI tables into a separate reference file (e.g. BENCHMARKS.md) and link to it from SKILL.md, keeping the main file as a concise overview.

Add an explicit pre-launch verification checkpoint (e.g., confirm all UTM links and analytics events fire correctly before launch day) as a concrete validation step in the pre-launch setup workflow.

Dimension	Reasoning	Score
Conciseness	Mostly information-dense (UTM conventions, KPI tables, benchmark bands) without explaining concepts Claude already knows, but contains motivational framing ("Without consistent measurement, launches are guesswork") and prose paragraphs that could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance: UTM parameter conventions with example URLs and rules, an instrumented-events table, per-tier KPI tables with where-to-track, numeric weak/solid/strong benchmarks, and a launch-history spreadsheet template with column headers.	3 / 3
Workflow Clarity	Clear sequence (pre-launch setup → launch-day monitoring → post-launch retro → launch history) with sequenced sub-steps and checklists (retro data to pull → questions → output); no destructive/batch operations requiring validate-fix-retry loops are present.	3 / 3
Progressive Disclosure	Well-organized single-file document with no nested references, but it is monolithic rather than an overview pointing to one-level-deep detail files; the benchmark and KPI tables could plausibly live in separate reference files, and no external bundle files exist to offload detail.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is strong across all dimensions: it lists concrete actions, provides natural trigger phrasing with quoted user questions, explicitly answers both what and when, and is clearly scoped to launch measurement. Voice is correctly third person with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("set up measurement and tracking," "run post-launch retros with data," "build a launch analytics system," "set up UTM parameters," "build a dashboard"), matching the anchor for enumerating several specific actions rather than only naming a domain.	3 / 3
Completeness	Explicitly states what the skill does and includes an explicit "Use this skill whenever..." plus "Also trigger for..." clause with concrete triggers, clearly answering both what and when.	3 / 3
Trigger Term Quality	Covers natural phrasings users would say ("track a launch," "set up UTMs," "run a launch retro," "build a dashboard") plus quoted real questions ("how do we know if the launch worked," "what should we track for this launch"), giving broad natural-keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to product-launch measurement with distinct triggers (UTMs, launch retro, launch analytics), occupying a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.