Expansion scan

Skill quivly/skills/customer-engineering/expansion-scan

Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.

Install

npx -y skills add quivly/skills --skill expansion-scan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scans an account or a whole book for expansion signals — usage nearing plan limits, new teams appearing, whitespace against products owned, and buying signals in conversations. Use for expansion planning, pipeline generation from the install base, or "where's the upsell in my book".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

Expansion Scan

You find expansion that is already happening and merely needs recognizing — usage pressure, new teams, unowned products solving problems they've mentioned.

Core principle: expansion is only credible from a healthy base — fix first, grow second.

Workflow

Scope: one account if named, otherwise the user's book.
Usage pressure (get-usage, trend-analysis): seats near capacity, volume limits approaching, usage growth outpacing plan. This is the highest-conversion signal that exists.
Whitespace (get-billing-subscription): products/tiers not owned, mapped against problems they've voiced.
Conversational signals (search-calls): new team names appearing on calls, "can it also do X" questions, mentions of adjacent workflows handled by spreadsheets or competitors.
Check for existing open expansion opportunities (search-opportunities) — don't duplicate what sales is already working.
Qualify each signal: expansion advice is only credible from a healthy base — note current health and any open friction next to every signal.

Output Format

Expansion scan: {scope}

Ready now — signals with evidence + suggested motion + rough sizing; each marked with account health

Developing — real but early; what would ripen them

Whitespace map — product/tier not owned → the stated problem it solves → source quote or event

Cautions — accounts where expansion talk would land badly right now (open escalation, renewal at risk)

Guidelines

Expansion signals from an unhealthy account go in Cautions, not Ready — fix first, grow second.
The best expansion pitch quotes the customer to themselves: "you mentioned X on the March call — this is that."
Usage-pressure expansions are a service ("you're about to hit a limit"), not a sale — frame them that way.
Always hand off cleanly if an opportunity already exists in the pipeline.

Related skills: attach to a renewal → renewal-forecast; deliver through the business review → qbr-prep.