Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

expansion-signal-spotter扩展信号观测器

Agent Skill

expansion-signal-spotter 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

194

周安装

8

GitHub Stars

630

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:expansion-signal-spotter(扩展信号观测器)
来源仓库:https://github.com/gooseworks-ai/goose-skills
仓库路径:skills/expansion-signal-spotter
安装命令:
npx skills add https://github.com/gooseworks-ai/goose-skills --skill expansion-signal-spotter
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/gooseworks-ai/goose-skills --skill expansion-signal-spotter

简介

expansion-signal-spotter 监控客户账户行为信号,预测其购买更多产品的时机。

  • 适用于早期公司 CS 团队抢占增购窗口期。
  • 可扫描指定时间段内的活动日志与事件流。
  • 需配置信号阈值与误报过滤规则以提高准确性。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

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.

When to Use

  • "Which customers are ready to expand?"
  • "Find upsell opportunities in our accounts"
  • "Run the weekly expansion signal scan"
  • "Who should I pitch [new feature/tier] to?"
  • "Monitor customer accounts for growth signals"

Phase 0: Intake

Account Data

  1. Customer list — CSV or sheet with: company name, domain, primary contact LinkedIn URL, current plan/tier, MRR/ARR, seats/usage
  2. Product tiers — What plans exist? What triggers an upgrade? (e.g., "Pro → Enterprise at 50+ seats")
  3. Cross-sell products — Any add-ons or adjacent products you can sell?

Signal Configuration

  1. Expansion triggers — What signals mean "ready to buy more" for your product?

- Team growth (new hires in relevant roles) - Funding announcement - Usage hitting plan limits - New department/use case interest - Champion promoted (more budget authority)

  1. Key contacts to monitor — LinkedIn URLs of champions, decision-makers per account (if available beyond primary)

Filters

  1. Minimum account value — Only scan accounts above $X MRR? (Focus effort)
  2. Accounts to exclude — Any accounts in active churn risk, paused, or in dispute

Phase 1: Signal Detection

1A: Team Growth Signals

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:

SignalWhat It MeansExpansion Play
Hiring in your product's domainGrowing the team that uses youMore seats / higher tier
New leadership hireBudget holder arrived, will evaluate stackExecutive alignment meeting
Hiring in adjacent teamNew department could use your productCross-sell / new use case
Rapid headcount growthScaling fast, needs to scale tools tooVolume upgrade

1B: Funding & Financial Signals

Search: "[company name]" funding OR raised OR "series" OR investment 2026
Search: "[company name]" revenue OR growth OR expansion
SignalWhat It MeansExpansion Play
New funding roundCash in bank, expanding everythingPremium tier / annual contract
Revenue milestoneBusiness doing well, likely investing in toolsROI-focused expansion pitch
AcquisitionNew parent company = new budgetEnterprise plan / multi-team

1C: Product Usage Signals (if usage data available)

From internal data, flag:

SignalThresholdExpansion Play
Approaching plan limit>80% of seats/usage quotaProactive upgrade offer
New feature adoptionStarted using a feature in higher tier (via trial/beta)Convert trial to paid
Power user emergence1+ users with 3x average usageChampion for internal expansion
Multi-team usageUsers from 2+ departmentsDepartment-level deal
API usage growthAPI calls trending up month-over-monthUsage-based tier upgrade

1D: Public Signal Monitoring

Search: "[company name]" launch OR "new product" OR partnership OR expansion
Search: "[company name]" "[your product category]" OR "[related use case]"
SignalWhat It MeansExpansion Play
New product launchMay need your product for the new lineNew use case pitch
Geographic expansionGrowing into new marketsMulti-region / additional seats
Partnership announcedBusiness growing, more complexityHigher tier for scale
Competitor of yours mentionedEvaluating alternativesRetention + upgrade pre-empt

1E: Champion & Stakeholder Signals

If monitoring champion LinkedIn profiles:

Search: "[champion name]" promoted OR "new role" OR "excited to announce"
SignalWhat It MeansExpansion Play
Champion promotedMore authority, bigger budgetPropose expansion aligned to new scope
Champion leftRisk + opportunity (new person = fresh pitch)Onboard new contact, re-pitch value
New exec joinedPotential new sponsorExecutive briefing

Phase 2: Opportunity Scoring

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

Opportunity Tiers

TierScoreAction
Hot15+Schedule expansion call this week
Warm8-14Send value-add touchpoint, plant expansion seed
Watch3-7Add to next QBR agenda, monitor

Phase 3: Talk Track Generation

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.]

Phase 4: Output Format

# 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).

Scheduling

Run weekly:

0 8 * * 2 python3 run_skill.py expansion-signal-spotter

Cost

ComponentCost
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 tracksFree (LLM reasoning)
TotalFree — $1.50

Tools Required

  • web_search — for funding, news, hiring signals
  • fetch_webpage — for career pages and announcements
  • Optional: linkedin-profile-post-scraper for champion monitoring
  • Optional: job-posting-intent for structured hiring signal detection

Trigger Phrases

  • "Find expansion opportunities in our accounts"
  • "Which customers are ready for an upgrade?"
  • "Run the expansion signal scan"
  • "Weekly expansion opportunity report"

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.02%
按下载量换算21

Claude

27.81%
按下载量换算18

Cursor

18.88%
按下载量换算12

Gemini CLI

9.91%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills