Agent skill

eol-internal-enablement

Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.

Dean Peters6,255★ · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/eol-internal-enablement/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,444
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# EOL Internal Enablement ## Purpose Build what customer-facing teams need **before** the EOL announcement goes out: a support FAQ, sales talking points with honest comparison data, objection handling, an escalation ladder, and — when the sunset warrants it — a channel partner brief and a training outline. The cardinal sin of EOL communication is handing Support and Sales the announcement five minutes before customers get it and wishing them luck. This skill exists to prevent that. Internal readiness is a prerequisite for announcing, not a follow-up task. ## Input **Works best with:** The product being sunset, what replaces it (if anything), and the key dates. **Also useful:** The objections you expect, which accounts are at risk, what continues versus what stops, and whether channel partners are in the picture. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks up to three questions — what's being sunset and what replaces it, the dates for stopping sale/support/s

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. Right-Size the Pack
  5. Enablement Precedes Announcement — Always
  6. Organize the FAQ by What Customers Ask
  7. Acknowledge — Reframe — Offer
  8. The Predictable Objections
  9. Escalation Is a Ladder With Names
  10. The Sticky-Note Rule
  11. Anti-Patterns (what this is NOT)
  12. Application
  13. Step 1: Set the level and the dates
  14. Step 2: Build the support FAQ (all levels)
Ships with 3 files
  • examples/sample-industrial.md
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the eol-internal-enablement skill do?

Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement --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 deanpeters/Product-Manager-Skills, a repository with 6,444 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.

Keep going