launchnotes-release-recap
Use when the user wants to know how a published update or a release landed — e.g. "how did last week's announcement do?", "recap the 2.4 release performance", "which updates got the most engagement?". Reports per-announcement engagement (views, email open/click, feedback sentiment, reach) and audience health from LaunchNotes' own analytics. Read-only. It does not measure product usage or adoption — that data isn't in LaunchNotes. Load launchnotes-use first.
Install
With your agent
Install OMGSkills skill "launchnotes/mcp-server-guide:skills/launchnotes-release-recap" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/launchnotes/mcp-server-guide /tmp/mcp-server-guide && ln -s /tmp/mcp-server-guide/skills/launchnotes-release-recap ~/.claude/skills/launchnotes-release-recapFrom README
Recap how a release landed An engagement recap a PM can paste into standup — from LaunchNotes analytics only. Requires: launchnotes-use loaded, a LaunchNotes project. Best when the user names a specific announcement or a recent release window. Steps Pull per-announcement metrics with launchnotesgettopannouncements (ranked, up to 50): unique viewers, emails sent, open/click rate, feedback sentiment, per-channel reach. A specific recent announcement will surface here reliably. Add audience context with launchnotesgetprojectanalytics: subscriber count and the confirmed / unsubscribed / blocked breakdown, plus overall sentiment. Report the highlights plainly — what got read, what resonated, how the audience is trending. Lead with the one or two numbers that matter, not a data dump. Guardrails (specific to this skill) Aggregate only, and say so. You can't see individual subscribers, emails, or raw exports — that stays in LaunchNotes by design. Frame it as a trust feature, not a gap.
More from this repo
launchnotes-draft-from-work
Used when the user wants to turn shipped or in-progress work into a LaunchNotes announcement — e.g.
launchnotes-feedback-to-roadmap
Used when the user wants to turn reader feedback into roadmap items — e.g.
launchnotes-import-existing-changelog
Used when the user wants to bring an existing changelog or blog into LaunchNotes — e.g.