expansion-signal-detection

Fuse call transcripts, usage anomalies, and tickets into ranked expansion signal digests.

Updated May 2, 2026
One-click install
npx skills add https://github.com/marius-bughiu/ooligo --skill expansion-signal-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expansion-signal-detection
Source: https://github.com/marius-bughiu/ooligo/tree/main/apps/web/public/artifacts/expansion-signal-detection-claude
Command: npx skills add https://github.com/marius-bughiu/ooligo --skill expansion-signal-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CSMs waste hours manually sifting through call transcripts, usage data, and support tickets to identify which existing customers are likely to expand their contracts, often prioritizing low-intent accounts over high-probability opportunities. This Skill automates the scanning and classification of expansion intent signals to eliminate that manual work and ensure CSMs focus on the most actionable accounts.

Core Features & Use Cases

  • Multi-source signal fusion: Combines CSM call mentions, pre-computed usage anomalies, and support ticket topics to identify expansion intent, rather than relying on a single data source.
  • Weak/strong signal classification: Separates high-certainty strong signals (corroborated by both call and usage data) from low-certainty weak signals to avoid flooding CSMs with noise.
  • Per-CSM ranked digests: Groups and sorts signals by CSM owner, ranking by ARR and renewal date to prioritize the most time-sensitive, high-value opportunities, with each signal mapped to a specific upsell SKU and concrete next-best action.
  • Use case: A CSM team running this weekly scan gets a 5-minute pre-meeting digest of exactly which accounts to target for expansion, with clear, actionable next steps for each high-priority signal.

Quick Start

Use the expansion-signal-detection skill with your weekly account portfolio, CSM call records, usage anomaly events, and support tickets to generate a per-CSM ranked expansion signal digest.

Frequently Asked Questions about expansion-signal-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize customer upsells using CSM call transcripts and usage anomalies?

To prioritize customer upsells, fuse CSM call transcripts, pre-computed usage anomalies, and support ticket data to classify expansion intent. This generates per-CSM ranked digests separating high-certainty strong signals from weak signals to guide actionable next-best actions.

How do I automate weekly scanning of customer accounts for expansion signals?

Automate weekly expansion signal scanning by processing account portfolios, CSM call records, usage anomaly events, and support tickets. The workflow outputs per-CSM ranked digests separating strong and weak expansion signals mapped to specific upsell SKUs.

What's the best way to group expansion signals by CSM owner and rank by ARR?

Group expansion signals by CSM owner and rank by ARR and renewal date by fusing multi-source account data. This prioritizes time-sensitive, high-value opportunities, mapping each signal to a specific upsell SKU and next-best action.

Can I use this expansion signal detection workflow for new logo sales analysis?

No, expansion signal detection applies strictly to existing customers with baseline usage and named CSM owners. It excludes new logo sales analysis, real-time event alerting, and outbound customer actions.

Why do I need pre-computed usage anomalies for customer success expansion tracking?

Pre-computed usage anomalies are required to corroborate CSM call mentions and support ticket topics. Fusing these sources identifies high-certainty strong expansion signals and avoids flooding CSMs with low-certainty weak signal noise.