Eol Internal Enablement
deanpeters/Product-Manager-Skills
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
Design and roll out a price increase or packaging change without triggering churn.
Install Pricing Change Strategist
$ npx skills add OneWave-AI/claude-skills --skill pricing-change-strategist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OneWave-AI/claude-skills pricing-change-strategist --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/OneWave-AI/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pricing-change-strategist .claude/skills/pricing-change-strategist && 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 "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .claude/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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/OneWave-AI/claude-skills/tree/main/pricing-change-strategistType 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 OneWave-AI/claude-skills --skill pricing-change-strategist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OneWave-AI/claude-skills pricing-change-strategist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pricing-change-strategist .agents/skills/pricing-change-strategist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .agents/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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 OneWave-AI/claude-skills --skill pricing-change-strategist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OneWave-AI/claude-skills pricing-change-strategist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pricing-change-strategist .cursor/skills/pricing-change-strategist && 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 "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .cursor/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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/OneWave-AI/claude-skills.git --path pricing-change-strategist--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 OneWave-AI/claude-skills --skill pricing-change-strategist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OneWave-AI/claude-skills pricing-change-strategist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pricing-change-strategist .gemini/skills/pricing-change-strategist && 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 "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .gemini/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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 OneWave-AI/claude-skills pricing-change-strategistInstalls 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 OneWave-AI/claude-skills --skill pricing-change-strategist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pricing-change-strategist .github/skills/pricing-change-strategist && 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 "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .github/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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 OneWave-AI/claude-skills --skill pricing-change-strategist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OneWave-AI/claude-skills pricing-change-strategist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pricing-change-strategist .opencode/skills/pricing-change-strategist && 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 "pricing-change-strategist" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/pricing-change-strategist into .opencode/skills/pricing-change-strategist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pricing-change-strategist", 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
pricing-change-strategist- GitHub stars
- 336
- Token cost
- ~1.2k tokens
- SKILL.md length
- 492 words
- Files
- 1
- Skills in repo
- 69
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design and roll out a price increase or packaging change without triggering churn.
- Works in 6 steps: Establish the baseline → Segment by price sensitivity → Model the scenarios → …
- Repackaging tiers
- SKILL.md covers Step 1 — Establish the baseline, Step 2 — Segment by price…, Step 3 — Model the scenarios and Step 4 — Decide the policy, plus 3 more sections
- Needs SUPABASE_TOKEN
What it does
Pricing Change Strategist is an agent skill from OneWave-AI/claude-skills. Design and roll out a price increase or packaging change without triggering churn. Segments the base by price sensitivity, models revenue and churn scenarios, decides grandfathering and notice strategy, and produces the full comms kit (customer email, in-app notice, sales talk track, support FAQ, objection handling). Use when raising prices, repackaging tiers, or moving customers to new plans.
Its SKILL.md is about 1.2k 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 Sales enablement and Help center and FAQ content. The repository describes itself as: 200+ production-ready Claude Code skills for sales, marketing, design, engineering, and AI agent architecture. Built and maintained by OneWave AI. The licence is MIT.
When your agent uses it
- Repackaging tiers
- Moving customers to new plans
Example prompts
- “/pricing-change-strategist”
Requirements
- A credential in SUPABASE_TOKEN
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fc5b785. 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
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SUPABASE_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pricing Change Strategist loads about 1.2k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 492 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 OneWave-AI/claude-skills at commit fc5b785, republished under its MIT licence (© OneWave-AI). 492 words, ~1,219 tokens.
Download SKILL.mdSave it as
.claude/skills/pricing-change-strategist/SKILL.md (or your agent's skills folder).- name
- pricing-change-strategist
- description
- Design and roll out a price increase or packaging change without triggering churn. Segments the base by price sensitivity, models revenue and churn scenarios, decides grandfathering and notice strategy, and produces the full comms kit (customer email, in-app notice, sales talk track, support FAQ, objection handling). Use when raising prices, repackaging tiers, or moving customers to new plans.
- tools
- Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, Agent
- model
- inherit
Pricing Change Strategist
Raising prices is the highest-leverage move most companies are too scared to make well. Done carelessly it churns your base and lights up Twitter. Done well it's nearly pure margin. This skill plans the change end to end — the math, the segmentation, the grandfathering call, and every word customers will read.
Pair it with product-launch-war-room (to decide whether) and customer-panel-of-experts (to hear how each segment reacts). This skill owns the how.
Step 1 — Establish the baseline
Gather (read-only from billing/CRM where connected — Stripe, Mercury, Supabase via $SUPABASE_TOKEN; otherwise ask):
- Current pricing, tiers, and discount reality (list vs. actual realized).
- Revenue distribution: ACV by segment, concentration, % on legacy/grandfathered plans.
- Churn and expansion rates by segment.
- Cost-to-serve by tier (where the margin actually is).
- The trigger: why now — cost, value delivered, repositioning, market.
Security: read-only. Never modify subscriptions, prices, or send anything. No real customer PII in artifacts — segment in aggregate. Secrets in env vars only.
Step 2 — Segment by price sensitivity
Split the base into action groups, e.g.:
- Anchor accounts — high revenue, high switching cost → can absorb increase, handle white-glove.
- Price-sensitive core — value-conscious, mobile → highest churn risk, needs the strongest value story.
- Legacy / underpriced — paying far below current value → biggest opportunity, biggest betrayal risk.
- At-risk — already low engagement → may use the increase as an exit cue; decide if you want to keep them.
For each: current price, proposed price, % change, estimated churn response, net revenue impact.
Step 3 — Model the scenarios
Build a simple, transparent model (write it out so the math is auditable — never hand-wave aggregates):
- Conservative / expected / aggressive increase levels.
- For each: projected churn %, retained revenue, net new revenue, payback on any concessions.
- The break-even churn: how much churn the increase can absorb before it's net-negative.
- Sensitivity: which assumption the outcome hinges on most.
State assumptions explicitly and label them assumptions. If billing data is connected, ground the model in real numbers and cite them; if not, mark it as estimated and tell the user what data would tighten it.
Show full SKILL.md (158 more words)Show less
Step 4 — Decide the policy
- Grandfathering: none / time-boxed / permanent for anchors — with the revenue trade-off of each.
- Notice period: how much warning (longer for larger increases / annual contracts).
- Migration path: how legacy plans move, and the off-ramp for those who won't.
- Concessions: annual-prepay discount, lock-in window, feature sweetener to soften the change.
- Sequencing: new customers first → expansions → renewals → existing base, or a clean date.
Step 5 — Produce the comms kit
# Price Change Plan — {Company}
Generated: {timestamp} · Grounding: {billing-data / estimated}
## Recommendation
Increase {X%} on {segments}, {grandfathering policy}, {notice}, effective {date}.
Expected: +{$} net revenue, {Y%} churn risk, break-even at {Z%} churn.
## Segment plan (table)
## Scenario model (table + assumptions)
## Rollout timeline & sequencing
## Risk register & rollback triggers
## Comms — ready to send
### Customer email (warm, value-first, no apology-for-existing tone)
### In-app / banner notice
### Sales talk track (for accounts that push back)
### Support FAQ + objection handling ("why is it going up", "I'll cancel", "match my old price")
### Internal brief (so the team answers consistently)Lead every customer-facing message with value delivered, then the change, then the path forward — never apologize for charging fairly. Match the user's voice: direct, confident, no corporate fluff.
Step 6 — Pressure-test
Offer to run the email and talk track through prospect-panel-simulator / customer-panel-of-experts before sending, and to set the rollback triggers as a monitoring checklist.
Guardrails recap
Read-only on billing — never change a subscription · model is transparent and assumptions are labeled · grandfathering and rollback are explicit decisions · comms lead with value, never apology · no real customer PII in artifacts.
© OneWave-AI, 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 pricing-change-strategist of OneWave-AI/claude-skills.
Open the folder on GitHubat commit fc5b785
Compare with similar skills
Pricing Change Strategist 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 |
|---|---|---|---|---|---|---|
| Pricing Change Strategist this skillOneWave-AI/claude-skills | 336 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Eol Internal Enablementdeanpeters/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 | |
| 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
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.
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 OneWave-AI/claude-skills
All 69 skills in this repoCRM Data Cleanup
OneWave-AI/claude-skills
Finds duplicate and junk records in a CRM CSV export with fuzzy matching, normalizes fields and writes a reviewable merge plan plus import-ready files without touching the live CRM.
Design Export Repair
OneWave-AI/claude-skills
Repairs broken decks and PDFs exported from Claude Design or similar AI deck generators: clipped text, wrong fonts and corrupted .pptx package structure.
Bi Measure Builder
OneWave-AI/claude-skills
Writes, explains, debugs, and optimizes BI calculations - Power BI / Fabric DAX measures and calculated columns, Tableau calculated fields (FIXED/INCLUDE/EXCLUDE LOD expressions, table…
Bookkeeping Close
OneWave-AI/claude-skills
Categorizes transactions, reconciles bank and card statements to the ledger, works a month-end checklist and prepares a close package, without ever forcing a balance.
CSV and Excel Merger
OneWave-AI/claude-skills
Combines CSV, TSV and Excel files into one verified table with pandas, by stacking or joining, mapping columns, normalizing keys and removing duplicates.
Sec Filing Puller
OneWave-AI/claude-skills
Pulls financial statement numbers for US public companies straight from SEC EDGAR's free official XBRL APIs (companyfacts, companyconcept, frames, submissions) into a cited table.
Related
Categories
Questions about Pricing Change Strategist
What does Pricing Change Strategist do?
Design and roll out a price increase or packaging change without triggering churn. Pricing Change Strategist is an agent skill from OneWave-AI/claude-skills. Design and roll out a price increase or packaging change without triggering churn.
When should I use Pricing Change Strategist?
Pricing Change Strategist fits situations like: repackaging tiers; moving customers to new plans.
How do I install Pricing Change Strategist in Claude Code?
Run `npx skills add OneWave-AI/claude-skills --skill pricing-change-strategist -a claude-code`. Or copy the skill folder (pricing-change-strategist in OneWave-AI/claude-skills) into .claude/skills/pricing-change-strategist in your project. Claude Code loads it when a task matches its description.
How do I install Pricing Change Strategist in Codex?
Run `npx skills add OneWave-AI/claude-skills --skill pricing-change-strategist -a codex`. Or copy the skill folder (pricing-change-strategist in OneWave-AI/claude-skills) into .agents/skills/pricing-change-strategist in your project. Codex loads it when a task matches its description.
Can I use Pricing Change Strategist 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 OneWave-AI/claude-skills --skill pricing-change-strategist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pricing-change-strategist, .gemini/skills/pricing-change-strategist, .github/skills/pricing-change-strategist and .opencode/skills/pricing-change-strategist in your project.
What does Pricing Change Strategist need to run?
Going by SKILL.md and its folder, Pricing Change Strategist needs credentials named SUPABASE_TOKEN. Our summary lists: A credential in SUPABASE_TOKEN.
Does Pricing Change Strategist 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 Pricing Change Strategist 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 Pricing Change Strategist use?
Pricing Change Strategist 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 Pricing Change Strategist use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Pricing Change Strategist?
Skills that share tags, products or a category with Pricing Change Strategist: Eol Internal Enablement (deanpeters/Product-Manager-Skills, 7.2k stars), Price Increase Announcement (mohitagw15856/pm-claude-skills, 1.4k 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 Pricing Change Strategist?
OneWave-AI (a GitHub organization) maintains it in OneWave-AI/claude-skills, which has 336 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.
Source: OneWave-AI/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.