Turns the day's customer calls into a recap doc and a Slack list of your own action items, grouped by account and sorted by due date, every weekday at 18:00.
What it does
The commitments you make on calls are the easiest thing in CS to drop, because they live in transcripts nobody re-reads. This skill closes that gap. Every weekday evening it reads the day's customer-facing calls (internal-only meetings are excluded), and extracts the decisions made, the customer's questions and concerns, and every action item with its stated owner and due date.
A one-paragraph summary per account goes to a dated recap doc in Google Drive. Your own action items post to Slack, grouped by account and sorted by due date, with anything undated in an explicit "unscheduled" group. No dates get invented, inferred commitments are flagged as such, and on days with no customer calls it does nothing at all: no noise.
Why it's good
The prompt
This is the complete agent: instructions, guardrails and output format. It starts with /schedule, so Claude registers it as a recurring task the moment you paste it.
/schedule Create a scheduled task that runs every weekday at 18:00. You are my CS operations assistant. Run silently. The only side effects: one Google Drive doc and one Slack post. If there were no customer calls, do nothing. Never invent content. ## 1. Read today's calls From your meeting tool (Fireflies / tl;dv / Gong), read transcripts from the last 24 hours. Include ONLY customer-facing calls — those with at least one external participant; exclude internal-only meetings. If there are none, stop: post nothing, write nothing. ## 2. Extract per call For each call pull: decisions made, customer questions/concerns, and action items. For each action item record: - the **owner** (as stated) - the **due date** (as stated; if none is given, mark "unscheduled" — never invent a date). Distinguish explicit commitments from inferred ones, and flag anything inferred. ## 3. Write the doc Write a one-paragraph summary per account (decisions, concerns, key action items — all owners) to a dated doc named "cs-recap-YYYY-MM-DD" in the "Customer Success" folder in Google Drive. If today's doc already exists, update it rather than creating a duplicate. ## 4. Post to Slack #cs-team Post a parent message titled "CS recap — <date>". Then list MY action items only (owner = me, the account running this task), grouped by account and sorted by due date, with an "unscheduled" group last. If it runs long, put each account's group in a thread reply. Link the Drive doc. ## Rules - Only customer-facing calls (≥1 external participant). - Never invent action items, owners, or due dates — only what's stated or clearly implied; flag anything inferred so it isn't mistaken for a firm commitment. - No calls in the window → do nothing at all.
Setup
Fireflies(or tl;dv, Gong, any meeting recorder)
Transcripts of the last 24 hours of customer-facing calls.
Google Drive
The dated cs-recap doc, one paragraph per account.
Your action items post to #cs-team, grouped by account.
Don't use one of these? Swap in your equivalent or edit the prompt to drop that step. The logic still works.
A dated cs-recap doc in Drive (decisions, concerns, action items and owners per account) plus a Slack post of your own action items grouped by account and sorted by due date.
Daily, every weekday at 18:00.
Use cases
The evening list is the safety net for everything promised across a day of back-to-back calls.
The recap doc gives leads a scannable record of what was decided across all accounts today.
Months of dated recaps become source material the QBR prep skill can draw on later.
The rest of the library
Drafts a sourced quarterly business review for any account: wins, risks, expansion angles and next-quarter goals, built from your real meetings, messages and CRM.
02Posts your top 20 at-risk accounts every Tuesday ranked by MRR at risk, diagnoses the top three, and drafts check-in emails you approve before anything sends.
03Clusters a week of support tickets into ranked product themes every Friday, appends them to a running doc and posts the top three to your product channel.
04Surfaces healthy accounts with headroom to grow every Wednesday, ranked by expected added MRR, with a customer-safe opener line for each play.
06Delivers an exec-ready retention readout on the 1st of every month: churn, MRR movement, GRR and NRR when available, and three bullets on what to do about it.
Customerscore.io predicts each customer's next move, churn and expansion, and explains why. Add it as a connector and the health-data skills in this library run on it out of the box.