staircase-churn-review

staircase-churn-review is a skill for Claude Code from gs-bbluhm/gainsight-mcp-plugins. It costs 125 tokens per session (2,697 once invoked), scanned A, original, MIT.

A quarterly review of customers who left, called churn, and the reasons they left. It also looks at negative themes that are increasing among current customers, which can signal future churn.

In plain words
What is it for?
Use it to summarise churned accounts, group their reasons, compare lost revenue by customer tier, and identify rising problems among active customers.
Why use it?
It combines a retrospective of lost customers with early warning signs from the remaining customer base. This helps a team learn from past losses while looking for ways to prevent the next ones.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the staircase plugin — 14 skills shipped together

Good fit Use it to summarise churned accounts, group their reasons, compare lost revenue by customer tier, and identify rising problems among active customers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gs-bbluhm/gainsight-mcp-plugins --skill staircase-churn-review
Clone the repo
git clone --depth 1 https://github.com/gs-bbluhm/gainsight-mcp-plugins

Made for: Claude Code.

Or install staircase, the plugin that ships this one along with the rest of its 14 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for staircase-churn-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review/github.svg)](https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review)
Your own site
<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for staircase-churn-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-churn-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00125 $0.02697
Opus 5.5 $0.00050 $0.01079
Sonnet 5.5 $0.00025 $0.00539
Haiku 4.5 $0.00013 $0.00270

Measured 25d ago against content hash 4a9eb81546b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

staircase-churn-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 25d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/staircase/skills/staircase-churn-review/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Staircase Quarterly Churn Review

A churn retrospective with a forward edge. Half of it is the post-mortem: who churned this quarter, the lost revenue, and the reasons, straight from the Churn analyst's stored synopses and issue lists. The other half is the leading indicator: which negative themes are rising across the accounts you still have, so the review ends in prevention, not just accounting. Both halves are structured reports; the churn analyst has already done the reading.

Foundation references

Read before composing queries if you have not this session:

  • ../staircase-mcp-expert/: report mechanics, the parent_topic theme-ranking primitive, field ids.
  • ../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.
  • User profile (~/.staircase-mcp/user-profile.md): the Owner scope for a per-CSM review; a leader may want the whole book (name the scope explicitly).

The two data sources (both verified live)

Half Tool + fields
Retrospective (what/why) customer report filtered status = Churned + churn.churn_date in the quarter. Columns: customer.churn.churn_date, customer.revenue, customer.tier, customer.churn.issues (Collection of reason phrases), customer.churn.synopsis (AI Churn Analysis narrative).
Leading indicators (what's rising) parent_topic report with the trend fields: accounts_count, negative_sentiment, current_period_volume, previous_period_volume, absolute_growth_percentage. Rank by growth% x negative volume to find themes heating up across the active book.

Step 0: Scope + quarter

  • Scope: leader review = whole book (say so); CSM review = their book through the resolved book-owner field (customer.<book_owner_field> In [<user_id>], or customer.<book_owner_field>.full_name In ["<name>"] for a named CSM). Never assume customer.owner.
  • Quarter: default the trailing 90 days; ask if they mean a named fiscal quarter, and set the churn_date window accordingly.

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 25d ago First seen · 128 lines · 125 tokens per session scan A 4a9eb81546b5

Subscribe to this mod's changes

staircase-churn-review is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 125 tokens to every session and 2,697 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens