ecosystem-powered-pipeline-prioritization

Ranks accounts by Crossbeam partner deal activity and ecosystem signals.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/getcrossbeam/crossbeam-claude-skills --skill ecosystem-powered-pipeline-prioritization-getcrossbeam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-powered-pipeline-prioritization
Source: https://github.com/getcrossbeam/crossbeam-claude-skills/tree/main/skills/ecosystem-powered-pipeline-prioritization
Command: npx skills add https://github.com/getcrossbeam/crossbeam-claude-skills --skill ecosystem-powered-pipeline-prioritization-getcrossbeam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales teams cannot see which accounts have real partner-driven buying motion, so pipeline prioritization relies on intent scores and static data that miss active ecosystem activity. ## Core Features & Use Cases - Ecosystem Signal Scanning: Pulls partner deal opens, closed-won events, and overlap populations from the Crossbeam MCP for every account on a configured list. - Signal-Based Ranking: Scores accounts on in-window partner motion with convergence and recency bonuses, keeping static overlap breadth out of the score. - Outreach Angles: Optionally generates 2-3 sentence talking points per ranked account based on what the partner activity implies. - Use Case: A sales manager runs a weekly scan over their top 300 prospect accounts and receives a ranked list showing which accounts had partner deals opened or closed in the last 30 days, with an outreach angle for each. ## Quick Start Run the ecosystem pipeline scanner on my account list and rank the accounts by partner activity from the last 30 days.

Frequently Asked Questions about ecosystem-powered-pipeline-prioritization

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

FAQPage Schema
How do I prioritize my sales pipeline using partner ecosystem data?

Configure an account source and lookback window, then run the scanner to pull Crossbeam partner deal activity for each account. It scores in-window deal opens and closed-won events, adds convergence and recency bonuses, and returns a ranked list with signal summaries.

What are Crossbeam Ecosystem Signals?

Ecosystem Signals are partner-driven events such as a partner opening or closing a deal on an account you track. They come from actual CRM deal activity shared by partners in Crossbeam, not from modeled or inferred intent data.

What do my partners need to share in Crossbeam for signals to appear?

Partners must have a CRM connected to Crossbeam and share deal open date, deal close date, deal is closed, and deal is won fields with you. To include contact names and titles on signals, partners must also share CRM contact data.

Can I filter signals to only my strategic or co-sell partners?

Yes, configure strategic partner tags in the skill's Configuration section to filter signals to tagged partners. If multiple tags are configured, the scanner queries each tag separately and unions the results before scoring.

Why did an account with many overlapping partners rank low in the scan?

Overlap breadth does not contribute to the score; only in-window partner deal activity earns points. An account with no partner activity inside the lookback window scores exactly zero and sorts below every account with live signals.

When should I use the account brief skill instead of this scanner?

Use the Ecosystem-Informed Account Brief for one-off deep dives into a single account. This scanner is built for batch prioritization across a list of accounts and does not produce per-account deep-dive reports.