Agent skill

Customer Success

by aAAaqwq in aAAaqwq/AGI-Super-Team

Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies

MITAuto-check passedSales & Support

Install Customer Success

skills CLI
$ npx skills add aAAaqwq/AGI-Super-Team --skill customer-success -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aAAaqwq/AGI-Super-Team customer-success --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/customer-success .claude/skills/customer-success && rm -rf skills-src

Use ~/.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/

Facts

Skill name
customer-success
GitHub stars
105
Used in
1 other repo
Token cost
~3.2k tokens
SKILL.md length
92 words
Files
1
Skills in repo
167
Repo updated
First seen
Licence
MIT

At a glance

Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies

  • Tasks that involve Customer success
  • SKILL.md covers Overview, Customer Onboarding, Health Scoring and QBR (Quarterly Business Review), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Customer Success is an agent skill from aAAaqwq/AGI-Super-Team. Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Customer success. The repository describes itself as: An installable, cross-framework AI organization: C-suite agents, expert subagents, curated skills, independent review, and one-command setup across 18 AI client/runtime adapters. The licence is MIT.

When your agent uses it

  • Tasks that involve Customer success

Example prompts

  • “/customer-success”

What it can do on your machine

Read from SKILL.md and the folder at commit 7cefd81. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names 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 loads about 3.2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 92 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

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 aAAaqwq/AGI-Super-Team at commit 7cefd81, republished under its MIT licence (© aAAaqwq). 92 words, ~3,201 tokens.

Download SKILL.mdSave it as .claude/skills/customer-success/SKILL.md (or your agent's skills folder).
name
customer-success
description
Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies
version
1.0.0
author
claude-office-skills
license
MIT
category
sales
tags
customer-success, retention, onboarding, qbr, expansion
department
Customer Success
models.recommended
claude-sonnet-4, claude-opus-4
capabilities
onboarding_design, health_scoring, qbr_creation, expansion_playbooks, retention_strategies
languages
en, zh
related_skills
crm-automation, subscription-management, saas-metrics

Customer Success

Comprehensive customer success management covering onboarding, health scoring, QBRs, expansion playbooks, and retention strategies.

Overview

This skill covers:

  • Customer onboarding programs
  • Health scoring and monitoring
  • QBR (Quarterly Business Review) templates
  • Expansion and upsell playbooks
  • Retention and churn prevention

Customer Onboarding

Onboarding Program Structure
yaml
onboarding_phases:
  phase_1_kickoff:
    duration: "Week 1"
    goals:
      - establish_relationship
      - set_expectations
      - gather_requirements
    activities:
      - kickoff_call: 60min
      - intro_to_support_channels
      - share_onboarding_plan
      - schedule_implementation
    deliverables:
      - success_plan_document
      - timeline_with_milestones
      
  phase_2_implementation:
    duration: "Week 2-3"
    goals:
      - technical_setup
      - data_migration
      - integration_configuration
    activities:
      - implementation_calls: 2-3x
      - technical_support
      - testing_and_validation
    deliverables:
      - working_environment
      - integrations_live
      
  phase_3_training:
    duration: "Week 3-4"
    goals:
      - user_enablement
      - admin_training
      - workflow_setup
    activities:
      - admin_training: 90min
      - end_user_training: 60min
      - workflow_workshop
    deliverables:
      - trained_users
      - documented_workflows
      
  phase_4_launch:
    duration: "Week 4-5"
    goals:
      - go_live
      - adoption_tracking
      - quick_wins
    activities:
      - launch_call
      - monitor_adoption
      - celebrate_wins
    deliverables:
      - users_active
      - first_value_achieved
      
  phase_5_handoff:
    duration: "Week 6"
    goals:
      - transition_to_csm
      - establish_cadence
      - document_success
    activities:
      - handoff_call
      - schedule_check_ins
      - nps_survey
    deliverables:
      - ongoing_csm_relationship
      - baseline_metrics
Onboarding Checklist
yaml
onboarding_checklist:
  pre_kickoff:
    - [ ] Review sales notes and requirements
    - [ ] Prepare success plan template
    - [ ] Schedule kickoff call
    - [ ] Send welcome email
    
  kickoff:
    - [ ] Introductions and roles
    - [ ] Review goals and timeline
    - [ ] Identify key stakeholders
    - [ ] Define success metrics
    - [ ] Schedule implementation calls
    
  implementation:
    - [ ] Account setup complete
    - [ ] Users provisioned
    - [ ] SSO configured (if applicable)
    - [ ] Integrations connected
    - [ ] Data migrated
    - [ ] Testing completed
    
  training:
    - [ ] Admin training delivered
    - [ ] User training delivered
    - [ ] Training materials shared
    - [ ] Self-service resources provided
    - [ ] Certification program introduced
    
  launch:
    - [ ] Go-live confirmed
    - [ ] Users logging in
    - [ ] First workflow completed
    - [ ] Quick win achieved
    - [ ] Launch celebration
    
  handoff:
    - [ ] CSM introduced
    - [ ] Regular cadence scheduled
    - [ ] Support escalation path clear
    - [ ] NPS survey sent
    - [ ] Onboarding documentation complete

Health Scoring

Health Score Model
yaml
health_score_components:
  product_engagement: # 40% weight
    metrics:
      - dau_mau_ratio:
          excellent: >0.5
          good: 0.3-0.5
          at_risk: 0.1-0.3
          critical: <0.1
          
      - feature_adoption:
          measure: core_features_used / total_core_features
          excellent: >80%
          good: 60-80%
          at_risk: 40-60%
          critical: <40%
          
      - depth_of_use:
          measure: actions_per_user_per_week
          benchmark: vs_similar_customers
          
  relationship: # 25% weight
    metrics:
      - nps_score:
          promoter: 9-10
          passive: 7-8
          detractor: 0-6
          
      - csm_engagement:
          regular_meetings: true/false
          responsive_to_outreach: true/false
          
      - executive_sponsor:
          identified: true/false
          engaged: true/false
          
  financial: # 20% weight
    metrics:
      - payment_history:
          on_time: excellent
          late_1x: good
          late_2x+: at_risk
          
      - growth_trajectory:
          expanding: excellent
          stable: good
          contracting: at_risk
          
  sentiment: # 15% weight
    metrics:
      - support_tickets:
          sentiment_trend: positive/neutral/negative
          resolution_satisfaction: score
          
      - feedback:
          product_feedback: positive/neutral/negative
          feature_requests: engaged/silent
          
scoring_formula:
  total: (engagement × 0.4) + (relationship × 0.25) + (financial × 0.2) + (sentiment × 0.15)
  
tiers:
  healthy: 80-100 (green)
  stable: 60-79 (yellow)
  at_risk: 40-59 (orange)
  critical: 0-39 (red)
Health Score Automation
yaml
health_automation:
  critical_score:
    trigger: score < 40
    actions:
      - alert: csm_immediately
      - alert: cs_manager
      - schedule: save_call_within_24h
      - pause: marketing_emails
      
  at_risk_score:
    trigger: score drops below 60
    actions:
      - alert: csm_same_day
      - schedule: check_in_call
      - review: account_for_team_meeting
      
  health_improvement:
    trigger: score increases by 20+
    actions:
      - flag: expansion_opportunity
      - schedule: success_story_interview
      - request: testimonial_or_referral

QBR (Quarterly Business Review)

QBR Template
markdown
# Quarterly Business Review
## {Company Name} | {Quarter} {Year}

---

### Agenda (60 minutes)
1. Business Update (10 min)
2. Success Metrics Review (15 min)
3. Product Usage Analysis (10 min)
4. Roadmap Preview (10 min)
5. Strategic Discussion (10 min)
6. Action Items & Next Steps (5 min)

---

### 1. Executive Summary

**Relationship Health**: 🟢 Healthy (Score: 85)

**Key Highlights:**
- ✅ Exceeded adoption targets by 15%
- ✅ 3 new departments onboarded
- ✅ NPS improved from 7 to 9
- ⚠️ Feature request pending: {feature}

**ROI Achieved This Quarter:**
- Time saved: 500+ hours
- Cost reduction: $50,000
- Productivity increase: 25%

---

### 2. Success Metrics

| Goal | Target | Actual | Status |
|------|--------|--------|--------|
| User Adoption | 80% | 92% | ✅ Exceeded |
| Daily Active Users | 100 | 120 | ✅ Exceeded |
| Support Tickets | <10/mo | 8/mo | ✅ On Track |
| NPS Score | >8 | 9 | ✅ Exceeded |

**Trend Charts:**
[Include usage trends, adoption curves]

---

### 3. Product Usage Analysis

**Most Used Features:**
1. {Feature 1} - 95% adoption
2. {Feature 2} - 87% adoption
3. {Feature 3} - 72% adoption

**Underutilized Features:**
- {Feature X} - 15% adoption
  - Recommendation: Training session
- {Feature Y} - 22% adoption
  - Recommendation: Workflow workshop

**Power Users:**
- {User 1}: Champion, can lead training
- {User 2}: Heavy API user

---

### 4. Roadmap Preview

**Coming Next Quarter:**
- 🚀 {Feature 1} - Addresses your request from {date}
- 🚀 {Feature 2} - Improves {workflow}
- 🚀 {Integration} - Connects with {tool}

**Beta Opportunities:**
- Would you like early access to {feature}?

---

### 5. Strategic Discussion

**Questions for You:**
1. What are your top priorities for next quarter?
2. Any organizational changes we should know about?
3. Where are you still experiencing friction?

**Growth Opportunities:**
- Department X could benefit from {product}
- {Use case} is now possible with new features
- Volume discount available at {tier}

---

### 6. Action Items

| Item | Owner | Due Date |
|------|-------|----------|
| Schedule training on {feature} | CSM | {date} |
| Connect with IT on integration | Customer | {date} |
| Share beta access | Product | {date} |
| Review expansion proposal | Customer | {date} |

---

### Next QBR: {Date}

Expansion Playbook

Expansion Triggers
yaml
expansion_signals:
  usage_based:
    - approaching_seat_limit: 80% of licensed
    - feature_usage_ceiling: using advanced features
    - api_volume_increasing: growth trend
    - storage_approaching_limit: 80%+ used
    
  behavioral:
    - champion_promoting: internal advocacy
    - new_department_interest: cross-team requests
    - executive_engagement: c-level using product
    - feature_requests: for_higher_tier_features
    
  business:
    - company_funding: new_round_announced
    - company_growth: hiring_increase
    - new_initiative: announced_project
    - renewal_approaching: 90_days_out
Expansion Conversation Framework
yaml
expansion_framework:
  discover:
    questions:
      - "What new initiatives are you planning?"
      - "Which other teams could benefit?"
      - "What's limiting you today?"
    listen_for:
      - growth_plans
      - pain_points
      - budget_cycles
      
  align:
    approach:
      - connect_to_their_goals
      - quantify_current_value
      - project_expanded_value
    messaging: |
      "Based on the {$X value} you've seen with 
      {current_use_case}, expanding to {new_use_case} 
      could deliver {projected_value}."
      
  propose:
    elements:
      - specific_recommendation
      - pricing_options
      - implementation_timeline
      - roi_projection
      
  close:
    tactics:
      - executive_alignment
      - champion_support
      - pilot_option
      - renewal_bundle

Retention Strategies

Churn Risk Playbook
yaml
churn_indicators:
  high_risk:
    - no_login_30_days
    - usage_drop_50%
    - support_complaints_increase
    - executive_sponsor_left
    - competitor_mentioned
    
  actions_by_risk:
    critical:
      - csm_call_within_24h
      - manager_escalation
      - executive_outreach
      - save_offer_prepared
      
    at_risk:
      - csm_call_within_48h
      - health_check_meeting
      - re_training_offered
      - success_plan_review
      
save_offers:
  by_reason:
    price:
      - discount: 20% for 3 months
      - annual_commitment: additional_discount
      - downgrade_option: lower_tier
      
    not_using:
      - training: free_intensive_session
      - implementation: professional_services
      - pause: 1-3_months
      
    competitor:
      - competitive_discount
      - feature_commitment
      - executive_meeting
      
    organizational:
      - contract_flexibility
      - pause_option
      - reduced_seats

Output Example

Request: "Create a QBR presentation for a customer"

Output:

markdown
# QBR Presentation - Acme Corp
## Q4 2025

---

## Slide 1: Executive Summary

### Health Score: 85/100 🟢

**This Quarter's Wins:**
- 📈 User adoption: 85% → 92%
- 💰 ROI delivered: $150,000
- ⭐ NPS: 8 → 9

**Focus Areas:**
- Expand to Marketing team
- Increase API usage
- Prepare for renewal

---

## Slide 2: Success Metrics

| Metric | Q3 | Q4 | Change |
|--------|----|----|--------|
| Active Users | 150 | 180 | +20% |
| Projects Created | 500 | 750 | +50% |
| Time Saved | 200h | 350h | +75% |

**ROI Calculation:**
- Hours saved: 350h × $50/hr = $17,500/mo
- Annual value: $210,000
- Investment: $60,000
- **ROI: 3.5x**

---

## Slide 3: Adoption Analysis

**Top Used Features:**
1. Task Management: 95%
2. Time Tracking: 82%
3. Reporting: 75%

**Opportunity Features:**
- Automation: 25% (training scheduled)
- Integrations: 30% (Slack integration available)

---

## Slide 4: Roadmap Alignment

**Coming in Q1:**
- ✅ AI Assistant (addresses your feature request)
- ✅ Salesforce Integration
- ✅ Advanced Analytics

**Early Access:**
Would you like beta access to AI features?

---

## Slide 5: Strategic Discussion

1. Marketing team interest → Expansion opportunity
2. API usage growing → Developer tier consideration
3. Renewal in 90 days → Multi-year discount available

---

## Slide 6: Action Items

| Action | Owner | Date |
|--------|-------|------|
| Marketing demo | Acme | Jan 15 |
| API tier proposal | CSM | Jan 20 |
| Renewal discussion | Both | Feb 1 |

**Next QBR: April 2026**

Customer Success Skill - Part of Claude Office Skills

© aAAaqwq, 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 of aAAaqwq/AGI-Super-Team.

Open the folder on GitHubat commit 7cefd81

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in aAAaqwq/AGI-Super-Team, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Customer Success 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.

Customer Success compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Customer Success this skillaAAaqwq/AGI-Super-Team1051 repos~3.2kAutomated safety check: PassMIT
Cs Health Scorecardmohitagw15856/pm-claude-skills1.4k—~2.4kAutomated safety check: PassMIT
Youtube SearchZeroPointRepo/youtube-skills1k1 repos~1.8kAutomated safety check: PassMIT
YtZeroPointRepo/youtube-skills1k1 repos~951Automated safety check: PassMIT
Account PlanBevel-Software/Hexis100—~2.1kAutomated safety check: PassApache-2.0
Loki Modedavila7/claude-code-templates33k7 repos~7.1kAutomated safety check: WarnMIT

Similar skills

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • 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…

    1k GitHub starsUsed in 1 repo~1.8k tokens
    Sales & SupportAuto-check passed
  • 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…

    1k GitHub starsUsed in 1 repo~951 tokens
    Sales & SupportAuto-check passed
  • 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.

    100 GitHub stars~2.1k tokensUpdated today
    Sales & SupportAuto-check passed
  • Loki Mode

    davila7/claude-code-templates

    Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 7 repos~7.1k tokens
    Sales & SupportAuto-check: warnings
  • 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…

    185 GitHub stars~2.8k tokensUpdated 3 days ago
    Sales & SupportAuto-check passed

More from aAAaqwq/AGI-Super-Team

All 167 skills in this repo
  • Content Creator

    aAAaqwq/AGI-Super-Team

    Create SEO-optimized marketing content with consistent brand voice.

    105 GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • Financial Calculator

    aAAaqwq/AGI-Super-Team

    Advanced financial calculator with future value tables, present value, discount calculations, markup pricing, and compound interest.

    105 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Bankr Signals

    aAAaqwq/AGI-Super-Team

    Transaction-verified trading signals on Base blockchain. An agent skill from aAAaqwq/AGI-Super-Team.

    105 GitHub starsUsed in 2 repos~3.3k tokens
    Auto-check passed
  • Erc 8004

    aAAaqwq/AGI-Super-Team

    Register AI agents on Ethereum mainnet using ERC-8004 (Trustless Agents).

    105 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Frontend Design Ultimate

    aAAaqwq/AGI-Super-Team

    Create distinctive, production-grade static sites with React, Tailwind CSS, and shadcn/ui — no mockups needed.

    105 GitHub starsUsed in 2 repos~2.7k tokens
    Auto-check passed
  • Zsxq Smart Publish

    aAAaqwq/AGI-Super-Team

    Publish and manage content on 知识星球 (zsxq.com). An agent skill from aAAaqwq/AGI-Super-Team.

    105 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Customer Success

What does Customer Success do?

Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies. Customer Success is an agent skill from aAAaqwq/AGI-Super-Team.

When should I use Customer Success?

Customer Success fits situations like: tasks that involve Customer success.

How do I install Customer Success in Claude Code?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill customer-success -a claude-code`. Or copy the skill folder (skills/customer-success in aAAaqwq/AGI-Super-Team) into .claude/skills/customer-success in your project. Claude Code loads it when a task matches its description.

How do I install Customer Success in Codex?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill customer-success -a codex`. Or copy the skill folder (skills/customer-success in aAAaqwq/AGI-Super-Team) into .agents/skills/customer-success in your project. Codex loads it when a task matches its description.

Can I use Customer Success 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 aAAaqwq/AGI-Super-Team --skill customer-success -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, .gemini/skills/customer-success, .github/skills/customer-success and .opencode/skills/customer-success in your project.

What does Customer Success need to run?

SKILL.md names no scripts, command-line tools or credentials: Customer Success is instructions for the agent only.

Does Customer Success 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 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 use?

Customer Success 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 use?

About 3.2k tokens (SKILL.md is roughly 13k 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?

Skills that share tags, products or a category with Customer Success: 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?

aAAaqwq (a GitHub user) maintains it in aAAaqwq/AGI-Super-Team, which has 105 GitHub stars. The repository holds 167 skills in this directory. The repository was last updated on October 8, 2026.

Source: aAAaqwq/AGI-Super-Team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.