expansion-signal
Skill23 starsChanged 2 months agoMITView on GitHub
Work an expansion-ready account into an angle and a clean hand to sales — the second growth motion the funnel forgets. Trigger when account-health flags an EXPANSION-SIGNAL, when a healthy account asks for more unprompted, a second team wants access, or the user says "this account is ready to grow", "expansion play", "upsell", or "land and expand".
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- account-healthSkill
- calendar-followupSkill
- churn-saveSkill
- cold-outreachSkill
- content-repurposeSkill
- event-to-pipelineSkill
- example-skillSkill
- follow-upSkill
- inbox-digestSkill
- lead-qualifySkill
- marketing-feedbackSkill
- meeting-prepSkill
- onboarding-handoffSkill
- product-signalSkill
- qbr-prepSkill
- retention-feedbackSkill
- status-updateSkill
- support-signalSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Build the case on realized value: Start from what they've already gotten — the outcome the book can show — and extend it to the new area, …
- Very specific: line 19
Don't run this on an unhealthy account — route that to churn-save first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Expansion Signal
The other act-skill on the right side. Two of the three ways a company grows happen after the first sale (docs/operating-model.md), and this is one of them: account-health flags the EXPANSION-SIGNAL; this turns it into an angle and hands it to sales with the customer context attached — so it isn't a cold internal restart.
From the healthy account in ops/customers.md and the EXPANSION-SIGNAL line:
- Confirm the trigger is real. Expansion rides on adoption, not the calendar. The signal is the core used well plus a named next pain — a second team asking unprompted, a new use case, more seats. A renewal date is not an expansion trigger; pushing growth on an account that isn't getting value yet is churn with extra steps.
- Name the angle. Which way does it grow — an adjacent team, a new use case, deeper use of what they already have? Is it cross-sell (a new thing) or more of the same (more seats, more volume)? One angle, named.
- Build the case on realized value. Start from what they've already gotten — the outcome the book can show — and extend it to the new area, in their words, not a feature list.
- Re-arm the champion. Expansion is carried internally, not pitched in. Give the champion the one-page case they can forward, and the line that makes it their idea — not your quota.
- Hand to sales with the CS context. The handoff is the account, the angle, the realized-value case, and the champion — so sales picks up a warm, qualified expansion, not a cold account. A real expansion is a new deal: it crosses back to
ops/pipeline.md, the loop the bowtie closes. - Log it and update the book. Mark the account Expanding; note the angle and the handoff in
ops/customers.md.
Don't run this on an unhealthy account — route that to churn-save first. Expansion is the reward for value landing, not a substitute for it.
Depth
- quick: confirm the trigger + name the one angle.
- standard: the full play — trigger, angle, value-case, champion, hand to sales.
- deep: + the multi-thread map of who signs off on the larger spend, and the buyer-facing one-pager for the champion to forward.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

