CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./launch/prove/launch-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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, contract-driven overview with a clear sequenced workflow and good external-reference discipline. It is held back by repeated handoff cross-linking across sections and by instructional guidance that stays at the directive level rather than providing executable connector examples.

Suggestions

De-duplicate sibling-skill handoffs: state each boundary once in Scope guard and reference it from Next Best Skill rather than re-listing all targets three times.

Add one or two executable examples showing how to invoke a connector (e.g. a sample `python scripts/connectors/hn.py ...` call or the expected CLI/arguments) so the polling steps are copy-pasteable, not just described.

Tighten the RAMP/registry jargon (P1 veto, P/M sub-items, operation: propose) or move the framework binding into ramp-benchmark.md so the overview reads cleanly without it.

DimensionReasoningScore

Conciseness

Mostly efficient prose that does not over-explain basic concepts, but the same sibling-skill handoff targets (launch-day-conductor, performance-analyzer, launch-retro-analyzer, etc.) are repeated across the Scope guard, Reference Materials, and Next Best Skill sections, which is padding that could be tightened.

3 / 5

Actionability

The 8-step instructions name connector scripts, data labels, modes, and thresholds, but give no executable code or sample connector invocations — readers learn what to do, not how to run hn.py/producthunt.py/gdelt.py, leaving key execution details implicit.

3 / 5

Workflow Clarity

A clear 8-step sequence is anchored by a 'Done when' contract, mode/receipt binding in step 1, per-surface pass/fail in step 2, threshold-named alerts in step 7, and an explicit window_status: OPEN fallback in step 8; validation is present, so the batch-operation cap does not apply, though a couple of checkpoints remain implicit.

4 / 5

Progressive Disclosure

A dedicated Reference Materials section signals one-level-deep links (ramp-benchmark.md, action-control.md, CONNECTORS.md, SECURITY.md, skill-contract.md) and the overview correctly defers detail to those files; however no bundle files ship in this skill directory and the cross-reference list is dense and somewhat repetitive, keeping it just short of fully clean navigation.

4 / 5

Total

14

/

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 strong, well-constructed description: explicit natural-language triggers, a comprehensive concrete action list, clear what/when pairing, and proactive disambiguation against sibling skills. Its only real weakness is verbosity and heavy internal jargon (RAMP P1, spike-sustain, owned-capture), but that is not a scored dimension here.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — pre-launch UTM/event verification, HN rank/points/comments polling, flamewar early-warning, PH votes/featured status, store charts/reviews, news echo, D0/W1/M1 KPI snapshots, spike-vs-sustain and owned-capture reads, threshold alerts — giving comprehensive coverage rather than generic phrasing.

5 / 5

Completeness

It explicitly answers both 'what' (runs the T-0 to T+30 window watch enumerating every activity) and 'when' (concrete trigger phrases), matching the anchor that requires both with explicit triggers.

5 / 5

Trigger Term Quality

An explicit 'Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"' clause supplies natural phrases plus synonyms (launch/monitor/track/watch, PH/HN, Product Hunt/Hacker News) a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Three explicit 'Not for ... use launch-day-conductor / performance-analyzer / rank-tracker' disambiguation clauses carve a clear niche and minimize wrong-skill triggering.

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: 11 missing, 11 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.