Customer success
Build customer success playbooks — onboarding flows, health scoring, QBR templates, and churn intervention plans.From its SKILL.md
npx -y skills add inbharatai/claude-skills --skill customer-successAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.8 KB, 324 tokens by cl100k_base, as published. Nobody here has run it
Customer Success
Overview
Build customer success playbooks — onboarding flows, health scoring, QBR templates, and churn intervention plans.
When to Use This Skill
Use Customer Success when you need to:
- Work with customer success tasks in your project or workflow
- Automate customer success operations at scale
- Generate production-quality customer success output quickly
Instructions
When this skill is active, Claude will:
- Understand the full context of your customer success request
- Apply best practices and conventions for Business & Productivity
- Produce clean, well-structured, production-ready output
- Explain key decisions and offer alternatives where relevant
Examples
Example 1 — Basic Usage
User: Help me get started with customer success.
Claude: I'll walk you through the essential steps for customer success in your context...
Example 2 — Advanced Usage
User: I need a production-ready customer success setup with full error handling.
Claude: Here's a complete, production-hardened customer success implementation...
Guidelines
- Always validate inputs before processing
- Follow the conventions of the target platform or language
- Prefer explicit over implicit — clarity beats cleverness
- Include comments for non-obvious logic
- Suggest tests or validation steps where appropriate
Dependencies
Required: none
Platforms
Available on: claude.ai, api
Part of the claude-skills collection — 183+ skills for Claude.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most customer support skills give in 324 tokens
Counted across 123 of the 124 authors here whose files we hold, read 2026-08-07
- Call RUBE_SEARCH_TOOLS first to get current schemasin 12 of 123, across 4 files
- Confirm connection status is ACTIVE before running workflowsin 12 of 123, across 4 files
- Stop and ask for clarification if required inputs are missingin 9 of 123, across 2 files
- Call RUBE_MANAGE_CONNECTIONS with the helpdesk toolkitin 9 of 123, across 2 files
- Use both timestamp and ID for cursor navigationin 8 of 123, across 1 file
- Implement backoff on 429 responsesin 8 of 123, across 1 file
- Parse response data defensively with fallback patternsin 8 of 123, across 1 file
- Use this skill only when the task clearly matches the scopein 8 of 123, across 1 file
- Pass a JSON file as the positional argumentin 7 of 123, across 1 file
- Specify output format with the --format flagin 7 of 123, across 1 file
- Run health, churn, and expansion scripts togetherin 7 of 123, across 1 file
- Verify output files contain expected records before continuingin 7 of 123, across 1 file
Said here and by no other author read
- understand the full context of the request
- apply best practices and conventions
- produce clean structured output
- explain key decisions and offer alternatives
- validate inputs before processing
- follow target platform conventions
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.