CSM playbooks.

Six skills that make the core CSM workflows consistent for everyone — prep, follow-up, health check, handover, the Monday briefing, and the weekly account notes.

The CSM playbook system

Six Claude Code skills standardize the core CSM workflows (five you invoke on demand, plus weekly-account-notes which runs on a schedule). They share one discipline: pull from real sources first (Attio, Gmail, tl;dv, Granola, Calendar, Slack), then produce a consistent artifact — and never fabricate pricing, dates, or commitments that aren’t in the record. They are installed in every CSM’s ~/.claude/skills/ (see Tooling).

Which playbook, when

TriggerSkillOutput
Prepping for any client call, QBR, or check-in/csm-account-prepOne-page meeting brief
Right after a client meeting/csm-follow-up-emailDrafted follow-up email (transcript-grounded)
Weekly book review/csm-health-checkRisk dashboard + prioritized action list
Reassigning an account to another CSM/csm-handoverPDF in Drive + Slack post + Attio note + intro email
Every Monday, before the week's calls/csm-monday-briefingEnablement briefing + three updated KB files
Every Friday evening (scheduled)Weekly Account NotesA note on every touched Attio account + a Gmail summary
One rule above all. If a transcript, email, or CRM record doesn’t say it, the playbook doesn’t write it. Flag the gap instead of guessing — a confident wrong number erodes trust faster than a question.

Source: the csm-account-prep, csm-follow-up-email, csm-health-check, and csm-handover SKILL.md files (Google Drive, current 2026-05-21) and the CSM Claude Code Setup guide.