Youtube Search
ZeroPointRepo/youtube-skills
A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…
Build a structured renewal playbook for a customer account. An agent skill from mohitagw15856/pm-claude-skills.
Install Renewal Playbook
$ npx skills add mohitagw15856/pm-claude-skills --skill renewal-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills renewal-playbook --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/renewal-playbook .claude/skills/renewal-playbook && 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 "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .claude/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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/renewal-playbookType 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 renewal-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills renewal-playbook --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/renewal-playbook .agents/skills/renewal-playbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .agents/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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 renewal-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills renewal-playbook --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/renewal-playbook .cursor/skills/renewal-playbook && 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 "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .cursor/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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/renewal-playbook--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 renewal-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills renewal-playbook --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/renewal-playbook .gemini/skills/renewal-playbook && 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 "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .gemini/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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 renewal-playbookInstalls 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 renewal-playbook -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/renewal-playbook .github/skills/renewal-playbook && 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 "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .github/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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 renewal-playbook -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 renewal-playbook --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/renewal-playbook .opencode/skills/renewal-playbook && 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 "renewal-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/renewal-playbook into .opencode/skills/renewal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renewal-playbook", 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
renewal-playbook- GitHub stars
- 1.4k
- Token cost
- ~3k tokens
- SKILL.md length
- 1,534 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a structured renewal playbook for a customer account. An agent skill from mohitagw15856/pm-claude-skills.
- Works in 9 steps: Account Health Snapshot → Stakeholder Map → Risk Register → …
- Asked to plan a renewal
- SKILL.md covers Required Inputs, Output Structure, 1. Account Health Snapshot and 2. Stakeholder Map, plus 12 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Renewal Playbook is an agent skill from mohitagw15856/pm-claude-skills. Build a structured renewal playbook for a customer account. Use when asked to plan a renewal, structure a renewal negotiation, prepare for an expansion conversation, or build a renewal strategy for at-risk or healthy accounts. Produces a renewal brief with health assessment, negotiation strategy, objection responses, expansion levers, and a timeline.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/risk-timeline.md`, `references/worked-example.md` and `templates/renewal-plan.md`).
It sits in Sales & Support, covering Customer success. 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 plan a renewal
- Structure a renewal negotiation
- Prepare for an expansion conversation
- Build a renewal strategy for at-risk
Example prompts
- “/renewal-playbook”
Workflow steps
9 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 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
Renewal Playbook loads about 3k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 1,534 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). 1,534 words, ~3,023 tokens.
Download SKILL.mdSave it as
.claude/skills/renewal-playbook/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- renewal-playbook
- description
- Build a structured renewal playbook for a customer account. Use when asked to plan a renewal, structure a renewal negotiation, prepare for an expansion conversation, or build a renewal strategy for at-risk or healthy accounts. Produces a renewal brief with health assessment, negotiation strategy, objection responses, expansion levers, and a timeline.
Renewal Playbook Skill
This skill produces a complete renewal playbook for a specific customer account, covering health assessment, commercial strategy, negotiation preparation, expansion opportunity mapping, and a step-by-step timeline. Output is ready for the CSM or account team to execute 90–180 days before renewal.
Required Inputs
Ask the user for these if not provided:
- Account name
- Renewal date
- Current ARR and proposed renewal ARR (if different)
- Account health — RAG status and main reasons (or describe the account situation)
- Key stakeholders — economic buyer, champion, and any detractors
- Renewal risk factors — budget pressure, low adoption, competitive threat, champion departure, etc.
- Expansion opportunity — any upsell or cross-sell potential?
- Contract terms — current plan, duration, and any terms up for renegotiation
Output Structure
Renewal Playbook: [Account Name]
Renewal date: [Date] Current ARR: [£/$/€ X] Target renewal ARR: [£/$/€ X — flat / +X% expansion / contraction risk] Health status: [Green / Amber / Red] CSM: [Name] Account executive: [Name] Days to renewal: [X days]
1. Account Health Snapshot
| Dimension | Score (1–5) | Evidence |
|---|---|---|
| Product adoption | [X/5] | [e.g. 3 of 5 purchased seats active; core feature used weekly] |
| Business outcomes | [X/5] | [e.g. Customer reports X% improvement in [metric]; no formal ROI review done] |
| Relationship depth | [X/5] | [e.g. Strong champion in [name/role]; limited exec sponsorship] |
| Support & satisfaction | [X/5] | [e.g. 2 open P2 tickets; last NPS 7; no escalations in 6 months] |
| Commercial engagement | [X/5] | [e.g. Invoice paid on time; no discount pressure raised yet] |
| Overall health | [X/5 — weighted] | [Green / Amber / Red] |
Renewal thesis: [One sentence: why this account will renew — or what must change for it to renew.]
2. Stakeholder Map
| Stakeholder | Role | Influence | Sentiment | Our relationship |
|---|---|---|---|---|
| [Name] | Economic buyer | High | [Positive / Neutral / Negative] | [Warm / Cold / Unknown] |
| [Name] | Champion | High | [Positive] | [Warm] |
| [Name] | End user | Low | [Neutral] | [Limited] |
| [Name] | IT / procurement | Medium | [Neutral] | [Transactional] |
Champion risk: [Is our champion secure in their role? Any signals of departure or reorganisation?]
Multi-thread plan: [Who else do we need relationships with before renewal? How do we get there?]
3. Risk Register
| Risk | Likelihood (H/M/L) | Impact (H/M/L) | Mitigation |
|---|---|---|---|
| [Budget pressure / cost-cutting] | [H] | [H] | [Build ROI case 90 days out; identify budget holder's priorities] |
| [Low adoption in [department]] | [M] | [H] | [Run targeted enablement session; tie to champion's OKRs] |
| [Competitor evaluation] | [M] | [M] | [Request competitive intelligence; schedule exec-level call] |
| [Champion departure] | [L] | [H] | [Map two additional stakeholders; executive intro call] |
4. Value Story
Build the ROI narrative for the renewal conversation:
Headline result: [e.g. "[Account] saved X hours/week or reduced [metric] by X% using [product]"]
Evidence sources:
- Product usage data (logins, features used, seat utilisation)
- Business metric improvement (pull from QBR deck or success plan)
- Support resolution time improvement
- Customer-provided testimonial or case study quotes
Value gaps to close before renewal: [Are there outcomes the customer expected but hasn't seen yet? What's the plan to close these?]
5. Expansion Opportunity
Map upside beyond flat renewal:
| Opportunity | Type | Estimated value | Likelihood | Timing |
|---|---|---|---|---|
| [Seat expansion — [dept] wants to add 10 users] | Upsell | [+£X ARR] | [High] | [Renewal or +3M] |
| [Cross-sell — [Product B] use case identified] | Cross-sell | [+£X ARR] | [Medium] | [+6M] |
| [Multi-year commitment] | Discount for term | [+£X TCV / -X% discount] | [Low] | [At renewal] |
Expansion play: [Which opportunity to lead with, and the sequence for raising it in the renewal conversation]
6. Commercial Strategy
Renewal scenario planning:
| Scenario | Probability | ARR outcome | Response strategy |
|---|---|---|---|
| Flat renewal | [X%] | [£X — same as current] | [Accept; plant seeds for +6M expansion] |
| Expansion | [X%] | [£X] | [Lead with ROI evidence; pitch seat or feature expansion] |
| Contraction risk | [X%] | [£X — downgrade to lower tier] | [Propose phased commitment; demonstrate path to full adoption] |
| Churn risk | [X%] | [£0] | [Escalate to leadership; executive sponsor engagement] |
Discount guardrails:
- Floor discount: [X% — do not go below without VP approval]
- Triggers for discount: [Multi-year / volume / reference customer commitment]
- What to ask for in return: [Reference case study / G2 review / executive intro / case study participation]
Pricing flexibility:
- [e.g. Can offer monthly billing in exchange for 24-month commit]
- [e.g. Can offer X seats free in exchange for expansion commitment]
7. Objection Responses
Prepare for the most likely objections:
"The price is too high"
Anchor on value delivered: "[Customer] achieved [X outcome] — at [£X ARR], that's [£Y per outcome / hour saved / user]. What would it cost to deliver that outcome without us?" If budget is genuinely constrained, explore: phased payment, reduction in scope rather than full churn, multi-year pricing.
"We're not seeing enough adoption"
Acknowledge, then commit: "You're right — [X seats] are actively using [core feature] out of [Y]. We want to fix this. Here's our 60-day plan: [exec sponsor on enablement call / training session / in-product nudge campaign]."
"We're evaluating [Competitor]"
Don't panic. Ask: "What's driving the evaluation — is it specific features, pricing, or something else?" Then map gaps honestly. Offer a feature roadmap preview if relevant. Get clarity on their criteria and timeline before responding defensively.
"We need to reduce spend this quarter"
Separate the commercial conversation from the value conversation. Offer to protect the relationship with a reduced scope today with a committed expansion trigger at a business milestone. Avoid discounting without a reason.
8. Renewal Timeline
| Week | Action | Owner | Notes |
|---|---|---|---|
| W–16 (4 months out) | Internal renewal review — health, expansion opportunity, risk | CSM | Flag to leadership if Red |
| W–12 | QBR / executive business review — ROI evidence delivered | CSM + AE | Book 45–60 min with economic buyer |
| W–10 | Champion 1:1 — pulse check on satisfaction and upcoming priorities | CSM | Uncover internal dynamics before commercial discussion |
| W–8 | Expansion conversation — plant seeds, share roadmap | AE | Do not lead with pricing |
| W–6 | Send renewal proposal — pricing, terms, options | AE | Include multi-year option |
| W–4 | Negotiation — address objections, finalise commercial terms | AE + CSM | Escalate to VP if >X% discount required |
| W–2 | Legal / procurement — contract redlines, signature process | AE + Legal | |
| W–0 | Signed. Handoff to post-renewal success plan | CSM | Thank the champion; begin next cycle |
Show full SKILL.md (591 more words)Show less
9. Success Criteria
- Renewal signed before deadline
- ARR outcome within target range
- Champion relationship maintained or improved
- At least one expansion conversation started
- ROI evidence documented and accepted by customer
Deeper Materials
This skill ships with support files — use them when they are available:
references/risk-timeline.md— The Renewal Clock: What Happens at T-minus-When. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/renewal-plan.md— a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Health honesty | Target ARR asserted with no health assessment, or a Red/Amber account given a flat-renewal plan on hope | Health snapshot present with evidence, but the renewal thesis and target ARR don't fully follow from it (e.g. shelfware acknowledged, target still flat) | Every dimension score cites evidence, the renewal thesis follows from the health picture, and the target ARR reflects reality — including recommending contraction or right-sizing when that is the honest play |
| Stakeholder & risk coverage | Champion-only view; economic buyer unmapped; risks are generic labels without mitigations | Economic buyer mapped but relationship gaps unaddressed; H/H risks listed but some mitigations are vague or unowned | Economic buyer, detractors, and champion risk all assessed with a concrete multi-thread plan; every H/H risk has a dated, owned, pre-emptive mitigation that reappears in the timeline |
| Commercial rigor | No scenario planning; discounting is the first and only lever; no floor or approval gate | Scenarios present but probabilities don't sum to 100% or ARR figures don't reconcile to contract components; floor exists but no ask-in-return framework | Scenario probabilities sum to 100%, every ARR figure decomposes into real contract line items, discount floor and escalation gate are explicit, and each concession names what we get in return |
| Timeline & objection specificity | No timeline, or one starting under 90 days without acknowledgment; objection responses are boilerplate | Timeline covers 90+ days with owners, but objections could apply to any account; genuine dissatisfaction and negotiating tactics handled identically | Timeline starts 90+ days out (or explicitly flags and compresses when late) with owners per step, and every objection response uses this account's actual numbers, distinguishing real dissatisfaction to resolve from tactics to negotiate |
Quality Checks
- Stakeholder map includes the economic buyer — not just the champion
- Risk register has a mitigation for every H/H risk
- Value story uses product data and business outcomes, not just feature lists
- Commercial strategy includes a floor discount and a reason-to-discount framework
- Timeline starts at least 90 days before renewal date
- Objection responses are specific to this account, not generic
Anti-Patterns
- Do not start renewal conversations less than 90 days before the renewal date for accounts over $50K ARR
- Do not build a renewal strategy without first honestly assessing account health — wishful thinking leads to last-minute churn
- Do not treat all renewal objections as negotiating tactics — some objections signal genuine dissatisfaction that requires resolution first
- Do not offer discounts as the first response to price objections — explore value gaps before reducing price
- Do not close the renewal without confirming the expansion opportunity — every renewal is also an expansion conversation
Example Trigger Phrases
- "Build a renewal playbook for [Account Name] renewing in [Month]"
- "Help me plan the renewal strategy for an at-risk customer"
- "Prepare a renewal brief for my QBR with [Company]"
- "What's my renewal strategy for a Red account coming up in 60 days?"
- "Create a renewal and expansion plan for [Account]"
© 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
SKILL.md and 3 other files (references) in skills/renewal-playbook of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/risk-timeline.md
- references/worked-example.md
- templates/renewal-plan.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Renewal Playbook 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 |
|---|---|---|---|---|---|---|
| Renewal Playbook this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~3k | Automated safety check: Pass | MIT | |
| Youtube SearchZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| YtZeroPointRepo/youtube-skills | 1k | 1 repos | ~951 | Automated safety check: Pass | MIT | |
| Account PlanBevel-Software/Hexis | 100 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Loki Modedavila7/claude-code-templates | 33k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Yt
ZeroPointRepo/youtube-skills
A skill your agent uses when YouTube is relevant: pasted video links or IDs, @handles, quick video lookups, summaries, channel latest uploads, topic search, or any request involving YouTube content…
Account Plan
Bevel-Software/Hexis
Build or refresh a strategic account plan - current state, goals, stakeholder coverage, opportunity map, risks, and the action plan - written to a doc and key fields synced to the CRM.
Loki Mode
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
Expansion Retention
tech-leads-club/agent-skills
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.
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 Renewal Playbook
What does Renewal Playbook do?
Build a structured renewal playbook for a customer account. An agent skill from mohitagw15856/pm-claude-skills. Renewal Playbook is an agent skill from mohitagw15856/pm-claude-skills. Build a structured renewal playbook for a customer account.
When should I use Renewal Playbook?
Renewal Playbook fits situations like: asked to plan a renewal; structure a renewal negotiation; prepare for an expansion conversation; build a renewal strategy for at-risk.
How do I install Renewal Playbook in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill renewal-playbook -a claude-code`. Or copy the skill folder (skills/renewal-playbook in mohitagw15856/pm-claude-skills) into .claude/skills/renewal-playbook in your project. Claude Code loads it when a task matches its description.
How do I install Renewal Playbook in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill renewal-playbook -a codex`. Or copy the skill folder (skills/renewal-playbook in mohitagw15856/pm-claude-skills) into .agents/skills/renewal-playbook in your project. Codex loads it when a task matches its description.
Can I use Renewal Playbook 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 renewal-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/renewal-playbook, .gemini/skills/renewal-playbook, .github/skills/renewal-playbook and .opencode/skills/renewal-playbook in your project.
What does Renewal Playbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Renewal Playbook is instructions for the agent only.
Does Renewal Playbook 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 Renewal Playbook 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 Renewal Playbook use?
Renewal Playbook 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 Renewal Playbook use?
About 3k 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. Its references folder adds about 4.1k tokens, read only when the agent opens those files.
What are the alternatives to Renewal Playbook?
Skills that share tags, products or a category with Renewal Playbook: Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars), Account Plan (Bevel-Software/Hexis, 100 stars) and Loki Mode (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Renewal Playbook?
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.