customer-success

Generates onboarding, support, retention, and voice-of-customer playbooks for launched products.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/sundarshahi/drydock --skill customer-success-sundarshahi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: customer-success
Source: https://github.com/sundarshahi/drydock/tree/main/skills/customer-success
Command: npx skills add https://github.com/sundarshahi/drydock --skill customer-success-sundarshahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a product ships, teams still need a complete post-launch customer success operation — onboarding flows, support SLAs, churn defense, and a feedback loop to product management — and building these from scratch is slow and inconsistent. This Skill produces that entire operational suite as structured, benchmark-grounded artifacts. ## Core Features & Use Cases - Onboarding & Activation: Defines first-value events per persona, sets a time-to-value target grounded in researched benchmarks, and specifies checklists, empty states, and welcome sequences. - Support Operations: Builds a help-center information architecture over existing docs, defines ticket tiers, concrete SLA matrices with escalation paths, canned responses, and a self-serve deflection plan. - Retention & Voice of Customer: Creates a weighted customer health score, churn intervention and renewal/expansion playbooks, an NPS/CSAT program, and routes prioritized, evidence-backed feedback requests to the product-manager. - Use Case: After launching a SaaS product, ask the agent to stand up the full customer success operation — it reads the BRD and docs, then emits onboarding specs, a support runbook, retention playbooks, and PM feedback requests with a completion receipt. ## Quick Start Ask the drydock orchestrator to run the customer-success agent to build the onboarding, support, retention, and voice-of-customer playbooks for the shipped product.

Frequently Asked Questions about customer-success

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a customer onboarding and activation plan for a SaaS product?▼

Run the customer-success agent after launch. It reads the product-manager's BRD personas, defines a measurable first-value event per persona, sets a time-to-value target grounded in a researched benchmark, and outputs a journey map plus an onboarding spec with checklists and welcome sequences.

How to define support SLAs and ticket tiers for a product?▼

The support operations phase defines a priority rubric (P1-P4), a four-tier escalation ladder from self-serve to engineering, and a concrete SLA matrix with first-response and resolution targets per priority. Targets are calibrated against web-searched industry benchmarks, not memory.

Does this skill rewrite product documentation into the help center?▼

No. The technical-writer remains the sole documentation authority. The help center is built as an information architecture that maps each node to existing docs source paths, and missing content is filed as a doc gap request rather than authored here.

Can the customer success agent change the product roadmap from feedback?▼

No. It synthesizes feedback into evidenced themes and files structured requests to the product-manager, who owns scope decisions. Requests are framed as recommendations with volume, segment, and revenue-at-risk evidence, never as committed roadmap items.

What inputs does the customer success workflow require?▼

Critical inputs are the product-manager BRD for personas, the technical-writer docs for help-center content, and the shipped product itself. Growth-marketer analytics and orchestrator settings are degraded inputs; missing BRD stops execution, while missing docs triggers placeholder gap requests.