CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

momentum-planner

Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, dense planning skill: the 9-step workflow is sequenced with user-agreement and NEEDS_INPUT checkpoints, artifacts and scripts are named precisely, and nothing explains concepts Claude already knows. It falls short of top marks on mild redundancy (repeated propose-request phrasing and triple-stated disambiguation), the absence of any worked example of the output artifacts, and references that all point outside the bundle rather than to resolvable bundled files.

Suggestions

State the 'authorized operation: propose request to registry-events.py' write convention once (e.g., in the Skill Contract) and refer back to it from steps 7–8 and Save Results, and merge the Scope guard / Reference Materials / Next Best Skill disambiguation into one section — the same neighbor skills are re-linked up to six times.

Add one worked example: a sample dated calendar row (with its milestone/shipped-loop/badge classification and tier) and a sample launches.ndjson propose payload, so the expected output is copy-paste ready rather than described in prose.

Add an explicit final validation pass before the handoff summary — re-check that no content-distribution slots are on the calendar, every milestone number is marked [needs source], and each Tier-1 spacing check is either sourced from calendar.md or marked NEEDS_INPUT.

DimensionReasoningScore

Conciseness

The body teaches no concepts Claude already knows and every section carries operational content, but the phrase 'via an authorized `operation: propose` request to `registry-events.py`' appears verbatim four times, and the Scope guard, Reference Materials, and Next Best Skill sections restate the same neighbor-skill disambiguation (content-amplifier linked ~5 times, launch-registry ~6). This is efficient with minor instances that could be trimmed — anchor 4 — rather than anchor 3, since there is no concept-explanation filler, and not anchor 5 given the real redundancy.

4 / 5

Actionability

Guidance is concrete: exact output paths (memory/launch/momentum-planner/YYYY-MM-DD-<launch-slug>-momentum-plan.md, memory/events/launches.ndjson), a named script invocation (registry-events.py, operation: propose), explicit classification taxonomies and a tier mapping, and three copy-paste Quick Start prompts. It stays at anchor 4 rather than 5 because the output artifacts are described in prose but never shown — there is no worked example of a calendar entry or a propose-request payload, leaving minor gaps in copy-paste readiness.

4 / 5

Workflow Clarity

Nine steps are clearly sequenced (confirm launch → read decay → build calendar → set cadence → judge relaunch → route spike → book next moment → claims hygiene → label and close) with explicit checkpoints: 'If state is absent, ask rather than assuming', 'If no calendar record exists, mark the spacing check NEEDS_INPUT', 'Agree the tier ... with the user', ask-before-save, and a 'Done when' checklist. It matches anchor 4 rather than 5 because there is no explicit feedback loop that re-validates the assembled plan (e.g., confirming no content-distribution slots landed on the calendar or every claim is marked [needs source]) before the handoff summary is emitted.

4 / 5

Progressive Disclosure

Section structure is good (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) and all references are one level deep and annotated with their purpose. Scored against the actual bundle — no references/, scripts/, or assets/ directories exist, and every referenced path (../../../references/ramp-benchmark.md, ../../../CONNECTORS.md, ../../research/launch-tier-planner/SKILL.md) escapes the bundle and cannot be resolved — this is anchor 4 ('good structure; references mostly clear; minor organization gaps') rather than anchor 5, whose well-signaled references would actually resolve, and the same neighbor-skill navigation is repeated across three sections.

4 / 5

Total

16

/

20

Passed

Description

100%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.

The description is exemplary: it states what the skill produces in five concrete terms, gives three verbatim user trigger phrases, and explicitly disambiguates against adjacent skills. Its only weakness is length — the trailing non-English keyword string duplicates terms (changelog-as-GTM, relaunch) already present, which is mild keyword padding rather than a coverage problem.

DimensionReasoningScore

Specificity

The description names five concrete outputs — 'a launch-moment calendar (milestone / shipped-loop / badge moments only)', 'announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only)', 'a relaunch legitimacy call', 'spike-to-owned handoff briefs', and 'the next Tier-1 moment with launch-stacking spacing' — with an explicit tier mapping. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it exceeds anchor 4 because no capability of the skill is left unlisted.

5 / 5

Completeness

It explicitly answers 'when' with three concrete quoted trigger phrases ('Use when the user asks to...') and 'what' with a full enumerated output list ('produces a T+1→T+30 momentum plan — ...'). Both halves are explicit with concrete triggers, matching the top anchor rather than anchor 4 where the 'when' could be more specific.

5 / 5

Trigger Term Quality

It quotes the exact phrases a user would say — "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", "is this update worth a relaunch" — and covers synonyms (changelog / release-notes; relaunch / update) plus a second-language keyword tail. This is comprehensive natural-term coverage, not anchor 4, since no obvious user phrasing variant is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is narrow (post-launch T+1→T+30 moment scheduling) and it negatively scopes its two nearest neighbors: 'Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner'. Clear distinct triggers with minimal conflict risk, matching anchor 5 rather than anchor 4's 'minor overlap risk'.

5 / 5

Total

20

/

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: 32 suspicious

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/prove/momentum-planner/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.