Price Increase Announcement
mohitagw15856/pm-claude-skills
Announce a price increase without triggering a churn spike — the rationale, grandfathering, effective dates, the FAQ, and the internal brief so support isn't blindsided.
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
Install Eol Internal Enablement
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-internal-enablement --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-internal-enablement .claude/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .claude/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablementType 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-internal-enablement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-internal-enablement --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-internal-enablement .agents/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .agents/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-internal-enablement --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-internal-enablement .cursor/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .cursor/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablement--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-internal-enablement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-internal-enablement --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-internal-enablement .gemini/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .gemini/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablementInstalls 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-internal-enablement -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-internal-enablement .github/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .github/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablement -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-internal-enablement --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-internal-enablement .opencode/skills/eol-internal-enablement && 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-internal-enablement" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-internal-enablement into .opencode/skills/eol-internal-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-internal-enablement", 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-internal-enablement- GitHub stars
- 7.2k
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,629 words
- Files
- 4
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
- Works in 6 steps: Set the level and the dates → Build the support FAQ (all levels) → Build sales talking points (Level 2+) → …
- Customer-facing teams must be ready before customers hear
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Reaches github.com
What it does
Eol Internal Enablement is an agent skill from deanpeters/Product-Manager-Skills. 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.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `examples/sample-industrial.md`, `examples/sample.md` and `template.md`).
It sits in Sales & Support, covering Help center and FAQ content and Sales enablement. 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
- Customer-facing teams must be ready before customers hear
- Tasks that involve Help center and FAQ content
- Tasks that involve Sales enablement
Example prompts
- “/eol-internal-enablement”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Set the level and the dates
- Build the support FAQ (all levels)
- Build sales talking points (Level 2+)
- Build objection handling (Level 2+)
- Channel brief and training (Level 3)
- Assumptions
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.
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 Internal Enablement loads about 3.1k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 1,629 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 1,629 words (~3,115 tokens).
“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…”
- name
- eol-internal-enablement
- argument-hint
- [product being sunset, replacement, and key dates]
- intent
- Generate the internal enablement materials customer-facing teams need before an EOL announcement goes out: a support FAQ, sales comparison talking points…
- type
- component
- theme
- eol-transition
- best_for
- Arming Support and Sales before the announcement, not five minutes after it, Turning predictable EOL objections into honest, non-defensive responses, Giving…
- scenarios
- We announce the sunset in three weeks and Support has nothing — what do they need?, Sales keeps getting ambushed on our EOL; build them talking points and…
- estimated_time
- 25-45 min
Files
SKILL.md and 3 other files in skills/eol-internal-enablement of deanpeters/Product-Manager-Skills.
- SKILL.md
- examples/sample-industrial.md
- examples/sample.md
- template.md
Open the folder on GitHubat commit 1b5a524
Compare with similar skills
Eol Internal Enablement 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 Internal Enablement this skilldeanpeters/Product-Manager-Skills | 7.2k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Price Increase Announcementmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Pricing Change StrategistOneWave-AI/claude-skills | 336 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sales Enablement Kitaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Brand Product Knowledge Builderlimecloud/lime | 1.5k | — | ~709 | Automated safety check: Pass | Apache-2.0 | |
| Case Study BuilderBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.8k | Automated safety check: Pass | None |
Similar skills
Pricing Change Strategist
OneWave-AI/claude-skills
Design and roll out a price increase or packaging change without triggering churn.
Sales Enablement Kit
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch…
Brand Product Knowledge Builder
limecloud/lime
将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的产品资料知识库。适用于用户要求“整理产品知识库”“沉淀产品 FAQ”“把品牌产品资料变成项目资料”“维护产品资料包”的场景。
Case Study Builder
BrianRWagner/ai-marketing-claude-code-skills
Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
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 Internal Enablement
What does Eol Internal Enablement do?
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Eol Internal Enablement is an agent skill from deanpeters/Product-Manager-Skills. Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
When should I use Eol Internal Enablement?
Eol Internal Enablement fits situations like: customer-facing teams must be ready before customers hear; tasks that involve Help center and FAQ content; tasks that involve Sales 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`. Or copy the skill folder (skills/eol-internal-enablement in deanpeters/Product-Manager-Skills) into .claude/skills/eol-internal-enablement in your project. Claude Code loads it when a task matches its description.
How do I install Eol Internal Enablement in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-internal-enablement -a codex`. Or copy the skill folder (skills/eol-internal-enablement in deanpeters/Product-Manager-Skills) into .agents/skills/eol-internal-enablement in your project. Codex loads it when a task matches its description.
Can I use Eol Internal Enablement 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-internal-enablement -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-internal-enablement, .gemini/skills/eol-internal-enablement, .github/skills/eol-internal-enablement and .opencode/skills/eol-internal-enablement in your project.
What does Eol Internal Enablement need to run?
SKILL.md names no scripts, command-line tools or credentials: Eol Internal Enablement is instructions for the agent only.
Does Eol Internal Enablement 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 Internal Enablement 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 Internal Enablement use?
Eol Internal Enablement 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 Internal Enablement use?
About 3.1k tokens (SKILL.md is roughly 12k 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 Internal Enablement?
Skills that share tags, products or a category with Eol Internal Enablement: Price Increase Announcement (mohitagw15856/pm-claude-skills, 1.4k stars), Pricing Change Strategist (OneWave-AI/claude-skills, 336 stars), Sales Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Brand Product Knowledge Builder (limecloud/lime, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eol Internal Enablement?
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.