conditional-customer-success
Installation
SKILL.md
Conditional Customer Success
A CONDITIONAL skill for products with recurring human relationships. This skill must never be loaded for every product context. It loads only when the product has accounts, renewals, QBRs, or a dedicated customer-success team. When those conditions are absent — for internal tools, pure transactional products, or public services without account-based engagement — this skill declines and routes the caller away.
When to Load (Should-Trigger Examples)
| Example | What makes it a match |
|---|---|
| B2B subscription product with named account managers | Accounts, renewals, dedicated CS team |
| Enterprise SaaS with quarterly business reviews | QBR cadence, account-tier engagement |
| Renewal-risk analysis needed for a contract portfolio | Renewal evidence, churn-risk signals |
| Product with an assigned customer-success team managing health plans | Success plans, health tracking |
| Account-expansion opportunity identified but adoption signals are mixed | Expansion with relationship context |
| Customer feedback loop — insight surfaced, product change made, customer communication needed | Closed-loop Voice of Customer |