CtrlK
BlogDocsLog inGet started
Tessl Logo

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/下一发布时刻

67

Quality

83%

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

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

The body is a well-structured, actionable planning workflow with clear sequencing and well-signaled cross-skill references. Its main weakness is redundancy — the same handoff/scope statements recur across several sections — which drags conciseness to the midpoint.

Suggestions

Consolidate the repeated scope/handoff carve-outs (content-amplifier, launch-tier-planner, launch-registry) into a single Scope Guard or Reference Materials block instead of restating them in the instructions, save-results, and next-best-skill sections.

Tighten the relaunch-legitimacy guidance in step 5 with a concrete checklist (new capability / new audience / stage change) rather than a prose definition, to lift actionability toward the top anchor.

Consider moving the detailed Skill Contract reads/writes/promotes lists into a bundled reference file so the SKILL.md body stays a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

It assumes Claude's competence (no basic-concept padding) and is mostly efficient, but the same scope carve-outs (content-amplifier, launch-tier-planner, launch-registry) are restated across the scope guard, instructions, reference materials, and next-best-skill sections, which could be tightened.

3 / 5

Actionability

Provides concrete guidance — explicit file paths, `operation: propose` requests to `registry-events.py`, a tier routing rule (major/medium/minor), and ready-to-use Quick Start prompts — with only minor abstract spots like the relaunch-legitimacy definition.

4 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit checkpoints (NEEDS_INPUT on missing calendar records, "ask before writing", a "Done when" contract, a claims-hygiene step); as a non-destructive planning skill it avoids the destructive/batch cap, with only minor validation gaps keeping it off the top anchor.

4 / 5

Progressive Disclosure

Well-organized into Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, and Next Best Skill, with clearly signaled one-level-deep references; no bundle files exist to split advanced detail into, which keeps it just below the top anchor.

4 / 5

Total

15

/

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: third-person voice, concrete capabilities, natural trigger phrasing, and explicit negative scope that distinguishes it from sibling skills. Every dimension lands at the top anchor with no verbosity penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — a T+1→T+30 momentum plan, a launch-moment calendar (milestone / shipped-loop / badge), 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 spacing — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both "what" ("produces a T+1→T+30 momentum plan ...") and "when" ("Use when the user asks to ...") with concrete trigger phrases, satisfying the top anchor.

5 / 5

Trigger Term Quality

Embeds natural phrases a user would actually say ("keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", "is this update worth a relaunch") alongside synonyms like relaunch and changelog-as-GTM, plus Chinese aliases.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (post-launch momentum scheduling) and explicitly carves out adjacent skills ("Not for the 30-day content-reuse map ... use content-amplifier; not for planning the next launch end to end — use launch-tier-planner"), minimizing conflict 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.

Validation12 / 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
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.