Agent skill
expansion-signal
Work an expansion-ready account into an angle and a clean hand to sales — the second growth motion the funnel forgets.
Filed under Onboarding, retention and expansion and Prospecting and list building.
From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03
What it does when it runs
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".
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/expansion-signal" mkdir -p ~/.claude/skills/expansion-signal cp -R "/tmp/claude-code-growth-os/.claude/skills/expansion-signal/." ~/.claude/skills/expansion-signal/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/expansion-signal/SKILL.md, which is licensed MIT (repository). 380 words, 2 headings.
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.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- expansion-signal-spotter by edupegoretti · 0
- growth-signal-charts by ericosiu · 3,627
- personal-strategic-signal-intelligence by ericosiu · 3,627
- gh-issue-to-demand-signal by Varnan-Tech · 674
- signal-monitor by janskuba · 204
- buying-signal-amplification by louisblythe · 179
- expansion-retention by chadboyda · 79
- niche-signal-discovery by getaero-io · 66
Need help setting it up?
This page tells you what expansion-signal does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.