Cs Playbooks

Q: Why use Cs Playbooks on TypingMind?

Because you install it once and use it with any model. Cs Playbooks is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

Q: How do I install Cs Playbooks in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LeadMagic/gtm-skills/tree/main/skills/customer-success/cs-playbooks. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Q: Which AI models can use Cs Playbooks?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

Q: How many AI models can I use with Cs Playbooks?

As many as you like. As long as a model supports skills, you can use Cs Playbooks with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Q: Is the Cs Playbooks AI skill free?

Yes. It is published on GitHub by LeadMagic under the MIT license. You only pay your own AI provider for the tokens you use.

Q: What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

Q: How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Organization

LeadMagic

cs-playbooks

Build customer success playbooks — onboarding, health scoring, CSQLs, expansion plays, QBRs, and churn intervention. Use when building a CS function, designing customer journeys, or creating playbooks for retention and expansion. Triggers on: "customer success", "CS playbook", "onboarding", "health score", "CSQL", "expansion play", "customer retention", "QBR", or any request about post-sale customer engagement.

Overview

Publisher	LeadMagic
Repository	`gtm-skills`
Skill name	`cs-playbooks`
Stars	72
Forks	18
Bundled files	8
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
8 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by LeadMagic on GitHub. Read the source before you install it.

Installation

Install the Cs Playbooks AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/LeadMagic/gtm-skills/tree/main/skills/customer-success/cs-playbooks
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/LeadMagic/gtm-skills.git /tmp/gtm-skills
mkdir -p .claude/skills
cp -r /tmp/gtm-skills/skills/customer-success/cs-playbooks .claude/skills/cs-playbooks

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cs Playbooks in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cs Playbooks on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cs Playbooks is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Customer Success Playbooks

Overview

Customer Success is not reactive support — it is proactive value delivery that drives retention and expansion. This skill builds the CS operating system: Desired Outcome mapping (Lincoln Murphy), health scoring with leading indicators (Gainsight), CSQL identification for expansion, and playbooks per customer lifecycle stage.

When to Use

"Build our customer success function"
"Design customer onboarding"
"Create a health score model"
"Set up expansion plays"
"Build QBR templates"
"Customer comms during outage / incident"
"CS crisis FAQ for support"
"Retention crisis — churn wave response"

Authoritative Foundations

Lincoln Murphy — Desired Outcome framework. Every customer has a Required Outcome and an Appropriate Experience. Success is their outcome, not your feature usage. The Success Gap: customers using the product correctly but still failing.
Nick Mehta / Gainsight — CS ops at scale: health scores, lifecycle stages, digital-first delivery. Operational layer on Murphy's strategy. → references/lincoln-murphy-customer-success.md
Allison Pickens — company-wide Customer Success. Treat retention and value delivery as a cross-functional operating model, not a CSM-only responsibility. Align post-sales roles around customer outcomes and use product signals to prioritize human intervention without confusing activity with value.
Winning by Design SPICED — Post-sale lifecycle: onboarding → adoption → value realization → expansion → renewal.

Step-by-Step Process

Phase 1: Map the Customer Journey

Define stages: Onboarding → Activation (Day 1-7, aha moment) → Habit Formation (Week 2-6, usage signals) → Indispensability (Month 2-6, workflow integration) → Expansion → Renewal. Each stage has a milestone metric.

Phase 2: Build Health Scoring

Score 0-100: product usage (0-40), engagement depth (0-30), relationship health (0-30). Red (<50): immediate CSM outreach. Yellow (50-74): automated nurture. Green (75+): expansion targeting.

Phase 3: Define CSQLs (Customer Success Qualified Leads)

Behavioral signals of expansion readiness: usage nearing plan limits, feature adoption in new department, new stakeholders in meetings, "can we do X?" questions, willingness to be a reference.

Phase 4: Build Playbooks per Stage

Onboarding play: time-to-first-value target, guided setup, success milestone
Adoption play: usage monitoring, best practice sharing, feature education
Expansion play: triggered by CSQLs, framed as "logical next step" not upsell
Risk play: early warning signals, intervention cadence, executive alignment
Renewal play: value review, ROI documentation, future roadmap alignment

Phase 5: Incident & Crisis Customer Comms

Canonical: references/crisis-management-playbook.md · Pattern 33 · Executive home: gtm-leadership

Role	CS responsibility
CS captain	Own customer email to affected segment; ticket macros
CSMs	Proactive outreach to red health accounts during outage
Support	Single FAQ source — the `gtm-leadership` skill (crisis-faq-for-support.md)

Sequence: Internal memo → holding statement / status page → affected customer email → FAQ for sales/support.

ACKNOWLEDGE → OWN → ACT → FOLLOW UP in all customer-facing copy. Legal review Sev 3+ before admitting data impact.

Post-incident: Retention play for accounts that churn-threatened; link churn-prevention and Retention stage in references/gtm-lifecycle-stages.md.

Cross-links: customer-onboarding (trust rebuild) · references/gtm-data-exchange-playbook.md (breach path)

Output Format

CS playbook with journey map, health score model, CSQL definitions, and stage-specific play templates.

Quality Check

Before delivering, verify:

All required sections are complete
Output matches the user's stated need
Named frameworks are cited for key recommendations
No vague claims — every recommendation has a specific action
Deliverable is ready for operational use, not just conceptual

Common Pitfalls

Measuring activity, not outcomes — logins are not value. Map customer Desired Outcomes and measure progress toward them.
CS as firefighting — if CSMs only engage when something is wrong, they are reactive support, not customer success.
No expansion motion — CS owns the relationship. If expansion lives only in Sales, the customer gets handed off at the worst moment.
One-size health score — different segments need different health models. Enterprise cares about executive engagement; SMB cares about time-to-value.

Execution Artifacts

references/framework-notes.md — named frameworks, citation anchors, and operating assumptions
templates/output-template.md — copy-paste deliverable structure for the user
scripts/check-output.py — local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand:
references/lincoln-murphy-customer-success.md — Desired Outcome, Success Gap, Gainsight ops Canonical lifecycle: references/gtm-lifecycle-stages.md (Engagement, Retention) · references/lifecycle-metrics-by-stage.md · the gtm-metrics skill (stage-health-scorecard.md) Crisis comms: references/crisis-management-playbook.md · the gtm-leadership skill (crisis-customer-email.md) · crisis-faq-for-support.md Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions

What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?

Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

Lincoln Murphy Desired Outcome: apply only the part that directly improves the requested deliverable.
Gainsight CS Index: apply only the part that directly improves the requested deliverable.
Winning by Design SPICED Post-Sale: apply only the part that directly improves the requested deliverable.
Allison Pickens company-wide and product-driven CS: apply only the part that directly improves the requested deliverable.

Deliverable Standard

A strong output from this skill includes:

A crisp diagnosis of the current situation
A recommended path with tradeoffs, not a generic list
A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
A measurement plan with leading and lagging indicators
Risks and edge cases called out before execution

Adaptation Rules

For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.

Related Skills

gtm-leadership: Executive war room and crisis severity (canonical)
customer-marketing: Public reputation, G2/TR during incidents
customer-onboarding: Post-incident trust and activation recovery
churn-prevention: Early warning detection and re-engagement
expansion-selling: Upsell and cross-sell motions
qbr-planning: Quarterly business review structure

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cs Playbooks AI skill do?

Why use Cs Playbooks on TypingMind?

Because you install it once and use it with any model. Cs Playbooks is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cs Playbooks in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LeadMagic/gtm-skills/tree/main/skills/customer-success/cs-playbooks. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cs Playbooks?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cs Playbooks?

As many as you like. As long as a model supports skills, you can use Cs Playbooks with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cs Playbooks AI skill free?

Yes. It is published on GitHub by LeadMagic under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Insight Error Page

vercel

OrganizationPopular

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix…

Mcp Apps Builder

**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP…

Canary

Post-deploy canary monitoring. (gstack)

Land And Deploy

Land and deploy workflow. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Customer Success Playbooks

Overview

When to Use

Authoritative Foundations

Step-by-Step Process

Phase 1: Map the Customer Journey

Phase 2: Build Health Scoring

Phase 3: Define CSQLs (Customer Success Qualified Leads)

Phase 4: Build Playbooks per Stage

Phase 5: Incident & Crisis Customer Comms

Output Format

Quality Check

Common Pitfalls

Execution Artifacts

Implementation Depth

Diagnostic Questions

Framework Application

Deliverable Standard

Adaptation Rules

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now