If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
Review Pipeline
Assess pipeline health, prioritize deals by impact and closability, flag stale/stuck/single-threaded deals, and output a weekly action plan. This skill works with pipeline data you provide; when CRM is connected, it can pull pipeline automatically and update records.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ REVIEW PIPELINE │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ Upload CSV from ~~CRM~~ or paste/describe deals │
│ ✓ Health score: stage progression, activity, close dates, coverage │
│ ✓ Prioritization: rank by close date, size, stage, activity, risk │
│ ✓ Risk flags: stale, stuck, past close date, single-threaded │
│ ✓ Hygiene audit: missing close date, amount, next step, contact │
│ ✓ Weekly action plan: what to focus on │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM~~: Pull pipeline automatically, update records │
│ + Activity data for engagement scoring │
│ + Historical patterns for risk prediction │
│ + ~~calendar~~: Upcoming meetings per deal │
└─────────────────────────────────────────────────────────────────┘
Prioritization Framework
| Factor |
Weight |
What to look for |
| Close date |
30% |
Soonest close gets priority |
| Deal size |
25% |
Larger deals = more focus |
| Stage |
20% |
Later stage = more focus |
| Activity |
15% |
Recent activity = healthier |
| Risk |
10% |
Lower risk = safer bet |
User can ask for different weighting (e.g. "focus on big deals over soon deals").
Output Structure
- Pipeline health score: Dimensions (stage progression, activity recency, close date accuracy, contact coverage) with issue counts.
- Priority actions this week: Ranked deals with why, action, impact.
- Deal prioritization matrix: Close this week / this month / nurture.
- Risk flags: Stale (no activity 14+ days), stuck (same stage 30+ days), past close date, single-threaded.
- Hygiene issues: Missing close date, amount, next step, primary contact.
- Pipeline shape: By stage, by close month, by deal size.
- Recommendations: This week / this month; deals to consider removing.
Data Sources (per REFERENCE.md)
CRM (if connected): Pipeline, activities, contacts. Enables auto-pull and record updates.
calendar (if connected): Upcoming meetings per deal.
- If tools are not connected, use only CSV or user-provided pipeline.
1---2name: review-pipeline3description: Analyze pipeline health — prioritize deals, flag risks, hygiene issues, and produce a weekly action plan. Works standalone with CSV or pasted deals; supercharged when you connect ~~CRM~~ or ~~calendar~~. Trigger with "review my pipeline", "pipeline health check", or use the /review-pipeline command.4---56> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).78# Review Pipeline910Assess pipeline health, prioritize deals by impact and closability, flag stale/stuck/single-threaded deals, and output a weekly action plan. This skill works with pipeline data you provide; when ~~CRM~~ is connected, it can pull pipeline automatically and update records.1112## How It Works1314```15┌─────────────────────────────────────────────────────────────────┐16│ REVIEW PIPELINE │17├─────────────────────────────────────────────────────────────────┤18│ ALWAYS (works standalone) │19│ ✓ Upload CSV from ~~CRM~~ or paste/describe deals │20│ ✓ Health score: stage progression, activity, close dates, coverage │21│ ✓ Prioritization: rank by close date, size, stage, activity, risk │22│ ✓ Risk flags: stale, stuck, past close date, single-threaded │23│ ✓ Hygiene audit: missing close date, amount, next step, contact │24│ ✓ Weekly action plan: what to focus on │25├─────────────────────────────────────────────────────────────────┤26│ SUPERCHARGED (when you connect your tools) │27│ + ~~CRM~~: Pull pipeline automatically, update records │28│ + Activity data for engagement scoring │29│ + Historical patterns for risk prediction │30│ + ~~calendar~~: Upcoming meetings per deal │31└─────────────────────────────────────────────────────────────────┘32```3334---3536## Prioritization Framework3738| Factor | Weight | What to look for |39|--------|--------|------------------|40| Close date | 30% | Soonest close gets priority |41| Deal size | 25% | Larger deals = more focus |42| Stage | 20% | Later stage = more focus |43| Activity | 15% | Recent activity = healthier |44| Risk | 10% | Lower risk = safer bet |4546User can ask for different weighting (e.g. "focus on big deals over soon deals").4748---4950## Output Structure5152- **Pipeline health score:** Dimensions (stage progression, activity recency, close date accuracy, contact coverage) with issue counts.53- **Priority actions this week:** Ranked deals with why, action, impact.54- **Deal prioritization matrix:** Close this week / this month / nurture.55- **Risk flags:** Stale (no activity 14+ days), stuck (same stage 30+ days), past close date, single-threaded.56- **Hygiene issues:** Missing close date, amount, next step, primary contact.57- **Pipeline shape:** By stage, by close month, by deal size.58- **Recommendations:** This week / this month; deals to consider removing.5960---6162## Data Sources (per REFERENCE.md)6364- **~~CRM~~** (if connected): Pipeline, activities, contacts. Enables auto-pull and record updates.65- **~~calendar~~** (if connected): Upcoming meetings per deal.66- If tools are not connected, use only CSV or user-provided pipeline.