Pricing Strategy
freekmurze/dotfiles
When the user wants help with pricing decisions, packaging, or monetization strategy.
End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust.
Install Eol Communication
$ npx skills add borghei/Claude-Skills --skill eol-communication -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills eol-communication --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/eol-communication .claude/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .claude/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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/borghei/Claude-Skills/tree/main/project-management/execution/eol-communicationType 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 borghei/Claude-Skills --skill eol-communication -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills eol-communication --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/execution/eol-communication .agents/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .agents/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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 borghei/Claude-Skills --skill eol-communication -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills eol-communication --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/execution/eol-communication .cursor/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .cursor/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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/borghei/Claude-Skills.git --path project-management/execution/eol-communication--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 borghei/Claude-Skills --skill eol-communication -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills eol-communication --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/execution/eol-communication .gemini/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .gemini/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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 borghei/Claude-Skills eol-communicationInstalls 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 borghei/Claude-Skills --skill eol-communication -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/execution/eol-communication .github/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .github/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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 borghei/Claude-Skills --skill eol-communication -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills eol-communication --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/execution/eol-communication .opencode/skills/eol-communication && 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-communication" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/eol-communication into .opencode/skills/eol-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-communication", 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-communication- GitHub stars
- 881
- Token cost
- ~1.2k tokens
- SKILL.md length
- 530 words
- Files
- 4 (incl. references)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust.
- Sunsetting a product
- SKILL.md covers Overview, Clarify First, When to Use and References, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Pricing strategy
What it does
Eol Communication is an agent skill from borghei/Claude-Skills. End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust. Use when sunsetting a product, feature, service, API version, or pricing tier.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `examples/sunsetting-classic-reports.md`, `references/playbook.md` and `references/red-flags.md`).
It sits in Sales & Support, covering Pricing strategy. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Sunsetting a product
- Tasks that involve Pricing strategy
Example prompts
- “/eol-communication”
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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
No URLs in SKILL.md.
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 Communication loads about 1.2k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 530 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
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 530 words, ~1,163 tokens.
Download SKILL.mdSave it as
.claude/skills/eol-communication/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- eol-communication
- description
- End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust. Use when sunsetting a product, feature, service, API version, or pricing tier.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.1
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- pm-execution
- metadata.updated
- 2026-06-15
- metadata.tech-stack
- eol, product-lifecycle, change-communication
EOL Communication Expert
Overview
Create clear, empathetic End-of-Life (EOL) communications that preserve customer trust and facilitate smooth transitions. Sunsetting a product is a high-stakes communication challenge -- done poorly, it damages brand trust and accelerates churn across your entire portfolio. Done well, it strengthens customer relationships and drives migration to replacement solutions.
The work runs in four phases: (1) Pre-announcement planning (what, why, who, when, what support, what risks), (2) Craft the message (transition narrative, customer impact, transition solution, timeline, one CTA), (3) Segment and distribute (different message and channel per segment), (4) Support and monitor (support FAQ, migration tracking, churn watch). See the playbook reference for the full framework, templates, and timeline guidance.
Clarify First
Before crafting the EOL communication, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- What is being sunset and why — drives the transition narrative and Phase 1 planning; a vague "why" reads as abandonment
- Replacement / migration path — drives the transition solution and the single CTA; if it is broken or absent, do not announce yet
- Timeline and key dates — drives the timeline section and varies sharply by product type (API vs paid product vs free feature)
- Customer segments affected — drives the Phase 3 segment/channel matrix; high-value accounts need different message and outreach than self-serve
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
When to Use
- Product sunset -- Discontinuing an entire product or product line.
- Feature deprecation -- Removing a significant feature from an existing product.
- Service migration -- Moving customers from one platform or infrastructure to another.
- API retirement -- Deprecating API versions or endpoints.
- Pricing model change -- Major pricing restructure that effectively ends old tiers.
When NOT to Use
- Minor feature changes that don't require customer notification.
- Internal tooling changes with no customer impact.
- Bug fixes or patches (use release notes instead).
Show full SKILL.md (210 more words)Show less
References
- references/playbook.md — read this when crafting a sunset announcement: the 4-phase EOL framework, the messaging template and writing rules, the segment/channel matrix, the internal support FAQ, the monitoring checklist, timeline best practices by product type, troubleshooting, and success criteria.
- references/red-flags.md — read this before sending the message to Legal and Support for review: common ways an EOL message, timeline, or migration plan goes wrong with bad/good examples anchored to the 4-phase framework.
Scope & Limitations
In Scope: EOL message creation, timeline planning, segment-specific messaging, internal FAQ preparation, migration monitoring framework, customer objection handling, support team preparation.
Out of Scope: Replacement product development, data migration tooling implementation, legal contract review, refund processing, technical infrastructure decommissioning.
Important Caveats: EOL communication is only as good as the transition path behind it. If the replacement product isn't ready or the migration path is broken, the best-written message won't prevent customer frustration. Ensure migration tooling is tested before announcing.
Integration Points
| Integration | Direction | What Flows |
|---|---|---|
create-prd/ | Complements | Replacement product PRD informs EOL transition narrative |
release-notes/ | Feeds into | Final product updates communicated alongside EOL timeline |
summarize-meeting/ | Receives from | EOL decision meeting notes inform communication content |
senior-pm/ | Receives from | Stakeholder map identifies high-risk accounts for personal outreach |
daci-framework/ | Complements | DACI chart clarifies who Drives the EOL decision and communication |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in project-management/execution/eol-communication of borghei/Claude-Skills.
- SKILL.md
- examples/sunsetting-classic-reports.md
- references/playbook.md
- references/red-flags.md
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Eol Communication 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 Communication this skillborghei/Claude-Skills | 881 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Pricing Strategyfreekmurze/dotfiles | 1k | 18 repos | ~1.6k | Automated safety check: Pass | None | |
| Profit Margin Calculator Amazonnexscope-ai/eCommerce-Skills | 1.1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Niche Opportunity Finderzanecole10/software-tailor-skills | 104 | — | ~4.2k | Automated safety check: Pass | None | |
| Pricing Strategyalirezarezvani/claude-skills | 28k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Software Pricing Calculatorzanecole10/software-tailor-skills | 104 | — | ~3.7k | Automated safety check: Pass | None |
Similar skills
Profit Margin Calculator Amazon
nexscope-ai/eCommerce-Skills
Amazon profit margin calculator for sellers. An agent skill from nexscope-ai/eCommerce-Skills.
Niche Opportunity Finder
zanecole10/software-tailor-skills
Discover untapped B2B software opportunities by analyzing specific industries for boring business problems, pain points, willingness to pay, competition levels, and where to find these businesses.
Pricing Strategy
alirezarezvani/claude-skills
Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.
Software Pricing Calculator
zanecole10/software-tailor-skills
Calculate the right price for custom software projects ($8K-$50K+) based on complexity, value delivered, and client ROI.
Pricing And Wtp
MaxKmet/idea-validation-agents
Models willingness to pay using Van Westendorp price sensitivity analysis, desire-premium multipliers, category benchmarks, and marketinsights monetization signals.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Eol Communication
What does Eol Communication do?
End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust. Eol Communication is an agent skill from borghei/Claude-Skills. End-of-life product messaging and sunset communication framework for clear, empathetic EOL announcements that preserve customer trust.
When should I use Eol Communication?
Eol Communication fits situations like: sunsetting a product; tasks that involve Pricing strategy.
How do I install Eol Communication in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill eol-communication -a claude-code`. Or copy the skill folder (project-management/execution/eol-communication in borghei/Claude-Skills) into .claude/skills/eol-communication in your project. Claude Code loads it when a task matches its description.
How do I install Eol Communication in Codex?
Run `npx skills add borghei/Claude-Skills --skill eol-communication -a codex`. Or copy the skill folder (project-management/execution/eol-communication in borghei/Claude-Skills) into .agents/skills/eol-communication in your project. Codex loads it when a task matches its description.
Can I use Eol Communication 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 borghei/Claude-Skills --skill eol-communication -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-communication, .gemini/skills/eol-communication, .github/skills/eol-communication and .opencode/skills/eol-communication in your project.
What does Eol Communication need to run?
SKILL.md names no scripts, command-line tools or credentials: Eol Communication is instructions for the agent only.
Does Eol Communication access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Eol Communication 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 Communication use?
Eol Communication is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Eol Communication use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.8k tokens, read only when the agent opens those files.
What are the alternatives to Eol Communication?
Skills that share tags, products or a category with Eol Communication: Pricing Strategy (freekmurze/dotfiles, 1k stars), Profit Margin Calculator Amazon (nexscope-ai/eCommerce-Skills, 1.1k stars), Niche Opportunity Finder (zanecole10/software-tailor-skills, 104 stars) and Pricing Strategy (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eol Communication?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.