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-
Profile →npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-monitor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Launch Monitor Watches the launch window — T-0 through T+30 — so traction is verifiable while it happens, not reconstructed afterwards. It is the first Prove-phase skill in the [RAMP loop](../../../references/ramp-benchmark.md): its pre-launch mode verifies measurement instrumentation on every launch surface (the direct upstream of the `P1` veto — untagged surfaces make traction unverifiable), and its window mode feeds the RAMP `P` sub-items for instrumentation, per-channel attribution reconciled against own analytics, KPI actuals vs targets at D0/W1/M1, spike-vs-sustain retention, and owned-capture rate. The live watch itself is the evidence behind the `M` live-monitoring-coverage sub-item. Telemetry comes from keyless or free-key connectors — `scripts/connectors/hn.py` (keyless), `scripts/connectors/producthunt.py` (free-key developer token; non-commercial API ToS — business use needs Product Hunt approval, attribution required), `scripts/connectors/appstore.py` (keyless documented endpoints), `scripts/connectors/gdelt.py` (news echo) — and degrades to user-pasted values when a connector or key is missing. It works one lever — window telemetry — and hands off. **Scope guard**:
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the launch-monitor skill do?
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-
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-monitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.