eol-internal-enablement — Claude Code skill: what it does
Prepares customer-facing teams for a product sunset with a support FAQ, sales guidance, objection responses, and an escalation plan.
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a claude-codeWhat eol-internal-enablement does
The skill drafts a support FAQ, sales comparison points, objection responses built around Acknowledge–Reframe–Offer, and an escalation path. For a larger sunset, it can add a partner brief and training outline. The pack’s scope depends on the size of the change.
Provide the product being retired, its replacement, and key dates. The skill can ask up to three questions when details are missing. Expected objections, accounts at risk, and partner arrangements can also shape the materials. Without dates for ending sales, support, or service, planning the transition is harder.
What it helps with
- prepare a support FAQ before a sunset announcement
- give sales teams comparison points for a replacement
- draft responses to expected customer objections
- define escalation owners and triggers
- create partner and training materials for a major sunset
Example prompts for the agent
- Prepare an enablement pack for
Legacy Module; the new dashboard replaces it, with Dec 31 as the key date. - Draft a support FAQ for a feature deprecation with no replacement.
- Write sales talking points and responses to likely objections about the product sunset.
How to install eol-internal-enablement
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a claude-code2Manually: put the files in place
~/.claude/skills/eol-internal-enablement/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/eol-internal-enablement/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a codex2Manually: put the files in place
.agents/skills/eol-internal-enablement/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a cursor2Manually: put the files in place
.cursor/skills/eol-internal-enablement/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills eol-internal-enablement2Manually: put the files in place
.github/skills/eol-internal-enablement/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/eol-internal-enablementManually: put the files in place
.devin/skills/eol-internal-enablement/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -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-internal-enablement
How do I install eol-internal-enablement in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a claude-code. The skill file is at ~/.claude/skills/eol-internal-enablement/SKILL.md.
What does eol-internal-enablement do?
It prepares internal materials for a product sunset: a support FAQ, sales guidance, objection responses, and an escalation plan.
What details should I provide to the skill?
Name the product being retired, its replacement, and the key dates. Expected objections, at-risk accounts, and partner involvement can also inform the pack.