Claude Skills for CSMs
The FunnelStory skills package teaches Claude how to turn your FunnelStory data into finished deliverables — an account brief, a QBR deck, a churn risk report — in a single request. Claude reads your data live through the FunnelStory MCP server, so every number comes from your workspace rather than a copy-pasted export.
How it works
The package is one skill, named funnelstory, with a sub-skill for each deliverable. You don't pick a sub-skill or type a command: you ask in plain language, and the skill routes your request to the right workflow. For example, "Why is this account's health score low?" goes to the health score breakdown, while "Tell me about this account" goes to the account brief.
When a request is ambiguous, Claude asks before it starts. A request for a "QBR", for instance, prompts "Is this for internal prep or to present to the customer?"
Setting up
- Connect the FunnelStory MCP server in Claude. See MCP Getting Started. This is the only hard requirement: without it, the skills have no data to read.
- Add the skills package. Download it from the public funnelstory/skills repository and add it as a custom skill:
- Claude (desktop or web): add the folder that contains
SKILL.mdand its sub-folders as a custom skill. See Using skills in Claude. - Claude Code: copy or symlink the whole folder into
~/.claude/skills/, keepingSKILL.mdnext to its sub-folders.
- Claude (desktop or web): add the folder that contains
- Ask naturally. Start with something like "Show me my book of business".
For requests about your accounts (book of business, what to do today, churn risk, renewals), the skill calls who_am_i and uses that email to find the accounts assigned to you. It asks you for an email only if that lookup fails. If none are assigned, it tries owner fields on the account, then asks you to name your accounts.
Health on every skill uses the same tiers as Focus Areas: Critical at 45 or below, At risk from 46 to 54, and On track at 55 or above. An account with no score is unscored. An open needle mover, a renewal date, or a churn prediction is reported next to the tier. It does not move the account into a different tier.
Most skills look at the last 90 days by default. You can widen or narrow the window in your request — for example, "…over the last 6 months".
Start the day
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Prioritize my day | Open Action Cards on your book, then Critical or At risk accounts and renewals inside 90 days that have no card | "What should I do today?" | Answer in chat |
Account intelligence
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Account brief | Internal summary of one account: ARR, renewal date, product usage, support history, open Needle Movers, health and prediction, and recommended next steps | "Give me an account brief for [Account]" | PDF (Claude asks first; Markdown or Word on request) |
| Book of business | A dashboard of your assigned accounts with health tier (Critical, At risk, On track, or Unscored), adoption, days to renewal, and two drivers per account, with filters and drill-down | "Show me my book of business" | HTML |
| Health score breakdown | The current score, its trend, the contributing factors, top positive and negative drivers with citations, and three actions | "Why is [Account]'s health score low?" | Markdown |
| Account support history | Recent tickets, open escalations, and support conversations for one account, open and escalated items first | "What's open with [Account]?" | Answer in chat |
Meeting and call preparation
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Meeting prep | A pre-call brief: who you are meeting, upcoming calendar invites, recent recorded calls, notes, open Needle Movers, action cards, and support. Themes come from content labels | "Prepare me for my call with [Account]" | Markdown in chat |
Risk management
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Churn risk report | Accounts ranked by health tier (Critical, At risk, On track), with top drivers, renewal date, and a recommended next action and owner | "Which accounts might churn?" | HTML |
| Renewal dashboard | Accounts renewing in the next 90 days (configurable), ranked by churn likelihood, with a suggested pre-renewal action for each | "What's my renewal pipeline?" | HTML |
| Executive sponsor coverage | Named sponsor, last executive touch, and a suggested action per account; highlights missing or stale sponsors | "Which accounts are missing exec engagement?" | HTML |
The churn risk report covers every at-risk account regardless of renewal date. The renewal dashboard covers only upcoming renewals.
Growth and expansion
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Expansion dashboard | Accounts with room to grow seats, users, or sites, with a suggested next play | "Which accounts can grow seats?" | HTML |
| Upsell dashboard | Accounts ready for a higher tier, premium module, or add-on, with evidence and a one-line talk track | "Which accounts can upgrade?" | HTML |
| Adoption gap | Accounts under-using what they bought, each with a severity and one enablement recommendation | "Where's the shelfware?" | HTML |
| Lead reports | Hot leads, product-qualified leads, or trial conversion opportunities, as a card-based email-ready report | "Show me this week's hot leads" | HTML |
Customer reviews and communication
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Internal QBR deck | Executive summary, health and prediction trends, product usage, meetings and notes, support, open Needle Movers, and next-quarter priorities. Marked "Not for customer distribution" | "Create an internal QBR deck for [Account]" | PowerPoint |
| Customer-facing QBR deck | Value delivered this quarter, adoption framed positively, milestones, and a looking-ahead section. Leaves out internal scores, predictions, and risk flags | "Create a customer QBR deck for [Account]" | PowerPoint (HTML or Markdown on request) |
| Value email | A subject line, impact bullets with numbers, and a looking-ahead paragraph, as email-safe HTML | "Write a value email for [Account]" | Markdown plus HTML |
| Case study | A publication-ready case study with headline, stat cards, challenge, solution, and results, grounded in FunnelStory data with no invented quotes | "Write a case study for [Account]" | HTML |
See Quarterly Business Reviews for how the QBR decks fit into review prep.
Strategic planning
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Success plan | A 30/60/90-day plan: gap summary, actions with owners, dates, and success metrics, milestones, and risks. Creating those tasks in FunnelStory is a separate request | "Build a plan to improve health for [Account]" | Markdown |
Product and marketing
These deliverables look across all accounts rather than your book, so Claude doesn't ask for your email.
| Deliverable | What you get | Try asking | Default output |
|---|---|---|---|
| Feature requests | What customers are asking for, drawn from Needle Movers, notes, content labels, and tickets, ranked by how often they come up and by contract value | "What are customers asking for?" | HTML |
| Adoption funnel | Which features are used, by how many accounts, and where adoption drops off | "Which features are under-adopted?" | HTML |
| Customer ROI stories | Short, metric-backed ROI snippets across several accounts, ready for decks and campaigns | "Give me ROI stories from our top accounts" | Markdown |
Flows, projects, and data models
These are in the same package. Creating or editing a flow, a project, or a data model requires a workspace admin. Creating a task does not.
| Deliverable | What you get | Try asking |
|---|---|---|
| Flow | A new or updated flow, after Claude reads the flow guide | "Create a flow that posts a weekday health summary to Slack" |
| Project or task | A project for an account, or a task (for example, the actions from a success plan) | "Add these plan actions as tasks" |
| Data model | A preview, then a saved model | "Map this query into an account model" |
A typical day
- Morning: ask what you should do today, then your book of business if you want the full snapshot.
- Before a call: ask Claude to prepare you for the call.
- After a call: log notes in FunnelStory, then ask for a success plan if the call needs a 30/60/90. Ask to add the actions as tasks if you want them in the product.
- QBR week: generate the internal deck for team prep, then the customer-facing deck.
- End of quarter: ask for the renewal dashboard to prioritize the next 90 days.