Eol Internal Enablement
deanpeters/Product-Manager-Skills
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
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.
Install Price Increase Announcement
$ npx skills add mohitagw15856/pm-claude-skills --skill price-increase-announcement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills price-increase-announcement --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/price-increase-announcement .claude/skills/price-increase-announcement && 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 "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .claude/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcementType 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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills price-increase-announcement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/price-increase-announcement .agents/skills/price-increase-announcement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .agents/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills price-increase-announcement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/price-increase-announcement .cursor/skills/price-increase-announcement && 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 "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .cursor/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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/mohitagw15856/pm-claude-skills.git --path skills/price-increase-announcement--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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills price-increase-announcement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/price-increase-announcement .gemini/skills/price-increase-announcement && 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 "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .gemini/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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 mohitagw15856/pm-claude-skills price-increase-announcementInstalls 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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/price-increase-announcement .github/skills/price-increase-announcement && 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 "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .github/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills price-increase-announcement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/price-increase-announcement .opencode/skills/price-increase-announcement && 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 "price-increase-announcement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/price-increase-announcement into .opencode/skills/price-increase-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "price-increase-announcement", 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
price-increase-announcement- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 532 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 5 steps: Lead with the number. Say the increase… → One true reason. Ideally "we've added X,… → Soften for loyalty. A price-lock window… → …
- Asked to announce a price increase
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: A Price Increase… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Price Increase Announcement is an agent skill from 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. Use when asked to announce a price increase, write pricing change comms, raise prices to customers, or communicate new pricing. Produces the customer email, the FAQ with objection handling, the grandfathering/transition terms, and the internal enablement brief. A pricing-comms craft, not a discount.
Its SKILL.md is about 1.1k 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 Sales & Support, covering Help center and FAQ content and Sales enablement. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to announce a price increase
- Write pricing change comms
- Raise prices to customers
- Communicate new pricing
Example prompts
- “/price-increase-announcement”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Lead with the number. Say the increase in the first lines; hiding it reads as shame and breeds distrust.
- One true reason. Ideally "we've added X, Y, Z since you signed" — value earns a price. Don't over-justify.
- Soften for loyalty. A price-lock window or phased ramp for existing customers turns a shock into a fair-notice.
- Give a clear date and choice. When it hits, and what they can do (renew early, switch plan, contact us).
- Arm the front line. Support/sales get the FAQ and save-rules before customers do — never after.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Price Increase Announcement loads about 1.1k tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 532 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 532 words, ~1,056 tokens.
Download SKILL.mdSave it as
.claude/skills/price-increase-announcement/SKILL.md (or your agent's skills folder).- name
- price-increase-announcement
- description
- 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. Use when asked to announce a price increase, write pricing change comms, raise prices to customers, or communicate new pricing. Produces the customer email, the FAQ with objection handling, the grandfathering/transition terms, and the internal enablement brief. A pricing-comms craft, not a discount.
Price Increase Announcement
A price increase is a trust event, and most are botched by burying the number, over-justifying, or blindsiding support the day the emails land. This writes the version that respects the customer: the increase stated plainly and early, a reason that's true (usually more value delivered), a transition that softens the jump for loyal customers, and an internal brief so every rep can answer the angry reply.
What This Skill Produces
- The customer announcement — clear increase, honest reason, effective date, what's not changing
- Grandfathering / transition terms — how existing customers are handled (locked price window, phased, or notice period)
- The FAQ — the hard questions ("why now," "can I lock in," "I'll cancel") with real answers
- The internal brief — talking points and the discount/save guardrails so support and sales are aligned
Required Inputs
Ask for these if not provided:
- The change — old price → new price, which plans, and when it takes effect
- The real reason — new capabilities, cost pressure, repositioning (the honest one, not a spin)
- Customer segments — new vs existing, annual vs monthly, enterprise vs self-serve — terms differ
- The transition — are existing customers grandfathered, phased, or given notice? What's the policy?
- Guardrails — what reps can offer to save an account, and what they can't
Framework: A Price Increase That Holds
- Lead with the number. Say the increase in the first lines; hiding it reads as shame and breeds distrust.
- One true reason. Ideally "we've added X, Y, Z since you signed" — value earns a price. Don't over-justify.
- Soften for loyalty. A price-lock window or phased ramp for existing customers turns a shock into a fair-notice.
- Give a clear date and choice. When it hits, and what they can do (renew early, switch plan, contact us).
- Arm the front line. Support/sales get the FAQ and save-rules before customers do — never after.
Output Format
Customer email
- Subject: [clear, not evasive]
- Body: the increase → the reason (value) → effective date → what's unchanged → their options → thank-you
Show full SKILL.md (204 more words)Show less
Transition terms
- Existing customers: [grandfather window / phased / notice]. New customers: [effective immediately].
FAQ
| Question | Answer |
|---|---|
| Why are prices going up? | … |
| Can I lock in the current price? | … |
| What if I want to cancel? | … |
Internal enablement brief
- Talking points · objection responses · save guardrails (what reps may/may not offer)
Quality Checks
- The new price and effective date are in the first few lines
- The reason is true and value-led, not padded with spin
- Existing-customer transition terms are explicit
- The FAQ answers the cancel/lock-in questions honestly
- The internal brief ships alongside (not after) the customer comms
- Save guardrails are defined so reps don't improvise discounts
Anti-Patterns
- Burying the number in paragraph four — the fastest way to lose trust.
- Over-justifying with a wall of reasons — one true reason beats five defensive ones.
- Blindsiding support — angry replies with no talking points is a self-inflicted wound.
- No transition for loyal customers — a flat overnight jump maximises churn.
- Spin as the reason ("to serve you better") when the truth is cost — customers can tell.
Example Trigger Phrases
- "Announce a price increase to our customers."
- "Write the pricing change email and FAQ."
- "We're raising prices 15% — help me communicate it without a churn spike."
- "Draft customer and internal comms for new pricing."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/price-increase-announcement of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Price Increase Announcement 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 |
|---|---|---|---|---|---|---|
| Price Increase Announcement this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Eol Internal Enablementdeanpeters/Product-Manager-Skills | 7.2k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| 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 mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Price Increase Announcement
What does Price Increase Announcement do?
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. Price Increase Announcement is an agent skill from 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.
When should I use Price Increase Announcement?
Price Increase Announcement fits situations like: asked to announce a price increase; write pricing change comms; raise prices to customers; communicate new pricing.
How do I install Price Increase Announcement in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill price-increase-announcement -a claude-code`. Or copy the skill folder (skills/price-increase-announcement in mohitagw15856/pm-claude-skills) into .claude/skills/price-increase-announcement in your project. Claude Code loads it when a task matches its description.
How do I install Price Increase Announcement in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill price-increase-announcement -a codex`. Or copy the skill folder (skills/price-increase-announcement in mohitagw15856/pm-claude-skills) into .agents/skills/price-increase-announcement in your project. Codex loads it when a task matches its description.
Can I use Price Increase Announcement 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 mohitagw15856/pm-claude-skills --skill price-increase-announcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/price-increase-announcement, .gemini/skills/price-increase-announcement, .github/skills/price-increase-announcement and .opencode/skills/price-increase-announcement in your project.
What does Price Increase Announcement need to run?
SKILL.md names no scripts, command-line tools or credentials: Price Increase Announcement is instructions for the agent only.
Does Price Increase Announcement 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 Price Increase Announcement 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 Price Increase Announcement use?
Price Increase Announcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Price Increase Announcement use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Price Increase Announcement?
Skills that share tags, products or a category with Price Increase Announcement: Eol Internal Enablement (deanpeters/Product-Manager-Skills, 7.2k 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 Price Increase Announcement?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-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.