.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Run a go/no-go assessment for retiring a product or feature, then right-size the effort.
Install Eol Readiness Advisor
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/eol-readiness-advisor .claude/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .claude/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/eol-readiness-advisor .agents/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .agents/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/eol-readiness-advisor .cursor/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .cursor/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/eol-readiness-advisor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/eol-readiness-advisor .gemini/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .gemini/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/eol-readiness-advisor .github/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .github/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/eol-readiness-advisor .opencode/skills/eol-readiness-advisor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "eol-readiness-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor into .opencode/skills/eol-readiness-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-readiness-advisor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
eol-readiness-advisor- GitHub stars
- 7.2k
- Token cost
- ~5.4k tokens
- SKILL.md length
- 2,876 words
- Files
- 1
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Run a go/no-go assessment for retiring a product or feature, then right-size the effort.
- Works in 4 steps: Financial viability — costs exceed… → Strategic alignment — conflicts with… → Solution replacement — an internal… → …
- Someone says we should probably kill this and nobody has made the call
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Reaches github.com
What it does
Eol Readiness Advisor is an agent skill from deanpeters/Product-Manager-Skills. 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.
Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
When your agent uses it
- Someone says we should probably kill this and nobody has made the call
- Tasks that involve Feature launches and release readiness
Example prompts
- “we should probably kill this”
- “/eol-readiness-advisor”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Financial viability — costs exceed revenue; support load drains disproportionate resources
- Strategic alignment — conflicts with company direction; you are exiting this market
- Solution replacement — an internal successor supersedes it; you're consolidating platforms
- Market irrelevance — needs shifted, technology moved, the core problem stopped existing
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Eol Readiness Advisor loads about 5.4k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 2,876 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,876 words (~5,386 tokens).
“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…”
- name
- eol-readiness-advisor
- argument-hint
- [product or feature under EOL consideration, and what triggered it]
- 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…
- 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…
- 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…
- estimated_time
- 15-25 min
Files
Just SKILL.md in skills/eol-readiness-advisor of deanpeters/Product-Manager-Skills.
Open the folder on GitHubat commit 1b5a524
Compare with similar skills
Eol Readiness Advisor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Eol Readiness Advisor this skilldeanpeters/Product-Manager-Skills | 7.2k | — | ~5.4k | Automated safety check: Pass | Custom licence | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoUser Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
TAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Related
Categories
Questions about Eol Readiness Advisor
What does Eol Readiness Advisor do?
Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Eol Readiness Advisor is an agent skill from deanpeters/Product-Manager-Skills. Run a go/no-go assessment for retiring a product or feature, then right-size the effort.
When should I use Eol Readiness Advisor?
Eol Readiness Advisor fits situations like: someone says we should probably kill this and nobody has made the call; tasks that involve Feature launches and release readiness.
How do I install Eol Readiness Advisor in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a claude-code`. Or copy the skill folder (skills/eol-readiness-advisor in deanpeters/Product-Manager-Skills) into .claude/skills/eol-readiness-advisor in your project. Claude Code loads it when a task matches its description.
How do I install Eol Readiness Advisor in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a codex`. Or copy the skill folder (skills/eol-readiness-advisor in deanpeters/Product-Manager-Skills) into .agents/skills/eol-readiness-advisor in your project. Codex loads it when a task matches its description.
Can I use Eol Readiness Advisor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eol-readiness-advisor, .gemini/skills/eol-readiness-advisor, .github/skills/eol-readiness-advisor and .opencode/skills/eol-readiness-advisor in your project.
What does Eol Readiness Advisor need to run?
SKILL.md names no scripts, command-line tools or credentials: Eol Readiness Advisor is instructions for the agent only.
Does Eol Readiness Advisor access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Eol Readiness Advisor safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Eol Readiness Advisor use?
Eol Readiness Advisor has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Eol Readiness Advisor use?
About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Eol Readiness Advisor?
Skills that share tags, products or a category with Eol Readiness Advisor: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eol Readiness Advisor?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.