HTML Ppt Zhangzara Daisy Days
nexu-io/open-design
A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain.
Build a joint customer success plan for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Install Customer Success Plan
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-success-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-success-plan --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/customer-success-plan .claude/skills/customer-success-plan && 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 "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .claude/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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/customer-success-planType 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 customer-success-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-success-plan --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/customer-success-plan .agents/skills/customer-success-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .agents/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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 customer-success-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-success-plan --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/customer-success-plan .cursor/skills/customer-success-plan && 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 "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .cursor/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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/customer-success-plan--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 customer-success-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-success-plan --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/customer-success-plan .gemini/skills/customer-success-plan && 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 "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .gemini/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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 customer-success-planInstalls 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 customer-success-plan -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/customer-success-plan .github/skills/customer-success-plan && 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 "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .github/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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 customer-success-plan -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 customer-success-plan --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/customer-success-plan .opencode/skills/customer-success-plan && 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 "customer-success-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-success-plan into .opencode/skills/customer-success-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-plan", 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
customer-success-plan- GitHub stars
- 1.4k
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,306 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a joint customer success plan for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
- Works in 8 steps: Partnership Objectives → Success Metrics → Milestone Roadmap → …
- Asked to create a success plan
- SKILL.md covers Required Inputs, Output Structure, 1. Partnership Objectives and 2. Success Metrics, plus 11 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Success Plan is an agent skill from mohitagw15856/pm-claude-skills. Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/outcome-contracting.md`, `references/worked-example.md` and `templates/success-plan.md`).
It sits in Sales & Support, covering Customer success and Project management. 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 create a success plan
- Joint success plan
- Mutual action plan
- Customer onboarding plan
Example prompts
- “/customer-success-plan”
Workflow steps
8 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
Customer Success Plan loads about 2.6k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 1,306 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,306 words, ~2,570 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-success-plan/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- customer-success-plan
- description
- Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.
Customer Success Plan Skill
This skill produces a joint customer success plan — a living document shared between the CSM and the customer that aligns on outcomes, milestones, and mutual commitments. Output is ready to co-author with the customer in a kickoff call or QBR.
Required Inputs
Ask the user for these if not provided:
- Account name and industry
- Product / plan purchased
- Key stakeholders — customer champion and economic buyer
- Customer's stated business goals — why did they buy? What problem are they solving?
- Contract term and renewal date
- Current onboarding stage (new customer / expanding / post-QBR / pre-renewal)
- Seats / licenses / usage purchased
- Any known risks — adoption gaps, champion uncertainty, competing priorities
Output Structure
Customer Success Plan: [Account Name]
Product: [Product name / plan tier] Contract term: [Start date → Renewal date] CSM: [Name] Customer champion: [Name, Title] Customer executive sponsor: [Name, Title — if known] Last updated: [Date] Status: [Active / Under review / Completed]
1. Partnership Objectives
What does success look like for [Account Name] at contract end?
[Write 2–3 sentences describing the customer's core objective in plain English — what they are trying to achieve in their business, not what features they are using.]
Primary business goal: [e.g. Reduce time-to-hire by 30% across engineering teams] Secondary goal: [e.g. Consolidate three legacy tools into one platform, saving £X/year] Success statement (customer's words): "[Direct quote from champion about what success looks like — ask for this in kickoff]"
2. Success Metrics
Define how both parties will measure success. Agreed in the kickoff call and tracked in QBRs.
| Metric | Baseline (today) | Target | By when | Data source |
|---|---|---|---|---|
| [e.g. Seat utilisation] | [X%] | [≥ 80%] | [Month 3] | [Product analytics] |
| [e.g. Time to hire] | [X days] | [< Y days] | [Month 6] | [Customer's ATS] |
| [e.g. Reports produced/month] | [X] | [≥ Y] | [Month 3] | [Product analytics] |
| [e.g. NPS] | [X] | [≥ 8] | [Month 6] | [Quarterly survey] |
Leading indicators (early signs the plan is on track):
- [e.g. 5+ users log in within the first 2 weeks]
- [e.g. First workflow automated within 30 days]
- [e.g. Champion presents the tool to their team by end of Month 1]
3. Milestone Roadmap
Break the success journey into phases with clear milestones and owners:
Phase 1: Onboard (Month 1)
| Milestone | Owner | Due date | Status |
|---|---|---|---|
| Admin setup complete (SSO, permissions, data integration) | [IT contact] | [Date] | [ ] |
| All purchased seats activated and users invited | [Champion] | [Date] | [ ] |
| Core workflow [X] configured and tested | [CSM + Champion] | [Date] | [ ] |
| First training session delivered (all teams) | [CSM] | [Date] | [ ] |
| Kickoff call completed and success plan co-signed | [CSM + Champion] | [Date] | [ ] |
Phase 2: Adopt (Months 2–3)
| Milestone | Owner | Due date | Status |
|---|---|---|---|
| [Core feature] in active daily use by ≥ X users | [Champion] | [Date] | [ ] |
| First business outcome achieved and documented | [Champion + CSM] | [Date] | [ ] |
| 30-day check-in completed | [CSM] | [Date] | [ ] |
| [Power user workflow] enabled for advanced users | [CSM] | [Date] | [ ] |
Phase 3: Value (Months 4–6)
| Milestone | Owner | Due date | Status |
|---|---|---|---|
| QBR 1 delivered — ROI evidence presented | [CSM + AE] | [Date] | [ ] |
| Success metric [X] hit target | [Champion] | [Date] | [ ] |
| Expansion use case identified and introduced | [AE] | [Date] | [ ] |
| Reference call or case study agreed | [Champion] | [Date] | [ ] |
Phase 4: Renew & Expand (Months 7–12)
| Milestone | Owner | Due date | Status |
|---|---|---|---|
| QBR 2 delivered — renewal conversation started | [CSM + AE] | [Date] | [ ] |
| Renewal proposal sent | [AE] | [Date] | [ ] |
| Expansion or flat renewal signed | [AE] | [Date] | [ ] |
4. Mutual Commitments
Success plans work when both parties commit. Document what each side will do:
[Vendor] commits to:
- Dedicated CSM available [X days/week / by email within 24 hours]
- Monthly [call / check-in / async update] with champion
- QBR every [90 days] with executive summary and ROI report
- Priority support for [Account] — response SLA of [X hours] for P1 issues
- Roadmap preview for relevant upcoming features
- [Any other specific commitment made in sales cycle]
[Account Name] commits to:
- Champion available for [30-min monthly] check-in
- Users complete onboarding training by [date]
- Feedback on product experience shared monthly (async or sync)
- Executive sponsor participates in QBR 1 and renewal discussion
- Provide outcome data to CSM quarterly for ROI tracking
5. Stakeholder Engagement Plan
| Stakeholder | Role | Engagement frequency | Format | Owner |
|---|---|---|---|---|
| [Champion] | Day-to-day owner | Weekly (async) + Monthly (call) | Slack / Email + Zoom | CSM |
| [Economic buyer] | Budget holder | Quarterly | QBR (in-person or video) | CSM + AE |
| [IT contact] | Integration owner | As needed | CSM | |
| [End users] | Active users | Training only | Group session | CSM |
6. Risk & Mitigation
| Risk | Likelihood | Impact | Mitigation plan |
|---|---|---|---|
| Low adoption in first 30 days | [M] | [H] | CSM hosts live onboarding; champion sends internal comms day 1 |
| Champion changes role | [L] | [H] | Multi-thread: introduce CSM to 2 additional stakeholders by Month 2 |
| Budget pressure at renewal | [M] | [H] | Build ROI case monthly; document value continuously |
| Competing priorities delay rollout | [H] | [M] | Agree minimum viable adoption path with champion; don't require perfection to declare value |
Show full SKILL.md (550 more words)Show less
7. Communication Plan
| Communication | Audience | Frequency | Format | Owner |
|---|---|---|---|---|
| Health update | Champion | Monthly | Email summary (3 bullets: what's good, what needs attention, one ask) | CSM |
| QBR | Champion + Exec | Quarterly | 45-min video call with slide deck | CSM + AE |
| Product updates | Champion | As released | Release notes email | CSM |
| Support status | Champion | When open tickets exist | Email / Slack | Support + CSM |
8. Escalation Path
If the success plan falls off track:
| Trigger | Action | Owner | Timeline |
|---|---|---|---|
| Health drops to Amber | Internal review + champion call within 5 days | CSM | Immediate |
| Health drops to Red | CS leadership + AE looped in; escalation brief drafted | CS Manager | Within 24 hours |
| Champion is unresponsive for >10 days | AE attempts exec sponsor contact | AE | After CSM attempt fails |
| Adoption <40% at Month 3 | Emergency enablement session + revised milestone plan | CSM | Within 1 week of flag |
Deeper Materials
This skill ships with support files — use them when they are available:
references/outcome-contracting.md— Outcome Contracting: Success Plans That Bind Both Sides. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/success-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 |
|---|---|---|---|
| Outcome orientation | All metrics are vendor-controlled product-usage numbers | Customer business metrics present but missing baselines, targets, or data sources | Customer business outcomes with baseline, target, date, and data source — plus leading indicators |
| Ownership & dates | Owners blank, "CS team", or dates left TBD | Owners named on the vendor side only; customer-side milestones unowned | Every milestone has a named owner on the correct side of the table and a confirmed date |
| Mutuality | Reads as the vendor's internal to-do list | Customer commitments listed but vague or clearly not agreed | Both sides carry concrete commitments; executive sponsor has a named engagement role; shareable as written |
| Risk realism | No risk register | Generic risks; champion departure and low adoption missing | Includes champion departure and low adoption with mitigations, owners, and escalation triggers |
Quality Checks
- Success metrics are the customer's metrics — not just product usage metrics
- Milestones have specific owners and due dates — not "TBD"
- Mutual commitments section is genuinely mutual — not just what the vendor will do
- Risk register includes champion departure and low adoption
- Plan is written to be shared with the customer — no internal-only commentary in this document
- Executive sponsor is identified and has an engagement role
Anti-Patterns
- Do not define success metrics that the vendor controls — metrics must reflect the customer's business outcomes
- Do not set milestone dates without customer confirmation — unilateral timelines undermine joint ownership
- Do not create a plan the customer hasn't agreed to — it must be mutual, not a CSM's internal plan
- Do not leave ownership fields blank or assigned to "CS team" — every action needs a named owner
- Do not confuse product adoption milestones with customer business outcomes — both are needed but are not the same
Example Trigger Phrases
- "Build a success plan for [Account Name] who just signed"
- "Create a joint success plan for our new enterprise customer"
- "Write a 6-month customer success roadmap for [Company]"
- "I need a mutual action plan for our QBR with [Account]"
- "Generate a customer success plan for an at-risk 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/customer-success-plan of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/outcome-contracting.md
- references/worked-example.md
- templates/success-plan.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Customer Success Plan 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 |
|---|---|---|---|---|---|---|
| Customer Success Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.6k | Automated safety check: Pass | MIT | |
| HTML Ppt Zhangzara Daisy Daysnexu-io/open-design | 100k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Customer Statustechwolf-ai/ai-first-toolkit | 132 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Onboarding Playbook Creationseb1n/awesome-ai-agent-skills | 206 | — | ~2.4k | 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 |
Similar skills
Customer Status
techwolf-ai/ai-first-toolkit
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
Onboarding Playbook Creation
seb1n/awesome-ai-agent-skills
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
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…
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.
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 Customer Success Plan
What does Customer Success Plan do?
Build a joint customer success plan for a specific account. An agent skill from mohitagw15856/pm-claude-skills. Customer Success Plan is an agent skill from mohitagw15856/pm-claude-skills. Build a joint customer success plan for a specific account.
When should I use Customer Success Plan?
Customer Success Plan fits situations like: asked to create a success plan; joint success plan; mutual action plan; customer onboarding plan.
How do I install Customer Success Plan in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-success-plan -a claude-code`. Or copy the skill folder (skills/customer-success-plan in mohitagw15856/pm-claude-skills) into .claude/skills/customer-success-plan in your project. Claude Code loads it when a task matches its description.
How do I install Customer Success Plan in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-success-plan -a codex`. Or copy the skill folder (skills/customer-success-plan in mohitagw15856/pm-claude-skills) into .agents/skills/customer-success-plan in your project. Codex loads it when a task matches its description.
Can I use Customer Success Plan 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 customer-success-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-success-plan, .gemini/skills/customer-success-plan, .github/skills/customer-success-plan and .opencode/skills/customer-success-plan in your project.
What does Customer Success Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Success Plan is instructions for the agent only.
Does Customer Success Plan 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 Customer Success Plan 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 Customer Success Plan use?
Customer Success Plan 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 Customer Success Plan use?
About 2.6k tokens (SKILL.md is roughly 10k 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 4k tokens, read only when the agent opens those files.
What are the alternatives to Customer Success Plan?
Skills that share tags, products or a category with Customer Success Plan: HTML Ppt Zhangzara Daisy Days (nexu-io/open-design, 100k stars), Customer Status (techwolf-ai/ai-first-toolkit, 132 stars), Onboarding Playbook Creation (seb1n/awesome-ai-agent-skills, 206 stars) and Youtube Search (ZeroPointRepo/youtube-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Success Plan?
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.