Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization.
Install Customer Success And Retention
$ npx skills add manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin customer-success-and-retention --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/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/customer-success-and-retention .claude/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .claude/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retentionType 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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin customer-success-and-retention --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/customer-success-and-retention .agents/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .agents/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin customer-success-and-retention --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/customer-success-and-retention .cursor/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .cursor/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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/manojbajaj95/claude-gtm-plugin.git --path skills/customer-success-and-retention--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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin customer-success-and-retention --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/customer-success-and-retention .gemini/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .gemini/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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 manojbajaj95/claude-gtm-plugin customer-success-and-retentionInstalls 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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/customer-success-and-retention .github/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .github/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin customer-success-and-retention --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/customer-success-and-retention .opencode/skills/customer-success-and-retention && 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-and-retention" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/customer-success-and-retention into .opencode/skills/customer-success-and-retention/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-and-retention", 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-and-retention- GitHub stars
- 105
- Token cost
- ~3k tokens
- SKILL.md length
- 1,219 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization.
- Works in 7 steps: Map customer goals and success criteria → Define key milestones and timeline → Create onboarding checklist → …
- Designing customer onboarding flows
- SKILL.md covers Workspace Context, Operating Contract, Quick Reference and Part 1: Core Principles, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Success And Retention is an agent skill from manojbajaj95/claude-gtm-plugin. Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization. Use when designing customer onboarding flows, reducing churn, building health scores, creating retention systems, designing upsells, or improving customer lifetime value. Covers proactive engagement, cancel flows, dunning, re-engagement, and the full customer lifecycle.
Its SKILL.md is about 3k 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 Customer success. The licence is MIT.
When your agent uses it
- Designing customer onboarding flows
- Building health scores
- Creating retention systems
- Designing upsells
Example prompts
- “/customer-success-and-retention”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Map customer goals and success criteria
- Define key milestones and timeline
- Create onboarding checklist
- Design enablement content
- Set up automated touchpoints
- Define handoff from sales
- Measure time-to-value
What it can do on your machine
Read from SKILL.md and the folder at commit 0830a46. 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 And Retention loads about 3k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 1,219 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 manojbajaj95/claude-gtm-plugin at commit 0830a46, republished under its MIT licence (© manojbajaj95). 1,219 words, ~2,984 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-success-and-retention/SKILL.md (or your agent's skills folder).- name
- customer-success-and-retention
- description
- Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization. Use when designing customer onboarding flows, reducing churn, building health scores, creating retention systems, designing upsells, or improving customer lifetime value. Covers proactive engagement, cancel flows, dunning, re-engagement, and the full customer lifecycle.
- metadata.version
- 1.0.0
- metadata.merged_from
- customer-success-manager, customer-success, churn-prevention, retain, retention-engine
Customer Success & Retention
Workspace Context
Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.
Operating Contract
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Comprehensive framework for customer success, retention, and lifetime value maximization.
Quick Reference
| Situation | Use This Skill For |
|---|---|
| Designing onboarding flows | Onboarding Excellence |
| Reducing churn | Churn Prevention & Recovery |
| Building health monitoring | Health Score Models |
| Improving LTV | Retention & Ascension |
| Cancel flow optimization | Cancel Flow Design |
| Payment failures | Dunning & Recovery |
Part 1: Core Principles
Time to Value Is Everything
The faster users get value, the more likely they stick. Measure and optimize time to first value moment. Remove every obstacle between signup and aha moment.
Proactive Beats Reactive
Reach out before problems escalate. Health scores predict churn before it happens. Intervention when metrics dip is worth 10x intervention after cancellation request.
Segment for Relevance
Not all customers are the same. High-touch for enterprise, tech-touch for SMB, self-serve for individuals. Match effort to customer value and needs.
Measure Leading Indicators
Revenue is a lagging indicator. Track: engagement, feature adoption, support tickets, NPS changes.
Make Expansion Natural
Upselling should feel like helping, not selling. When customers outgrow their tier, expansion is a solution.
Part 2: Customer Onboarding Design
Onboarding Workflow
- Map customer goals and success criteria
- Define key milestones and timeline
- Create onboarding checklist
- Design enablement content
- Set up automated touchpoints
- Define handoff from sales
- Measure time-to-value
Activation Milestones
| Milestone | Target Time | D30 Retention Impact |
|---|---|---|
| Account created | T+0 | Baseline |
| Profile complete | T+5 min | +8% |
| First core action | T+24 hr | +15% |
| First value experience | T+3 days | +25% |
| 3-day active streak | T+7 days | +35% |
Onboarding Patterns
| Approach | Best For | Risk |
|---|---|---|
| Product-first | Simple products, B2C | Blank slate overwhelm |
| Guided setup | Products needing personalization | Friction before value |
| Value-first | Products with demo data | May not feel "real" |
Part 3: Health Scoring
Customer Health Score (100 points)
| Dimension | Weight | Signals |
|---|---|---|
| Usage frequency | 25% | DAU/MAU ratio, sessions, last login |
| Feature depth | 20% | Feature adoption %, core feature use |
| Engagement | 20% | Time on app, actions per session |
| Satisfaction | 15% | NPS, CSAT, support sentiment |
| Growth | 10% | Seat additions, plan upgrades |
| Relationship | 10% | Community participation, referrals |
Health Score Thresholds
| Score | Status | Action |
|---|---|---|
| 80-100 | Healthy | Upsell opportunities |
| 60-79 | Stable | Monitor |
| 40-59 | At Risk | Automated intervention |
| 0-39 | Critical | Human outreach |
Churn Risk Scoring
| Level | Score | Action |
|---|---|---|
| Low | 0-29 | Continue normal engagement |
| Medium | 30-49 | Automated re-engagement |
| High | 50-69 | Personalized intervention |
| Critical | 70+ | Human outreach (call/email) |
Part 4: Churn Prevention
Churn Types & Solutions
| Type | Cause | Solution |
|---|---|---|
| Voluntary | Customer chooses to cancel | Cancel flows, save offers, exit surveys |
| Involuntary | Payment fails | Dunning emails, smart retries, card updaters |
Voluntary churn is typically 50-70% of total. Involuntary is 30-50% but easier to fix.
Risk Signals
| Signal | Risk Level | Timeframe |
|---|---|---|
| Login frequency drops 50%+ | High | 2-4 weeks before cancel |
| Key feature usage stops | High | 1-3 weeks before cancel |
| Support tickets spike then stop | High | 1-2 weeks before cancel |
| Billing page visits increase | High | Days before cancel |
| Team seats removed | High | 1-2 weeks before cancel |
| Data export initiated | Critical | Days before cancel |
| NPS score drops below 6 | Medium | 1-3 months before cancel |
Proactive Interventions
| Trigger | Intervention |
|---|---|
| Usage drop >50% for 2 weeks | "We noticed you haven't used [feature]. Need help?" email |
| Approaching plan limit | Upgrade nudge |
| No login for 14 days | Re-engagement email with product updates |
| NPS detractor (0-6) | Personal follow-up within 24 hours |
Part 5: Cancel Flow Design
The Cancel Flow Structure
Trigger → Survey → Dynamic Offer → Confirmation → Post-CancelExit Survey Design
| Reason | What It Tells You |
|---|---|
| Too expensive | Price sensitivity, may respond to discount |
| Not using it enough | Low engagement, may respond to pause/onboarding |
| Missing a feature | Product gap, show roadmap |
| Switching to competitor | Competitive pressure |
| Technical issues | Product quality, escalate to support |
| Temporary / seasonal | Usage pattern, offer pause |
Save Offer Mapping
| Cancel Reason | Primary Offer | Fallback Offer |
|---|---|---|
| Too expensive | Discount (20-30% for 2-3 months) | Downgrade |
| Not using | Pause (1-3 months) | Free onboarding |
| Missing feature | Roadmap preview | Workaround guide |
| Competitor | Competitive comparison + discount | Feedback session |
| Technical issues | Escalate to support | Credit + priority fix |
Show full SKILL.md (489 more words)Show less
Save Offer Types
- Discount: 20-30% for 2-3 months (avoid 50%+)
- Pause: 1-3 months max, 60-80% eventually return
- Downgrade: Show what they keep vs. lose
- Feature unlock: Extend trial of higher tier
- Personal outreach: For high-value accounts
Part 6: Involuntary Churn (Dunning)
The Dunning Stack
Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancelPre-Dunning (Prevent Failures)
- Card expiry alerts: 30, 15, 7 days before
- Backup payment method prompt at signup
- Card updater services (Visa/MC auto-update)
- Pre-billing notification for annual plans
Smart Retry Logic
| Decline Type | Retry Strategy |
|---|---|
| Soft decline | Retry 3-5 times over 7-10 days |
| Hard decline | Don't retry — ask for new card |
| Authentication required | Send customer to update payment |
Dunning Email Sequence
| Timing | Content | |
|---|---|---|
| 1 | Day 0 | "Your payment didn't go through. Update your card." |
| 2 | Day 3 | "Quick reminder — update your payment." |
| 3 | Day 7 | "Your account will be paused in 3 days." |
| 4 | Day 10 | "Last chance to keep your account active." |
Part 7: Re-engagement & Retention
Re-engagement Triggers
| Trigger | Condition | Channel | Max Frequency |
|---|---|---|---|
| Early dormancy | 3-7 days inactive | Push | 4×/month |
| Mid dormancy | 7-14 days inactive | 2×/month | |
| Onboarding drop | Incomplete onboarding | 3×/month | |
| Feature discovery | Unused high-value feature | In-app | 1×/month |
| Streak at risk | Streak expires in 6 hours | Push | As needed |
Habit Formation (Hook Model)
| Phase | Goal | Examples |
|---|---|---|
| Trigger | Create the cue | Push notifications, email digest |
| Action | Minimum viable behavior | One-click action, simple daily task |
| Variable Reward | Unpredictable value | Social recognition, progress unlocks |
| Investment | User commits something | Profile data, settings, connections |
Gamification Elements
- Badge rarity: Common → Rare → Epic → Legendary
- Progress levels: 5 levels with XP ranges
- Streak systems: 7-day → 30-day → 100-day → 365-day
Part 8: LTV Maximization
The LTV Equation
LTV = (Average Revenue Per Customer × Average Customer Lifespan) - CACTo maximize LTV:
- INCREASE Revenue Per Customer (upsells, cross-sells)
- INCREASE Customer Lifespan (reduce churn)
- DECREASE CAC (get referrals)
Ascension Ladder
Level 1: Entry Offer → Solves first problem
↓
Level 2: Core Offer → Deeper solution
↓
Level 3: Premium Offer → Advanced/faster results
↓
Level 4: Done-For-You → They pay you to do it
↓
Level 5: Ongoing Relationship → Retainer/subscriptionRetention Levers
- Onboarding Excellence — Get them a win in first 24-48 hours
- Engagement Systems — Keep them using regularly
- Success Milestones — Make progress visible and celebrated
- Community/Connection — Create belonging
- Ascension Triggers — Move to next level at right time
Part 9: Metrics & Measurement
Key Metrics
| Metric | Formula | Target |
|---|---|---|
| Monthly churn rate | Churned / Start-of-month | <5% B2C, <2% B2B |
| Revenue churn (net) | (Lost MRR - Expansion) / Start MRR | Negative |
| Cancel flow save rate | Saved / Total cancel sessions | 25-35% |
| Dunning recovery rate | Recovered / Total failures | 50-60% |
| Time to cancel | Days from signal to cancel | Track trend |
Cohort Analysis
Segment by:
- Acquisition channel
- Plan type
- Tenure
- Cancel reason
- Save offer type
Part 10: Segmentation Strategy
Customer Segment Approach
├── Enterprise (high-touch)
│ ├── Dedicated CSM
│ ├── Custom success plans
│ └── Executive sponsors
├── Mid-market (mid-touch)
│ ├── Pooled CSM model
│ ├── Templated playbooks
│ └── Regular check-ins
└── SMB (tech-touch)
├── Automated journeys
├── Self-service resources
└── Trigger-based outreachCommon Mistakes
- No cancel flow — Even simple survey + offer saves 10-15%
- Same offer for every reason — Match offer to reason
- Discounts too deep — 50%+ trains customers to cancel-for-deals
- Ignoring involuntary churn — Often 30-50% of total
- No dunning emails — Letting payment failures silently cancel
- Guilt-trip copy — Damages brand trust
- Pausing too long — Beyond 3 months rarely reactivates
Related Skills
- marketing-automation: For onboarding and win-back sequences
- conversion-rate-optimization: For in-app upgrade moments
- pricing-strategy: For plan structure
- user-onboarding: For activation optimization
- data-and-funnel-analytics: For churn signal events
© manojbajaj95, 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/customer-success-and-retention of manojbajaj95/claude-gtm-plugin.
Open the folder on GitHubat commit 0830a46
Compare with similar skills
Customer Success And Retention 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 And Retention this skillmanojbajaj95/claude-gtm-plugin | 105 | — | ~3k | Automated safety check: Pass | MIT | |
| Cs Health Scorecardmohitagw15856/pm-claude-skills | 1.4k | — | ~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 | |
| 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 |
Similar skills
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.
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…
More from manojbajaj95/claude-gtm-plugin
All 52 skills in this repoApp Store Optimization
manojbajaj95/claude-gtm-plugin
A skill your agent uses when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
Market Research Analysis
manojbajaj95/claude-gtm-plugin
Comprehensive market research and analysis skill. An agent skill from manojbajaj95/claude-gtm-plugin.
Pitch Deck Creation
manojbajaj95/claude-gtm-plugin
Create professional investor pitch decks with structured content and visual design.
Qr Code Generator
manojbajaj95/claude-gtm-plugin
Generate QR codes with URLs and UTM tracking. An agent skill from manojbajaj95/claude-gtm-plugin.
SEO And Aeo Strategy
manojbajaj95/claude-gtm-plugin
SEO, AEO (Answer Engine Optimization), and GEO strategy for search engines and AI visibility.
Linkedin
manojbajaj95/claude-gtm-plugin
LinkedIn profile optimization and content creation. An agent skill from manojbajaj95/claude-gtm-plugin.
Related
Categories
Questions about Customer Success And Retention
What does Customer Success And Retention do?
Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization. Customer Success And Retention is an agent skill from manojbajaj95/claude-gtm-plugin. Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization.
When should I use Customer Success And Retention?
Customer Success And Retention fits situations like: designing customer onboarding flows; building health scores; creating retention systems; designing upsells.
How do I install Customer Success And Retention in Claude Code?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a claude-code`. Or copy the skill folder (skills/customer-success-and-retention in manojbajaj95/claude-gtm-plugin) into .claude/skills/customer-success-and-retention in your project. Claude Code loads it when a task matches its description.
How do I install Customer Success And Retention in Codex?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -a codex`. Or copy the skill folder (skills/customer-success-and-retention in manojbajaj95/claude-gtm-plugin) into .agents/skills/customer-success-and-retention in your project. Codex loads it when a task matches its description.
Can I use Customer Success And Retention 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 manojbajaj95/claude-gtm-plugin --skill customer-success-and-retention -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-and-retention, .gemini/skills/customer-success-and-retention, .github/skills/customer-success-and-retention and .opencode/skills/customer-success-and-retention in your project.
What does Customer Success And Retention need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Success And Retention is instructions for the agent only.
Does Customer Success And Retention 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 And Retention 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 And Retention use?
Customer Success And Retention 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 And Retention 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.
What are the alternatives to Customer Success And Retention?
Skills that share tags, products or a category with Customer Success And Retention: Cs Health Scorecard (mohitagw15856/pm-claude-skills, 1.4k stars), Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars) and Account Plan (Bevel-Software/Hexis, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Success And Retention?
manojbajaj95 (a GitHub user) maintains it in manojbajaj95/claude-gtm-plugin, which has 105 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on September 18, 2026.
Source: manojbajaj95/claude-gtm-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.