Build and execute customer success strategies using playbooks, health scoring, QBRs, and expansion frameworks. Use for: onboarding optimization, customer health monitoring, proactive engagement, churn prevention, expansion planning, QBR execution, and driving product adoption and retention.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill customer-success-jh9282026-manus --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Customer Success Jh9282026 Manus?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-customer-success-jh9282026-manus-claude-skill-registry)More formats (shields.io, HTML) on the badges page.
---
name: "customer-success"
description: "Build and execute customer success strategies using playbooks, health scoring, QBRs, and expansion frameworks. Use for: onboarding optimization, customer health monitoring, proactive engagement, churn prevention, expansion planning, QBR execution, and driving product adoption and retention."
---
# Customer Success
Customer success in 2026 emphasizes proactive engagement, data-driven health scoring, and systematic playbook execution.
## Overview
Modern customer success combines technology, process, and human touch to drive retention, expansion, and advocacy.
## Using the Reference Files
Reference files provide detailed implementation guidance, templates, and advanced techniques for this skill.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...