CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-monitor

Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar early-warning (Estimated heuristic), PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds against the launch-tier KPI targets. Not for launch-day go/rollback calls — use launch-day-conductor; not for metric deep-dives — use performance-analyzer; not for SEO rank tracking — use rank-tracker. 发布监控/排名轮询/火焰战比/spike-sustain

Quality

91%

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

85%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 tightly engineered instruction-only skill: clear scope boundaries, receipt-bound close semantics, explicit labeling rules (Measured / User-provided / Estimated), and well-signaled external references. Its weaknesses are density and repetition rather than missing substance, plus the absence of any example connector invocation for a skill whose whole job is polling via four scripts.

Suggestions

Add one example invocation per connector in Data Sources (e.g., `python scripts/connectors/hn.py <story-url>` and its output shape) so the polling steps are copy-paste executable instead of by-filename reference.

State the launch-day-conductor / retro-analyzer routing once in the Scope guard and reference it from steps 4, 7, and 8 instead of restating the full handoff each time.

Split the 90-word single-sentence steps (especially step 1) into short sub-bullets for mode/receipt/targets so the receipt rules scan without re-reading.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and every section is functional, but it is dense to a fault — steps 1 and the opening paragraph are 90-100-word single sentences — and cross-skill handoffs repeat (launch-day-conductor appears in the Scope guard, step 4, Reference Materials, and Next Best Skill; launch-retro-analyzer appears four times), so it is not 'every token earns its place'. Not 3: there is no truly unnecessary explanation, only tightening opportunities; not 5: the repetition and compound-sentence density exceed the lean anchor.

4 / 5

Actionability

Guidance is concrete throughout — named connector scripts ('scripts/connectors/hn.py (keyless Algolia + Firebase — rank, points, comments)'), explicit cadence limits ('gdelt.py needs ≥5s between calls; keep HN/PH polling to a few reads per hour'), a save-path template ('memory/launch/launch-monitor/YYYY-MM-DD-<topic>.md'), and alert fields (metric, threshold, KPI target). Not 5: for a script-driven skill, no connector is ever shown being invoked (no example call to hn.py or producthunt.py with arguments), leaving the polling steps one level short of copy-paste executable; not 3: the guidance is specific and directive, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

Eight numbered steps are clearly sequenced (confirm mode → verify instrumentation → set cadence → watch signals → snapshot → read retention → alert → close), with explicit validation (per-surface pass/fail in step 2, 'No targets means NEEDS_INPUT' in step 1, a 'Done when' checklist) and a real feedback loop: close only when 'every required current-manifest action has a terminal matching receipt', otherwise 'emit window_status: OPEN with the missing receipt IDs' and re-check. Not 4: checkpoints and error-recovery loops are explicit rather than merely present; this is a read/watch skill, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The body is a well-organized overview and detail is offloaded to clearly signaled, one-level-deep references, each annotated with its purpose in Reference Materials ('CONNECTORS.md — connector setup for scripts/connectors/hn.py, producthunt.py...', 'Launch Action Control — receipt-bound snapshots, required-action joins, and close-window semantics'). No bundle files ship with this skill, and the inline content (the 8-step procedure, Skill Contract) is core operating material that belongs in SKILL.md, not material that should have been split out. Not 4: navigation is easy, references are labeled, and nothing inlined obviously belongs in a separate file.

5 / 5

Total

18

/

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.

A model description: quoted natural trigger phrases, a comprehensive third-person action inventory, an explicit launch-window scope, and negative routing to the three nearest conflicting skills. The trailing Chinese keyword line and internal framework jargon add length but no ambiguity about when to invoke the skill.

DimensionReasoningScore

Specificity

The description enumerates eight-plus concrete actions — 'pre-launch instrumentation verification (UTM/event checks...)', 'HN rank/points/comments polling with a comments-over-points flamewar early-warning', 'PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds' — comprehensive coverage of the skill's behavior. Not 4: the action list has no coverage gaps; it matches the multiple-specific-actions anchor exactly, and the voice is third-person ('runs the...window watch'), so no voice penalty applies.

5 / 5

Completeness

Both halves are explicit: 'Use when the user asks to "monitor my launch"...' answers when with concrete trigger phrases, and 'runs the T-0 to T+30 window watch — [enumerated activities]' answers what, with negative scope ('Not for launch-day go/rollback calls — use launch-day-conductor') on top. Not 4: the 'when' clause is fully explicit with quoted trigger phrases, not merely present but improvable.

5 / 5

Trigger Term Quality

It leads with directly quoted natural user phrasings — 'monitor my launch', 'track our Product Hunt / Hacker News ranking', 'watch the launch window' — and covers synonyms (monitor/track/watch; HN/Hacker News; PH/Product Hunt). Not 4: natural terms, their variations, and platform names are all present rather than 'a few missing'; the internal jargon (RAMP P1, owned-capture) supplements rather than displaces the natural keywords.

5 / 5

Distinctiveness Conflict Risk

The niche is precise — a T-0 to T+30 launch-window watch — and three adjacent skills are explicitly routed away ('use launch-day-conductor', 'use performance-analyzer', 'use rank-tracker'), leaving minimal overlap risk with closely related launch/monitoring skills. Not 4: the not-for list actively disambiguates the nearest neighbors rather than leaving minor residual overlap.

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: 11 missing, 11 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

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