/csm-monday-briefing.

The fifth weekly CSM playbook. Where /csm-health-check scans the book for account risk, this scans the week's meetings for product knowledge and upsell signal — banking it in a living knowledge base and coaching three concrete moves for the week ahead.

The throughline — never fabricate. Like every csm-* skill, the briefing reads from real sources before it writes anything. Every fact traces to a meeting, thread, or record. Pricing, dates, and commitments come from the source, never from memory. Anything that can't be reconciled is flagged, not guessed.

When to run it

Every Monday morning, before the week's calls. It is the knowledge-and-coaching bookend to the weekly health check: run the health check to triage accounts, run the briefing to absorb what the prior week taught you about the product and the deals.

When	Do this	Playbook
Before every client call or QBR	Pull a one-page brief	/csm-account-prep
After every client call	Draft a tight follow-up from the transcript	/csm-follow-up-email
Weekly book review	Scan all accounts for risk	/csm-health-check
Every Monday	Mine last week's meetings for product knowledge + upsell signal; coach 3 moves	/csm-monday-briefing
On any account reassignment	Generate the handover PDF + Slack post + intro email	/csm-handover

What it does

Seven steps, all read-only except for writing the CSM's own KB files and the HTML output:

Pull the week's meetings (Granola) — every meeting where the CSM is a participant, last 7 days. Full summaries for internal and external. External meetings are mined for product/upsell signal only — they are not recapped.
Read the three KB files — product-knowledge.md, upsell-crosssell-playbook.md, stats-history.md.
Extract new facts — pricing, MOQs, lead times, fees, decoration rules, suppliers, integrations, platform features, bugs, margin reference, client Q&A; plus cross-sell/upsell patterns, best practices, discovery questions, quotes, objection handling, client hooks, pricing tactics.
Append to the KB — each fact at the top of its section, dated and source-tagged; contradictions updated in place.
Update stats history — calls, external/internal split, new KB entries, lost deals, new signs — enabling week-over-week and month-over-month tracking.
Generate the HTML briefing — dark theme, fixed section order, body under 1,500 words.
Output — link the HTML, a 4-6 line exec summary, and the three updated KB files.

CSM-agnostic by design

The skill resolves who it runs for at invocation, so every CSM gets their own briefing on their own book — not a copy of someone else's accounts.

Parameter	Default
`CSM_NAME` / `CSM_EMAIL`	The invoking user
`GRANOLA_SCOPE`	Meetings where the CSM is a participant, last 7 days
`ATTIO_VIEW`	The CSM's accounts (Attio `csm` field)
`KB_DIR`	The CSM's knowledge-base folder (falls back to the run's output folder if unreachable)

What it produces

A single dark-theme HTML briefing with a fixed section order: Stats What changed Watchlist Coach's 3 moves Consolidated KB Product additions Playbook additions Prompt notes. Plus three updated, source-tagged KB markdown files that accumulate week over week.

Write boundary. This playbook is read-and-report. It writes only to the CSM's own KB files and the HTML output. It never sends email, posts to Slack, or edits Attio, Notion, or Linear — any outbound action stays with the CSM.

Source: generalized from the original Monday Briefing scheduled prompt (S. Yidi, May–Jun 2026) and the prompt-improvement notes from the 2026-06-22 run (KB-path fallback; reused-meeting-title handling). Skill file: csm-monday-briefing/SKILL.md.