Usage Pulse / CS Health Check (internal)
The anti-churn nudge. For a single customer account, this internal CS skill
reads where the account is — its plan tier, what it's actually been running,
where it's leaving value on the table — and produces a short, warm "3 things to
try this week" email with copy-paste prompts, so a CSM can send activation in
five minutes instead of writing it cold. The job-to-be-done: turn a quiet
account into an active one before it lapses. The artifact is a per-account
health read plus a ready-to-send email.
v1 capability note. There is no account-usage telemetry tool on the MCP
yet (it's wishlist item 5, get_account_usage, tracked in CRE-543). Until it
lands, this skill takes the account's current usage as an operator-supplied
input — pasted from the billing/admin dashboard, an export, or the CSM's
notes — and does not fabricate usage it cannot see. When the telemetry tool
ships, step 1 below becomes a tool call and the rest is unchanged.
Read first: ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md (tool schemas, credit
prices, the conventions). This skill honors thrifty/thorough credit modes
(${CLAUDE_PLUGIN_ROOT}/shared/credit-modes.md) and Refusal Recovery
(${CLAUDE_PLUGIN_ROOT}/shared/refusal-recovery.md). It is near-zero-credit: it
reasons over the skill catalog and the account's profile, and makes at most one
optional market-intel call to season a prompt with a live number.
Inputs to collect
- Account (required) — name/segment (agency, brand, talent manager) and
plan tier (free / pro / pilot). Tier gates which skills are even
available, so it shapes every recommendation.
- Current usage (required for v1, operator-supplied) — what the account has
run recently: which skills/workflows, rough call volume, credits consumed vs
granted. Paste from the billing/admin dashboard. If the user can't supply it,
say plainly that v1 can't read usage itself and proceed on tier + segment
alone, clearly labeling the read as "tier-based, not usage-based".
- Their vertical / who they cast for (optional) — lets prompts be
pre-filled with the account's real vertical instead of a placeholder.
- Known goals or friction (optional) — anything the CSM knows (e.g. "they
only ever run shortlists, never pricing"). Sharpens the gap analysis.
- Mode — default
thorough; thrifty skips the optional live-number call.
Flow
This skill is mostly reasoning, not tool calls.
Read the account (v1: from the operator-supplied usage; future: a
get_account_usage call). Establish tier, what's been used, what's been
granted vs consumed. No credits in v1.
Map the opportunity (no tool calls) — diff the account's actual usage
against the catalog of skills its tier unlocks but it isn't using. Weight
by fit to the account's segment and vertical:
- Agencies idle on
brief-to-shortlist/cross-market-slate -> casting depth.
- Brands not touching
vertical-briefing/competitor-watch -> market intel.
- Anyone on pro never running pricing ->
fair-price-brief/rate-card-generator.
Pick the 3 highest-leverage unused workflows for this account — concrete,
not the whole menu.
Season one prompt with a live number (thorough only, optional) — at most
one query_market_intelligence { mode: "rate" | "market", vertical: <their vertical> } (5 credits, wrapped in Refusal Recovery) — in rate mode you
may optionally add creator_tier (emerging <1k / nano 1k-10k / micro 10k-100k / mid 100k-500k / macro 500k-1M / mega 1M+)
for a tier-specific hook, or omit it (the default) for the vertical-wide
band — so a recommendation
can carry a real "median rate in your vertical is $X — here's the skill that
uses it" hook. Skip in thrifty. Never imply this number is account-specific;
it's a vertical market band (convention 2).
Write the email (no tool calls) — warm, short, 3 concrete suggestions,
each with a one-line "why it helps you" and a paste-ready prompt the
account can drop straight into their session. Respect tier: never recommend a
workflow their tier doesn't unlock — instead, if the highest-value next step
is gated, frame it as the upgrade reason, honestly.
Credit footprint is ~0–5 credits total (one optional market call). No pre-run
estimate needed.
Deliverable
# Usage pulse — <Account> (<tier>, <segment>)
*Prepared <date> · read basis: <"usage dashboard, <date>" / "tier-based only —
usage not supplied">*
## Health read
- Using well: <skills/workflows they already run>
- Leaving on the table: <tier-unlocked workflows they aren't using>
- Risk note: <e.g. "low credit consumption vs grant — activation risk"; only if
usage was supplied>
## The 3 to try this week
1. **<Skill / workflow>** — <one line why it fits this account>.
2. **<Skill / workflow>** — ...
3. **<Skill / workflow>** — ...
## Ready-to-send email
> Subject: 3 quick wins in Creatorland this week
>
> Hi <name>,
> <2-3 warm sentences.>
>
> 1. **<Win>** — <why>. Try this:
> `<paste-ready prompt, pre-filled with their vertical>`
> 2. ...
> 3. ...
>
> <Soft close + offer to walk through one live.>
---
**Read basis:** <usage source + date, or the honest "tier-based, usage not
read in v1 — no account-telemetry tool yet (CRE-543 wishlist item 5)">.
**Provenance (if a live number was used):** <the market-intel provenance line,
verbatim, + recency window — and it is a vertical market band, not this
account's data>.
Credits used this run: ~N (0 if thrifty / no live number; 5 if one market call)
Honesty rules
- Don't invent usage. v1 has no telemetry tool. If usage wasn't supplied,
the read is explicitly "tier-based, not usage-based" — never a fabricated
"you've run X searches". Say what you can and can't see.
- Respect the tier. Never recommend a workflow the account's tier doesn't
unlock as if it were available; if it's the best next step, frame it as an
honest upgrade reason, not a bait.
- Live numbers are vertical market bands (convention 2) — a "$X median in
your vertical" hook is corpus-level context, never the account's own rate or
a creator's rate.
- Provenance survives into the email when a live number is used (convention
- — the paste-ready prompt or a footer carries the citation.
- No contact info in the deliverable (convention 7); the email is to the
account, but creator/brand contact data never appears in it.
- Internal artifact, honest framing. This is a CS tool; the activation
suggestions are genuine fit reads, not upsell padding — recommend what
actually helps the account, in priority order.
Credit footprint
thorough: ~0-5 credits (catalog reasoning is free; one optional market-intel
call is 5, +5 per ladder retry) · thrifty: 0 credits (no live number).
1---2name: usage-pulse3description: Internal CS skill — for one customer account, map what skills/workflows they COULD be running against their plan tier, then write a short "3 things to try this week" email with paste-ready prompts to drive activation and beat churn. Use when the user says "usage pulse for <account>", "CS health check", "what should this account be using", "write an activation nudge", or a CSM is prepping an account review. Deliverable is a per-account health read plus a ready-to-send email. v1 reads the billing/usage dashboard manually — no account-telemetry tool exists yet (wishlist item 5).4---56# Usage Pulse / CS Health Check (internal)78The anti-churn nudge. For a single customer account, this internal CS skill9reads where the account is — its plan tier, what it's actually been running,10where it's leaving value on the table — and produces a short, warm "3 things to11try this week" email with copy-paste prompts, so a CSM can send activation in12five minutes instead of writing it cold. The job-to-be-done: turn a quiet13account into an active one before it lapses. The artifact is a per-account14health read plus a ready-to-send email.1516**v1 capability note.** There is **no account-usage telemetry tool** on the MCP17yet (it's wishlist item 5, `get_account_usage`, tracked in CRE-543). Until it18lands, this skill takes the account's current usage as an **operator-supplied19input** — pasted from the billing/admin dashboard, an export, or the CSM's20notes — and does not fabricate usage it cannot see. When the telemetry tool21ships, step 1 below becomes a tool call and the rest is unchanged.2223Read first: ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md (tool schemas, credit24prices, the conventions). This skill honors thrifty/thorough credit modes25(${CLAUDE_PLUGIN_ROOT}/shared/credit-modes.md) and Refusal Recovery26(${CLAUDE_PLUGIN_ROOT}/shared/refusal-recovery.md). It is near-zero-credit: it27reasons over the skill catalog and the account's profile, and makes at most one28optional market-intel call to season a prompt with a live number.2930## Inputs to collect3132- **Account** (required) — name/segment (agency, brand, talent manager) and33 **plan tier** (free / pro / pilot). Tier gates which skills are even34 available, so it shapes every recommendation.35- **Current usage** (required for v1, operator-supplied) — what the account has36 run recently: which skills/workflows, rough call volume, credits consumed vs37 granted. Paste from the billing/admin dashboard. If the user can't supply it,38 say plainly that v1 can't read usage itself and proceed on tier + segment39 alone, clearly labeling the read as "tier-based, not usage-based".40- **Their vertical / who they cast for** (optional) — lets prompts be41 pre-filled with the account's real vertical instead of a placeholder.42- **Known goals or friction** (optional) — anything the CSM knows (e.g. "they43 only ever run shortlists, never pricing"). Sharpens the gap analysis.44- **Mode** — default `thorough`; `thrifty` skips the optional live-number call.4546## Flow4748This skill is mostly reasoning, not tool calls.49501. **Read the account** (v1: from the operator-supplied usage; future: a51 `get_account_usage` call). Establish tier, what's been used, what's been52 granted vs consumed. No credits in v1.53542. **Map the opportunity** (no tool calls) — diff the account's actual usage55 against the catalog of skills its **tier unlocks** but it isn't using. Weight56 by fit to the account's segment and vertical:57 - Agencies idle on `brief-to-shortlist`/`cross-market-slate` -> casting depth.58 - Brands not touching `vertical-briefing`/`competitor-watch` -> market intel.59 - Anyone on pro never running pricing -> `fair-price-brief`/`rate-card-generator`.60 Pick the **3 highest-leverage unused workflows** for this account — concrete,61 not the whole menu.62633. **Season one prompt with a live number (thorough only, optional)** — at most64 one `query_market_intelligence` `{ mode: "rate" | "market", vertical: <their65 vertical> }` (5 credits, **wrapped in Refusal Recovery**) — in rate mode you66 may optionally add `creator_tier` (emerging <1k / nano 1k-10k / micro 10k-100k / mid 100k-500k / macro 500k-1M / mega 1M+)67 for a tier-specific hook, or omit it (the default) for the vertical-wide68 band — so a recommendation69 can carry a real "median rate in your vertical is $X — here's the skill that70 uses it" hook. Skip in thrifty. Never imply this number is account-specific;71 it's a vertical market band (convention 2).72734. **Write the email** (no tool calls) — warm, short, 3 concrete suggestions,74 each with a one-line "why it helps you" and a **paste-ready prompt** the75 account can drop straight into their session. Respect tier: never recommend a76 workflow their tier doesn't unlock — instead, if the highest-value next step77 is gated, frame it as the upgrade reason, honestly.7879Credit footprint is ~0–5 credits total (one optional market call). No pre-run80estimate needed.8182## Deliverable8384```markdown85# Usage pulse — <Account> (<tier>, <segment>)86*Prepared <date> · read basis: <"usage dashboard, <date>" / "tier-based only —87usage not supplied">*8889## Health read90- Using well: <skills/workflows they already run>91- Leaving on the table: <tier-unlocked workflows they aren't using>92- Risk note: <e.g. "low credit consumption vs grant — activation risk"; only if93 usage was supplied>9495## The 3 to try this week961. **<Skill / workflow>** — <one line why it fits this account>.972. **<Skill / workflow>** — ...983. **<Skill / workflow>** — ...99100## Ready-to-send email101> Subject: 3 quick wins in Creatorland this week102>103> Hi <name>,104> <2-3 warm sentences.>105>106> 1. **<Win>** — <why>. Try this:107> `<paste-ready prompt, pre-filled with their vertical>`108> 2. ...109> 3. ...110>111> <Soft close + offer to walk through one live.>112113---114**Read basis:** <usage source + date, or the honest "tier-based, usage not115read in v1 — no account-telemetry tool yet (CRE-543 wishlist item 5)">.116**Provenance (if a live number was used):** <the market-intel provenance line,117verbatim, + recency window — and it is a vertical market band, not this118account's data>.119Credits used this run: ~N (0 if thrifty / no live number; 5 if one market call)120```121122## Honesty rules123124- **Don't invent usage.** v1 has no telemetry tool. If usage wasn't supplied,125 the read is explicitly "tier-based, not usage-based" — never a fabricated126 "you've run X searches". Say what you can and can't see.127- **Respect the tier.** Never recommend a workflow the account's tier doesn't128 unlock as if it were available; if it's the best next step, frame it as an129 honest upgrade reason, not a bait.130- **Live numbers are vertical market bands** (convention 2) — a "$X median in131 your vertical" hook is corpus-level context, never the account's own rate or132 a creator's rate.133- **Provenance survives into the email** when a live number is used (convention134 1) — the paste-ready prompt or a footer carries the citation.135- **No contact info** in the deliverable (convention 7); the email is to the136 account, but creator/brand contact data never appears in it.137- **Internal artifact, honest framing.** This is a CS tool; the activation138 suggestions are genuine fit reads, not upsell padding — recommend what139 actually helps the account, in priority order.140141## Credit footprint142143thorough: ~0-5 credits (catalog reasoning is free; one optional market-intel144call is 5, +5 per ladder retry) · thrifty: 0 credits (no live number).