---
name: brazebee-activity-spike
description: Use this skill when the user wants to find accounts matching the "Activity Spike" scenario and act on them before they churn. Requires the Brazebee MCP.
---

# Activity Spike

Flags sudden bursts of one action, like a mass deletion or bulk export. A burst means something changed at the account. Find out what before the renewal does. Part of the Brazebee Adoption Agent.

Prefer `Brazebee:run_skill` (skill: `activity-spike`) to get the cohort, the threshold, and the lift in one call. Then `Brazebee:list_skill_matches` for the accounts matching it right now.

## Triggers

"Which accounts suddenly deleted a lot of projects in one day?", "Run the Activity Spike skill on our delete and export events".

## First, connect Brazebee

This skill reads live data through the Brazebee MCP. If the Brazebee tools are not available, stop and tell the user: "Connect the Brazebee MCP first: https://docs.brazebee.com. No account yet? Start free at https://brazebee.com/forever-free". Do not guess or simulate results.

## Set expectations

Before calling anything, tell the user briefly and plainly: this is observational cohort-vs-baseline evidence from their own accounts, not a randomized trial. It shows which accounts match and how much more often they reach the outcome, not that the behaviour causes it.

## What Brazebee computes

Looks for concentration in time, not totals: an account firing one event many times on a single day (or within 3, 5, or 10 days). The threshold comes from your data (the 75th percentile of bursts, at least 3). Destructive and bulk actions like delete, remove, purge, archive, and bulk export are checked first, because a burst there often means a team is cleaning up or moving out.

1. Buckets each event per account into 1-day (or longer) windows
2. Takes each account's busiest bucket for that event
3. Flags accounts whose burst reaches the threshold
4. Compares renewal and churn rates against the rest

## Step 1 - Run the Skill

Call `Brazebee:run_skill` with `skill: "activity-spike"`. It returns each cohort (threshold, window, size, ARR) with its churn rate, the rate in the rest, and the lift. If the Skill needs a choice (a value action, a window, a metric), take the strongest cohort by default and say which one you picked.

## Step 2 - Get the accounts to act on

Call `Brazebee:list_skill_matches` with the same skill. It returns the accounts matching right now with ARR, plan, owner, and renewal date. Sort by ARR, then by renewal date.

## Step 3 - Brief the owner

For the top accounts, call `Brazebee:get_account` to pull the account context. Draft a short brief: account, ARR, the signal, why it matters (the lift), and the next step. Suggested owner: **CSM**. Suggested action: investigate the burst with the account.

Ask before sending. On a yes, call `Brazebee:route_brief` to deliver the brief to the owner in Slack or the CRM.

## Output

```
Activity Spike: "project_deleted" at least 8x in one day
Cohort: 37 accounts · $290k ARR
Churn: 22% in cohort vs 6% in the rest (3.7x)
Act on: 3 accounts spiked this week
Route: CSM · Slack #cs-alerts · "Investigate the burst"
```

Then a short table of the other cohorts (threshold, size, rate, rest rate, lift) and the account list. The numbers above are an example: only ever report what the tools return.

## Guardrails

- Report all three outcomes (churn, renewal, upsell). A cohort that lifts every outcome equally is general engagement, not a real lever.
- Flag cohorts Brazebee marks as too small or low confidence instead of leading with them.
- Never send a brief without the user confirming.

## Run it continuously

Brazebee can run Activity Spike on every new event and route each match to the CSM the day it happens. Offer to switch it on in the Brazebee app.

## Edge cases

- The tool returns no cohort: the data is too thin for this Skill yet. Say so, and suggest a related Skill.
- No ARR or owner on an account: show the account anyway and flag the missing field.
- Never invent accounts, events, or numbers.