Menu

Individual skill

launch-monitor

0upvotes

Use this skill when a product launch is live and you need to know what press, social, and developer communities are saying — and what to do about it. Produces a response war room report: a triaged signal feed with urgency levels and action badges, a mischaracterization tracker with copy-ready corrections, a competitor response panel, and a sentiment velocity read. Reach for it when someone says "monitor this launch", "track the launch", "what's being said about the launch", "what's the reaction to the announcement", "flag any mischaracterizations", "check press coverage for the launch", "post-launch coverage", or "how are competitors responding to our launch". Not for steady-state brand monitoring outside a launch window.

skills/uri-knorovich/launch-monitor/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Applies from the moment a launch is public until the coverage wave dies — typically two to four weeks. Produces a triaged response war room report where every signal carries an urgency level, an action badge, and an exact source link, so the team knows what to respond to, correct, amplify, or escalate — in that order.

Replace before enabling: `{{ALERTS_CHANNEL}}` — where act-now items get flagged to the team; `{{COMMS_OWNER}}` — who receives escalations (comms, legal, or leadership).

## Before the first sweep

Do two research steps before asking the user anything:

1. **Resolve alternate names silently.** Search the live web for the product's codenames, former names, version names, API/SDK/repo names, and model identifiers — they are often different from the marketing name, and coverage splits across all of them. Fold every confirmed variant into your query list without showing the user this step. Query patterns are in `references/sources.md`.
2. **Confirm the launch date from evidence.** Search for when the product actually launched. Present what you found for confirmation; if announcement date and general availability differ, surface both and ask which window matters.

Then confirm in a single message: launch date, lookback window (default: launch to now), depth (quick scan vs deep sweep — default deep), and competitors to prioritize or exclude (default: on, identified automatically). If the user says "just run it", take every default. If the product name is ambiguous after research, disambiguate before spending a single search on the wrong product.

**Profile the product before querying.** Answer five questions from the announcement and a quick search: What category is it? What ecosystem does it live in? Who is the audience? What are the key launch claims? And — most important — what would a mischaracterization look like: wrong category, wrong price, wrong capability, wrong comparison? This profile decides which communities you sweep, and you cannot flag a mischaracterization without knowing what "correct" looks like.
Back to top