eol-message — Claude Code skill: what it does, how to install
Drafts proportional sunset notifications for retiring features, tools, or subscription plans. Clarifies rationale, migration options, and timelines to keep user trust intact.
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a claude-codeWhat eol-message does
This skill creates end-of-life notices calibrated to the scope of the retirement. Minor interface adjustments receive a brief heads-up of one to three paragraphs. Commercial offerings or core services receive a multi-stage communication plan with lifecycle milestones, spanning the period from halting new sales to final decommission. It articulates why the retirement happens from the customer perspective rather than corporate convenience.
The framework handles three distinct outcomes: directing users to an internal replacement, guiding migration to another tier, or sunsetting without a successor. For total shutdowns, the prompt insists on detailing data export steps and openly pointing toward third-party tools. Without a clear reason for the shutdown and explicit next steps for accounts, the skill stops to prompt for them, because omitting those details damages credibility.
What it helps with
- draft clear sunset notices without triggering support ticket spikes
- match announcement length to the real blast radius of the deprecated feature
- communicate a complete product shutdown when no in-house alternative exists
- break retirement timelines into plain-English operational milestones
Example prompts for the agent
- Draft an EOL announcement for retiring our legacy analytics module on Dec 31, moving 400 teams to the new dashboard.
- We are turning off an unused settings toggle in three weeks with no replacement. Write a brief notice for the changelog.
How to install eol-message
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a claude-code2Manually: put the files in place
~/.claude/skills/eol-message/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/eol-message/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a codex2Manually: put the files in place
.agents/skills/eol-message/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a cursor2Manually: put the files in place
.cursor/skills/eol-message/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills eol-message2Manually: put the files in place
.github/skills/eol-message/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/eol-messageManually: put the files in place
.devin/skills/eol-message/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about eol-message
How do I install eol-message in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill eol-message -a claude-code. The installer places the skill files directly into your configuration directory.
What announcement formats does eol-message support?
It provides three communication tiers: brief notices for minor settings, standard single-page messages for active products, and multi-part campaigns for high-stakes enterprise systems.
How does the skill handle features retired without a replacement?
It applies a graceful exit structure that explains the reasoning honestly, gives concrete instructions for exporting data, and points users toward external alternatives.