playbook-auditor

Audit CS playbooks for coverage gaps, trigger vagueness, and adoption weaknesses.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill playbook-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-auditor
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/cs-ops/skills/playbook-auditor
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill playbook-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies whether your CS playbooks are complete, measurable, and actually being used so you can pinpoint where the system will fail before it impacts churn, renewals, or expansion.

Core Features & Use Cases

  • Playbook coverage audit: Maps configured plays against a baseline of common CS scenarios to surface coverage gaps by category and severity.
  • Trigger and outcome quality checks: Evaluates trigger specificity (the “two CSMs, same account, same moment” test) and verifies outcomes are observable and TARO-complete.
  • Adoption and dead-play detection: Analyzes play activation and closure rates (when activation history exists) and flags plays that appear dead or underused.

Quick Start

Run: use the playbook-auditor skill to perform a full quarterly audit of play coverage, trigger quality, outcomes, adoption, and dead plays.

Frequently Asked Questions about playbook-auditor

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

FAQPage Schema
How do I audit customer success playbooks for coverage gaps and adoption weaknesses?

Auditing customer success playbooks involves mapping configured plays against common CS scenarios to surface coverage gaps by category and severity, while analyzing activation and closure rates to detect adoption weaknesses and dead plays.

How do I evaluate trigger specificity and outcome measurability in CS playbooks?

Evaluating trigger specificity in CS playbooks applies the 'two CSMs, same account, same moment' test to verify triggers are unambiguous, while outcome measurability checks ensure outcomes are observable and TARO-complete.

What is the TARO framework for playbook auditing?

The TARO framework is a quality standard used during playbook auditing to enforce that play outcomes are fully measurable and observable, ensuring governance guardrails are met and play effectiveness is trackable.

Can I detect dead or underused plays without extensive activation history?

Detecting dead or underused plays requires access to play activation history to analyze closure rates, but playbook coverage and trigger quality audits can still be performed with just a configured play list of trigger conditions and outcomes.

How often should I run a playbook coverage audit for customer success operations?

A playbook coverage audit should be run during quarterly playbook reviews to systematically identify missing plays, trigger vagueness, and outcome measurability issues before they impact churn, renewals, or expansion.

What data do I need to identify ineffective or missing CS plays?

Identifying ineffective or missing CS plays requires a configured play list with trigger conditions and outcomes, plus optional activation history for adoption analysis to flag plays that appear dead or underused.