Skip to content
mcp/skillhub

Agent Skill

Eol Message skill

eol-messagedeanpeters/Product-Manager-Skillsskills/eol-message/SKILL.md

Write a right-sized EOL announcement — brief notice through full phased comms — with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan.

7.6k

always on

41 tokname + description

once used

3,712 tokSKILL.md body

bundled files

320 KB

repo stars

7.6kGitHub

Install the Eol Message skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-message

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills
mkdir -p ~/.claude/skills
cp -R /tmp/Product-Manager-Skills/skills/eol-message ~/.claude/skills/eol-message

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description41 tok
When the agent uses itThe SKILL.md instructions3,712 tok
Only if opened3 bundled files (20 KB)varies

Until it is used, eol-message costs about 33× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 77 skills from deanpeters/Product-Manager-Skills would load 2,883 tokens of descriptions. Skills vs MCP study

Checks

Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • EOL Message
  • Purpose
  • Input
  • Key Concepts
  • Size the Message to the Change
  • The Three Transition Paths
  • Lifecycle Gates (shared vocabulary)
  • The EOL Messaging Framework
  • Why This Works
  • The Sticky-Note Rule
  • Anti-Patterns (What This Is NOT)
  • When to Use This
  • When NOT to Use This
  • Application
  • Step 1: Establish size and path
  • Step 2: Gather context
  • Step 3: Draft the transition narrative
  • Step 4: Provide current product context
  • Step 5: Acknowledge customer impact
  • Step 6: Present the transition solution
  • Step 7: Outline support measures and timeline
  • Step 8: Provide clear next steps
  • Final Step: Offer what comes next
  • Examples

More skills from deanpeters/Product-Manager-Skills

All skills in this repo
  1. acquisition-channel-advisordeanpeters/Product-Manager-Skills

    Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.

    7.6k34 tok idle · 5,366 in use
  2. agent-orchestration-advisordeanpeters/Product-Manager-Skills

    Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.

    7.6k40 tok idle · 7,154 in use
  3. ai-shaped-readiness-advisordeanpeters/Product-Manager-Skills

    Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

    7.6k33 tok idle · 9,703 in use
  4. altitude-horizon-frameworkdeanpeters/Product-Manager-Skills

    Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

    7.6k33 tok idle · 2,912 in use
  5. ansoff-matrixdeanpeters/Product-Manager-Skills

    Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.

    7.6k40 tok idle · 2,405 in use
  6. autonomous-investigationdeanpeters/Product-Manager-Skills

    The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.

    7.6k40 tok idle · 2,475 in use
  7. battle-card-builderdeanpeters/Product-Manager-Skills

    Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

    7.6k36 tok idle · 2,168 in use
  8. business-health-diagnosticdeanpeters/Product-Manager-Skills

    Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.

    7.6k32 tok idle · 5,919 in use