> on LinkedIn, new job postings, product usage patterns, funding announcements, and public company news. Produces a weekly expansion opportunity list with context and talk tracks. Chains web search, LinkedIn profile monitoring, and job posting detection.
npx skills add https://github.com/gooseworks-ai/goose-skills --skill expansion-signal-spotter
Find expansion revenue hiding in your existing customer base. Monitors accounts for signals that indicate they're ready to buy more — before they ask or before a competitor gets there first.
Built for: CS teams and founders at early-stage companies where expansion revenue is the fastest path to growth. You already have the relationship — this skill finds the timing.
For each customer, search for hiring activity:
Search: "[company name]" hiring OR "we're hiring" OR "join our team"
Search: site:linkedin.com/jobs "[company name]" [relevant role keywords]
Search: "[company name]" "head of" OR "director of" OR "VP" [your product's domain]
Signals to detect:
| Signal | What It Means | Expansion Play |
|--------|---------------|----------------|
| Hiring in your product's domain | Growing the team that uses you | More seats / higher tier |
| New leadership hire | Budget holder arrived, will evaluate stack | Executive alignment meeting |
| Hiring in adjacent team | New department could use your product | Cross-sell / new use case |
| Rapid headcount growth | Scaling fast, needs to scale tools too | Volume upgrade |
Search: "[company name]" funding OR raised OR "series" OR investment 2026
Search: "[company name]" revenue OR growth OR expansion
| Signal | What It Means | Expansion Play |
|--------|---------------|----------------|
| New funding round | Cash in bank, expanding everything | Premium tier / annual contract |
| Revenue milestone | Business doing well, likely investing in tools | ROI-focused expansion pitch |
| Acquisition | New parent company = new budget | Enterprise plan / multi-team |
From internal data, flag:
| Signal | Threshold | Expansion Play |
|--------|-----------|----------------|
| Approaching plan limit | >80% of seats/usage quota | Proactive upgrade offer |
| New feature adoption | Started using a feature in higher tier (via trial/beta) | Convert trial to paid |
| Power user emergence | 1+ users with 3x average usage | Champion for internal expansion |
| Multi-team usage | Users from 2+ departments | Department-level deal |
| API usage growth | API calls trending up month-over-month | Usage-based tier upgrade |
Search: "[company name]" launch OR "new product" OR partnership OR expansion
Search: "[company name]" "[your product category]" OR "[related use case]"
| Signal | What It Means | Expansion Play |
|--------|---------------|----------------|
| New product launch | May need your product for the new line | New use case pitch |
| Geographic expansion | Growing into new markets | Multi-region / additional seats |
| Partnership announced | Business growing, more complexity | Higher tier for scale |
| Competitor of yours mentioned | Evaluating alternatives | Retention + upgrade pre-empt |
If monitoring champion LinkedIn profiles:
Search: "[champion name]" promoted OR "new role" OR "excited to announce"
| Signal | What It Means | Expansion Play |
|--------|---------------|----------------|
| Champion promoted | More authority, bigger budget | Propose expansion aligned to new scope |
| Champion left | Risk + opportunity (new person = fresh pitch) | Onboard new contact, re-pitch value |
| New exec joined | Potential new sponsor | Executive briefing |
Score each expansion opportunity:
Expansion Score = Signal Strength × Account Value × Timing
Signal Strength (1-5):
5 = Approaching plan limit + funding + team growth (multiple signals)
4 = Strong usage signal + one external signal
3 = One strong external signal (funding, hiring)
2 = Usage trending up, no external confirmation
1 = Weak or single minor signal
Account Value (multiplier):
2.0x = Top 20% accounts by MRR
1.5x = Mid-tier accounts
1.0x = Smaller accounts
Timing (multiplier):
2.0x = Signal detected this week (fresh)
1.5x = Signal detected this month
1.0x = Signal older than 30 days
| Tier | Score | Action |
|------|-------|--------|
| Hot | 15+ | Schedule expansion call this week |
| Warm | 8-14 | Send value-add touchpoint, plant expansion seed |
| Watch | 3-7 | Add to next QBR agenda, monitor |
For each Hot and Warm opportunity, generate:
ACCOUNT: [Company Name]
CURRENT PLAN: [Plan] — $[MRR]/mo
EXPANSION TYPE: [Upsell / Cross-sell / Volume increase]
ESTIMATED EXPANSION: $[additional MRR]/mo
SIGNALS:
- [Signal 1] — [Source + date]
- [Signal 2] — [Source + date]
EXPANSION OPPORTUNITY:
[2-3 sentences: What should they buy and why now?]
TALK TRACK:
"[Opening line — connects the signal to their business goals, not your quota]"
"[Value bridge — how the expansion directly helps with what they're already trying to do]"
"[Soft ask — suggest next step without pressure]"
TIMING: [Why now is the right time — tied to signal]
RISK: [What could block this — budget freeze, champion change, etc.]
# Expansion Signal Report — Week of [DATE]
Accounts scanned: [N]
Total expansion pipeline identified: $[X] additional MRR
---
## Summary
| Tier | Opportunities | Potential MRR |
|------|--------------|---------------|
| 🔥 Hot | [N] | $[X]/mo |
| 🟡 Warm | [N] | $[X]/mo |
| 👀 Watch | [N] | $[X]/mo |
---
## 🔥 Hot Opportunities
### [Company 1] — Current: $[X]/mo → Target: $[Y]/mo (+$[Z])
**Signals:** [list]
**Expansion type:** [Upsell to Enterprise / Add 20 seats / Cross-sell analytics]
**Talk track:** "[scripted opener]"
**Next step:** [Specific action + date]
### [Company 2] — ...
---
## 🟡 Warm Opportunities
### [Company] — Current: $[X]/mo | Signal: [brief]
**Recommended touchpoint:** [What to do — e.g., "Send case study of similar customer who expanded"]
---
## 👀 Watch List
| Account | Signal | Next Check |
|---------|--------|------------|
| [Name] | [Signal] | [Date] |
---
## Trends
- [N] accounts showing team growth signals (potential seat expansion)
- [N] accounts approaching usage limits
- [N] accounts with new funding (potential tier upgrade)
## Expansion Playbook Priority
This week, focus on:
1. **[Account]** — [Why: highest value + strongest signal]
2. **[Account]** — [Why]
3. **[Account]** — [Why]
Save to the current working directory or wherever the user prefers (e.g., expansion/expansion-signals-[YYYY-MM-DD].md).
Run weekly:
0 8 * * 2 python3 run_skill.py expansion-signal-spotter
| Component | Cost |
|-----------|------|
| Web search (hiring, funding, news) | Free |
| LinkedIn monitoring (if using linkedin-profile-post-scraper) | ~$0.50-1.00 |
| Job posting detection (if using job-posting-intent) | ~$0.50 |
| All analysis and talk tracks | Free (LLM reasoning) |
| Total | Free — $1.50 |
linkedin-profile-post-scraper for champion monitoringjob-posting-intent for structured hiring signal detectionAssess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
Take gooseworks-ai/expansion-signal-spotter from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.