SkillAgentSearch skills...

eol-readiness-advisor

Run a go/no-go assessment for retiring a product or feature, then right-size the effort

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of eol-readiness-advisor

eol-readiness-advisor scores 90/100 on our quality scale, 1289th of 4,700 Development & Engineering skills we index (top 28%).

Its SKILL.md is 21 KB long, well organised into 35 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so eol-readiness-advisor is actively maintained.
  • Our last check on 2026-10-30 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

eol-readiness-advisor compared with similar skills

All 4 of these similar skills score higher than eol-readiness-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
eol-readiness-advisor (this skill)by deanpeters907.1k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install eol-readiness-advisor?
Run npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does eol-readiness-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is eol-readiness-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is eol-readiness-advisor still maintained?
The repository was last updated about 3 months ago, so eol-readiness-advisor is actively maintained.

name: eol-readiness-advisor argument-hint: "[product or feature under EOL consideration, and what triggered it]" description: "Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Use when someone says "we should probably kill this" and nobody has made the call." intent: >- Structured go/no-go assessment for sunsetting a product or feature. Determines whether EOL is the right call, how intense the sunset effort needs to be, and which organizational functions need to be involved. Prevents both premature kills and expensive delays on products that should have been retired sooner. type: interactive theme: eol-transition best_for:

  • "Deciding whether a declining product should actually be retired — or held, harvested, or fixed"
  • "Right-sizing an EOL effort so a feature deprecation doesn't get a flagship playbook"
  • "Naming the obligations and landmines that make a sunset harder than it looks" scenarios:
  • "Leadership keeps saying we should kill this module but nobody will make the call — help me assess it"
  • "We're retiring a hardware line with service contracts and channel partners; how big does this effort need to be?" estimated_time: "15-25 min"

EOL Readiness Advisor

Purpose

Decide whether a product or feature should actually be retired — and if so, how much machinery the retirement deserves. This skill produces a go/no-go verdict with named evidence, an intensity level you choose, and a short list of the obligations that will bite you if ignored.

Most EOL guidance assumes the decision is already made and jumps to the plan. This skill sits earlier: it is the conversation where "we should probably kill this" becomes a decision someone will defend in a room.

It is equally willing to tell you not to retire. A "hold" or "harvest" verdict is a real outcome here, not a consolation prize.

Input

Works best with: The product or feature under consideration and what triggered the conversation (a declining number, a strategy shift, a support-cost complaint, an exec offhand remark).

Also useful: Revenue and customer counts, whether a replacement exists, contract or regulatory commitments, and any political sensitivities you already know about.

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 opens by asking what's under review and why, then walks you through blast radius, intensity, and transition path one question at a time. You do not need the numbers in front of you — "I don't know" is a valid answer that becomes a labeled assumption in the verdict.

Example invocations:

  • Should we retire our legacy reporting module? Usage is down 60% and support costs are climbing.
  • EOL readiness check on our NFA-200 controller line — 120 installs, channel partners, UL certified.

Key Concepts

The Right-Sizing Dial

Not all EOLs play out the same. Some are a changelog entry and a support macro. Some consume the whole company for three quarters. Most land in the middle. The single most common EOL failure in either direction is a mismatch between the size of the sunset and the size of the response — a flagship retirement run as a Jira ticket, or a feature deprecation that spawns a steering committee.

So the intensity is a dial you set, not a verdict the framework hands you:

| Dimension | Level 1 — Light | Level 2 — Standard | Level 3 — Heavy | |---|---|---|---| | Typical scope | Feature, internal tool, unversioned API | Commercial product with active customers | Revenue-critical, hardware, regulated | | Stakeholder stops | 3-4 | 7-8 | 10+ | | Lifecycle gates used | 2-3 (NSC, EOS, EOL) | 4-5 (NSC, EOS, EOE, EOM, EOL) | All 8 (GA through EOSRV) | | Functional areas | Product, Eng, Support, Docs | + Sales, Marketing, CS, Finance, Legal, IT, Data | + Supply Chain, Channel, Regulatory, Org | | Enablement | Support FAQ only | + Sales talking points, objections, escalation | + Channel brief, account tiers, training | | Customer message | Brief notice | Standard with phase table | Full with compliance section | | Typical lead time | Weeks | 6-12 months | 12-24 months |

Level 2 is where most sunsets belong. Treat it as the default and argue your way up or down.

The dial is yours to move. Recommend a level, explain the reasoning, then let the user override in either direction — and let them move it again later. A PM who says "give me the light version, I know my org" is exercising judgment, not making an error. Honor it, and note in one line what the lighter level leaves uncovered so the choice is informed rather than blind.

Lifecycle Gates (shared vocabulary)

EOL is not one date. It is a series of gates, and most customer anger comes from collapsing them into a single announcement:

  • GA (General Availability): Actively sold and fully supported
  • NSC (Notice of Status Change): The decision is communicated; planning begins
  • EOS (End of Sale): No new customers can purchase
  • EOE (End of Expansion): Existing customers cannot add capacity or seats
  • EOR (End of Renewal): Existing contracts will not be renewed
  • EOM (End of Maintenance): Bug fixes and patches stop
  • EOL (End of Life): The product is retired
  • EOSRV (End of Service): All support and service obligations end

Light sunsets use three of these. Heavy sunsets use all eight. Naming the gates you're not using is as useful as naming the ones you are.

The Four Retire Signals

Evidence that supports a go verdict. Two or more, strongly present, is a real case:

  1. Financial viability — costs exceed revenue; support load drains disproportionate resources
  2. Strategic alignment — conflicts with company direction; you are exiting this market
  3. Solution replacement — an internal successor supersedes it; you're consolidating platforms
  4. Market irrelevance — needs shifted, technology moved, the core problem stopped existing

The Four Hold Signals

Evidence that argues against retiring now, even when the retire signals are loud:

  1. Obligation lock — contracts, SLAs, regulatory commitments, or "lifetime" promises still run
  2. Strategic hostage — low revenue, but it sits inside your most important accounts
  3. No landing place — no replacement and no third-party alternative; customers would be stranded
  4. Exit costs exceed carry costs — the sunset costs more than another year of quiet maintenance

Anti-Patterns (what this is NOT)

  • Not a rubber stamp. If the hold signals dominate, the verdict is hold, and the skill says so.
  • Not a portfolio screen. This assesses one product. Screening a catalog is different work.
  • Not the plan. The verdict and intensity level are inputs to planning, not the plan itself.
  • Not a financial model. It reasons about revenue and cost qualitatively; it does not forecast.

Application

Use workshop-facilitation as the default interaction protocol for this skill.

This skill asks up to 4 adaptive questions, then delivers a verdict, an intensity level, and numbered next steps. Give the heads-up at the start: four questions, roughly fifteen minutes, and they can dump context at any point to skip ahead.


Question 1 of 4 — What's under review, and what triggered this?

Agent asks:

"What product or feature is under EOL consideration, and what brought it up? The trigger matters as much as the product — a declining metric, a strategy shift, a support-cost complaint, and an exec offhand remark lead to very different assessments."

Is retirement even the right question yet? This skill assesses one play: retiring. At the mature-to-decline inflection there are three — extend the product, replace it with a successor, or retire it. If the user hasn't established that retirement is the play, say so and offer the upstream diagnosis:

"Before we assess retiring it — is retiring the play you've settled on? There are two others (extend it, or replace it with a successor), and lifecycle-play-advisor works out which fits. Happy to continue here if the call is made."

Don't force the detour. A user who says "we've decided, assess the retirement" gets the assessment.

Listen for the trigger type, because it predicts the failure mode:

| Trigger | Watch for | |---|---| | Declining metric | Is it decline, or seasonality/measurement change? | | Strategy shift | Is the product misaligned, or just unfashionable? | | Support cost | Is retirement the fix, or is a bug fix the fix? | | Exec remark | Is there evidence, or is this an opinion with a title? | | Replacement shipped | Is the replacement actually at parity for these customers? |

If the trigger is an exec remark with no supporting evidence, say so plainly at verdict time. That is the single most common source of premature kills.


Question 2 of 4 — What's the blast radius?

Agent asks:

"Help me size the impact. Rough numbers are fine, and 'I don't know' is a real answer:

  1. Customers: How many accounts or users are on it?
  2. Revenue: Roughly what does it represent, and is it concentrated in a few accounts?
  3. Commitments: Any contracts, SLAs, renewal dates, or regulatory obligations attached?
  4. Physical or channel: Is there hardware, inventory, spare parts, or are partners reselling it?"

Why this matters (say it): These four answers set the intensity level. Item 3 is the one that most often turns a "simple" sunset into a legal problem — it is asked early on purpose.

Mark any unknown as an assumption to be labeled in the verdict. Do not stall the flow to chase a number; an assessment with three labeled assumptions beats an assessment that never happened.


Question 3 of 4 — Set the intensity

Agent presents the recommendation, then hands over the dial:

"Based on what you've described, here's my read on how much machinery this deserves:

Recommended: Level [N] — [Light / Standard / Heavy] Because: [two or three specifics drawn from their answers]

  1. Level 1 — Light. Punch list, 3-4 stakeholders, brief notice. Right when the blast radius is internal or the users are few and reachable.
  2. Level 2 — Standard. Cross-functional checklist, 7-8 stakeholders, phased customer comms. Right for a commercial product with real customers and no regulatory entanglement. Most sunsets belong here.
  3. Level 3 — Heavy. Full playbook, 10+ stakeholders, all eight gates, channel and regulatory workstreams. Right when revenue is critical, hardware is in the field, or compliance applies.

Take the recommendation, or pick a different level — you know your organization. You can also change it later; nothing downstream is locked to this choice."

If the user dials down, accept it and add one line: "Going lighter than recommended means [the specific thing that goes uncovered — usually Legal review, channel notification, or migration support]. Flagging it so it's a choice, not a surprise."

If the user dials up, accept it without argument. Over-preparing an EOL is a cheap mistake.


Question 4 of 4 — Where do customers land?

Agent asks:

"What happens to the people using it? Three broad paths:

  1. Replacement — another product of yours takes over
  2. Migration — they move to a different configuration, tier, or platform
  3. Graceful exit — nothing replaces it; they need data, notice, and alternatives

Which is it, and how ready is that path today?"

Path readiness is a go/no-go input, not a detail. A replacement that is not at feature parity for these specific customers is not a landing place yet. If the path is unready, the verdict is

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryDevelopment
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
eol-readiness-advisor — Universal Skill: Install & Safety Check | SkillAgent