Task Forest
dongshuyan/compass-skills
Maintains a repo-local task forest or task DAG for the current workspace.
Scores customer health, churn risk and expansion potential from a JSON export of account data, using three Python scripts that need no extra libraries.
Install Customer Success Manager
$ npx skills add alirezarezvani/claude-skills --skill customer-success-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills customer-success-manager --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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/skills/customer-success-manager .claude/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .claude/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-managerType 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 alirezarezvani/claude-skills --skill customer-success-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills customer-success-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/business-growth/skills/customer-success-manager .agents/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .agents/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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 alirezarezvani/claude-skills --skill customer-success-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills customer-success-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/business-growth/skills/customer-success-manager .cursor/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .cursor/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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/alirezarezvani/claude-skills.git --path business-growth/skills/customer-success-manager--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 alirezarezvani/claude-skills --skill customer-success-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills customer-success-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/business-growth/skills/customer-success-manager .gemini/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .gemini/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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 alirezarezvani/claude-skills customer-success-managerInstalls 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 alirezarezvani/claude-skills --skill customer-success-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/business-growth/skills/customer-success-manager .github/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .github/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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 alirezarezvani/claude-skills --skill customer-success-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills customer-success-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/business-growth/skills/customer-success-manager .opencode/skills/customer-success-manager && 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-manager" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/customer-success-manager into .opencode/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", 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-manager- GitHub stars
- 28k
- Used in
- 1 other repo
- Token cost
- ~2.3k tokens
- SKILL.md length
- 670 words
- Files
- 13 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scores customer health, churn risk and expansion potential from a JSON export of account data, using three Python scripts that need no extra libraries.
- Works in 3 steps: health_score_calculator.py → churn_risk_analyzer.py → expansion_opportunity_scorer.py
- Scoring a customer portfolio to see which accounts are healthy or at risk
- SKILL.md covers Table of Contents, Input Requirements, Output Formats and How to Use, plus 5 more sections
- Runs Python scripts from its folder; calls python
What it does
Three command-line scripts read a JSON file of customer records and produce repeatable results. health_score_calculator.py scores each account from usage, engagement, support and relationship data with a trend comparison, churn_risk_analyzer.py sorts accounts into risk tiers using contract end dates and warning signals, and expansion_opportunity_scorer.py ranks upsell chances from seat usage, module adoption and department reach.
They rely only on the Python standard library, call no APIs and use no machine-learning models. Output is readable text by default, or JSON with --format json for pipelines. A sample data file shows the expected fields, and the skill bundles templates for onboarding checklists, success plans, quarterly business reviews and executive business reviews, plus reference notes on metrics benchmarks, playbooks and the health-scoring framework.
When your agent uses it
- Scoring a customer portfolio to see which accounts are healthy or at risk
- Prioritizing accounts for retention outreach ahead of renewal
- Finding upsell and expansion candidates from product usage data
- Preparing a quarterly business review or success plan from a template
Example prompts
- “Run the health score calculator on ./data/customers.json and list the five weakest accounts.”
- “Which accounts in this export are most likely to churn before their contract end date?”
- “Find expansion opportunities among our Enterprise customers using seat usage and module adoption.”
Requirements
- Python 3 (standard library only)
Workflow steps
3 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 19392f7. 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
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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 Manager loads about 2.3k tokens when it runs, and up to ~9.4k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 670 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); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 670 words, ~2,306 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-success-manager/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- customer-success-manager
- description
- Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- business-growth
- metadata.domain
- customer-success
- metadata.updated
- 2026-02-06
- metadata.python-tools
- health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py
- metadata.tech-stack
- customer-success, saas-metrics, health-scoring
Customer Success Manager
Production-grade customer success analytics with multi-dimensional health scoring, churn risk prediction, and expansion opportunity identification. Three Python CLI tools provide deterministic, repeatable analysis using standard library only -- no external dependencies, no API calls, no ML models.
Table of Contents
- Input Requirements
- Output Formats
- How to Use
- Scripts
- Reference Guides
- Templates
- Best Practices
- Limitations
Input Requirements
All scripts accept a JSON file as positional input argument. See assets/sample_customer_data.json for complete schema examples and sample data.
Health Score Calculator
Required fields per customer object: customer_id, name, segment, arr, and nested objects usage (login_frequency, feature_adoption, dau_mau_ratio), engagement (support_ticket_volume, meeting_attendance, nps_score, csat_score), support (open_tickets, escalation_rate, avg_resolution_hours), relationship (executive_sponsor_engagement, multi_threading_depth, renewal_sentiment), and previous_period scores for trend analysis.
Churn Risk Analyzer
Required fields per customer object: customer_id, name, segment, arr, contract_end_date, and nested objects usage_decline, engagement_drop, support_issues, relationship_signals, and commercial_factors.
Expansion Opportunity Scorer
Required fields per customer object: customer_id, name, segment, arr, and nested objects contract (licensed_seats, active_seats, plan_tier, available_tiers), product_usage (per-module adoption flags and usage percentages), and departments (current and potential).
Output Formats
All scripts support two output formats via the --format flag:
text(default): Human-readable formatted output for terminal viewingjson: Machine-readable JSON output for integrations and pipelines
How to Use
Quick Start
# Health scoring
python scripts/health_score_calculator.py assets/sample_customer_data.json
python scripts/health_score_calculator.py assets/sample_customer_data.json --format json
# Churn risk analysis
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json --format json
# Expansion opportunity scoring
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json --format jsonWorkflow Integration
# 1. Score customer health across portfolio
python scripts/health_score_calculator.py customer_portfolio.json --format json > health_results.json
# Verify: confirm health_results.json contains the expected number of customer records before continuing
# 2. Identify at-risk accounts
python scripts/churn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json
# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer
# 3. Find expansion opportunities in healthy accounts
python scripts/expansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json
# Verify: confirm expansion_results.json lists opportunities ranked by priority
# 4. Prepare QBR using templates
# Reference: assets/qbr_template.mdError handling: If a script exits with an error, check that:
- The input JSON matches the required schema for that script (see Input Requirements above)
- All required fields are present and correctly typed
- Python 3.7+ is being used (
python --version) - Output files from prior steps are non-empty before piping into subsequent steps
Scripts
1. health_score_calculator.py
Purpose: Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.
Dimensions and Weights:
| Dimension | Weight | Metrics |
|---|---|---|
| Usage | 30% | Login frequency, feature adoption, DAU/MAU ratio |
| Engagement | 25% | Support ticket volume, meeting attendance, NPS/CSAT |
| Support | 20% | Open tickets, escalation rate, avg resolution time |
| Relationship | 25% | Executive sponsor engagement, multi-threading depth, renewal sentiment |
Classification:
- Green (75-100): Healthy -- customer achieving value
- Yellow (50-74): Needs attention -- monitor closely
- Red (0-49): At risk -- immediate intervention required
Usage:
python scripts/health_score_calculator.py customer_data.json
python scripts/health_score_calculator.py customer_data.json --format json2. churn_risk_analyzer.py
Purpose: Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.
Risk Signal Weights:
| Signal Category | Weight | Indicators |
|---|---|---|
| Usage Decline | 30% | Login trend, feature adoption change, DAU/MAU change |
| Engagement Drop | 25% | Meeting cancellations, response time, NPS change |
| Support Issues | 20% | Open escalations, unresolved critical, satisfaction trend |
| Relationship Signals | 15% | Champion left, sponsor change, competitor mentions |
| Commercial Factors | 10% | Contract type, pricing complaints, budget cuts |
Risk Tiers:
- Critical (80-100): Immediate executive escalation
- High (60-79): Urgent CSM intervention
- Medium (40-59): Proactive outreach
- Low (0-39): Standard monitoring
Usage:
python scripts/churn_risk_analyzer.py customer_data.json
python scripts/churn_risk_analyzer.py customer_data.json --format jsonShow full SKILL.md (251 more words)Show less
3. expansion_opportunity_scorer.py
Purpose: Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.
Expansion Types:
- Upsell: Upgrade to higher tier or more of existing product
- Cross-sell: Add new product modules
- Expansion: Additional seats or departments
Usage:
python scripts/expansion_opportunity_scorer.py customer_data.json
python scripts/expansion_opportunity_scorer.py customer_data.json --format jsonReference Guides
| Reference | Description |
|---|---|
references/health-scoring-framework.md | Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration |
references/cs-playbooks.md | Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures |
references/cs-metrics-benchmarks.md | Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry |
Templates
| Template | Purpose |
|---|---|
assets/qbr_template.md | Quarterly Business Review presentation structure |
assets/success_plan_template.md | Customer success plan with goals, milestones, and metrics |
assets/onboarding_checklist_template.md | 90-day onboarding checklist with phase gates |
assets/executive_business_review_template.md | Executive stakeholder review for strategic accounts |
Best Practices
- Combine signals: Use all three scripts together for a complete customer picture
- Act on trends, not snapshots: A declining Green is more urgent than a stable Yellow
- Calibrate thresholds: Adjust segment benchmarks based on your product and industry per
references/health-scoring-framework.md - Prepare with data: Run scripts before every QBR and executive meeting; reference
references/cs-playbooks.mdfor intervention guidance
Limitations
- No real-time data: Scripts analyze point-in-time snapshots from JSON input files
- No CRM integration: Data must be exported manually from your CRM/CS platform
- Deterministic only: No predictive ML -- scoring is algorithmic based on weighted signals
- Threshold tuning: Default thresholds are industry-standard but may need calibration for your business
- Revenue estimates: Expansion revenue estimates are approximations based on usage patterns
Last Updated: February 2026 Tools: 3 Python CLI tools Dependencies: Python 3.7+ standard library only
© alirezarezvani, 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 12 other files (scripts, references, assets) in business-growth/skills/customer-success-manager of alirezarezvani/claude-skills.
- SKILL.md
- assets/executive_business_review_template.md
- assets/expected_output.json
- assets/onboarding_checklist_template.md
- assets/qbr_template.md
- assets/sample_customer_data.json
- assets/success_plan_template.md
- references/cs-metrics-benchmarks.md
- references/cs-playbooks.md
- references/health-scoring-framework.md
- scripts/churn_risk_analyzer.py
- scripts/expansion_opportunity_scorer.py
- scripts/health_score_calculator.py
Open the folder on GitHubat commit 19392f7
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Customer Success Manager 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 Manager this skillalirezarezvani/claude-skills | 28k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Task Forestdongshuyan/compass-skills | 753 | — | ~1.6k | Automated safety check: Pass | MIT | |
| 1688 Buyer Opportunity Trackernext-1688/1688-customer-opportunity | 553 | — | ~4.6k | Automated safety check: Pass | None | |
| Faq Shortcutskishormorol/cli-faq-shortcuts | 127 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Review Analyzer Skillbuluslan/review-analyzer-skill | 131 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Write Docsbeyonders-studio/initiative | 171 | — | ~3.8k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
1688 Buyer Opportunity Tracker
next-1688/1688-customer-opportunity
Finds high-value repeat buyer clusters on 1688, shows their details, launches outreach messaging and surfaces which buyers most need a follow-up.
Faq Shortcuts
kishormorol/cli-faq-shortcuts
Turn the questions and instructions a user keeps typing into a project into short slash-command skills, mined from their real Claude Code, Codex and Cursor session history and git log.
Review Analyzer Skill
buluslan/review-analyzer-skill
review-analyzer-skill是由buluslan（公众号：新西楼.AI）研发的电商评论深度分析Skill（VOC 客户之声分析），他会帮你把一堆产品评论变成一份能落地的决策依据——22 维 AI 打标提炼用户画像、痛点和真实需求，输出 15 章深度洞察报告和可视化看板，从差评里挖出产品优化机会点、从好评里找到爆款基因。
Write Docs
beyonders-studio/initiative
Write or edit the Initiative help center under docs/en/ — the house voice, the structural rules, and how to build and check the site.
- Official
Customer Deck Builder
zapier/gtm-cheat-codes
Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Works with
Categories
Questions about Customer Success Manager
What does Customer Success Manager do?
Scores customer health, churn risk and expansion potential from a JSON export of account data, using three Python scripts that need no extra libraries. Three command-line scripts read a JSON file of customer records and produce repeatable results.py ranks upsell chances from seat usage, module adoption and department reach.
When should I use Customer Success Manager?
Customer Success Manager fits situations like: scoring a customer portfolio to see which accounts are healthy or at risk; prioritizing accounts for retention outreach ahead of renewal; finding upsell and expansion candidates from product usage data; preparing a quarterly business review or success plan from a template.
How do I install Customer Success Manager in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill customer-success-manager -a claude-code`. Or copy the skill folder (business-growth/skills/customer-success-manager in alirezarezvani/claude-skills) into .claude/skills/customer-success-manager in your project. Claude Code loads it when a task matches its description.
How do I install Customer Success Manager in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill customer-success-manager -a codex`. Or copy the skill folder (business-growth/skills/customer-success-manager in alirezarezvani/claude-skills) into .agents/skills/customer-success-manager in your project. Codex loads it when a task matches its description.
Can I use Customer Success Manager 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 alirezarezvani/claude-skills --skill customer-success-manager -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-manager, .gemini/skills/customer-success-manager, .github/skills/customer-success-manager and .opencode/skills/customer-success-manager in your project.
What does Customer Success Manager need to run?
Going by SKILL.md and its folder, Customer Success Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3 (standard library only).
Does Customer Success Manager 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 Manager 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Customer Success Manager use?
Customer Success Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Customer Success Manager use?
About 2.3k tokens (SKILL.md is roughly 9.2k 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 7.1k tokens, read only when the agent opens those files.
What are the alternatives to Customer Success Manager?
Skills that share tags, products or a category with Customer Success Manager: Task Forest (dongshuyan/compass-skills, 753 stars), 1688 Buyer Opportunity Tracker (next-1688/1688-customer-opportunity, 553 stars), Faq Shortcuts (kishormorol/cli-faq-shortcuts, 127 stars) and Review Analyzer Skill (buluslan/review-analyzer-skill, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Success Manager?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/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.