Fetches pipeline-review from anthropics/knowledge-work-plugins and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/pipeline-review
Restart Cursor to activate pipeline-review. Access via /pipeline-review in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Analyze your pipeline health, prioritize deals, and get actionable recommendations for where to focus.
Usage
/pipeline-review [segment or rep]
Review pipeline for: $ARGUMENTS
If a file is referenced: @$1
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PIPELINE REVIEW │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Upload CSV export from your CRM │
│ ✓ Or paste/describe your deals │
│ ✓ Health check: flag stale, stuck, and at-risk deals │
│ ✓ Prioritization: rank deals by impact and closability │
│ ✓ Hygiene audit: missing data, bad close dates, single-thread │
│ ✓ 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: See upcoming meetings per deal │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
Option A: Upload a CSV
Export your pipeline from your CRM (e.g. Salesforce, HubSpot). Helpful fields:
Deal/Opportunity name
Account name
Amount
Stage
Close date
Created date
Last activity date
Owner (if reviewing a team)
Primary contact
Option B: Paste your deals
Acme Corp - $50K - Negotiation - closes Jan 31 - last activity Jan 20
TechStart - $25K - Demo scheduled - closes Feb 15 - no activity in 3 weeks
BigCo - $100K - Discovery - closes Mar 30 - created last week
Option C: Describe your pipeline
"I have 12 deals. Two big ones in negotiation that I'm confident about. Three stuck in discovery for over a month. The rest are mid-stage but I haven't talked to some of them in a while."
Output
# Pipeline Review: [Date]**Data Source:** [CSV upload / Manual input / CRM]
**Deals Analyzed:** [X]
**Total Pipeline Value:** $[X]
---## Pipeline Health Score: [X/100]| Dimension | Score | Issue ||-----------|-------|-------||**Stage Progression**| [X]/25 | [X] deals stuck in same stage 30+ days ||**Activity Recency**| [X]/25 | [X] deals with no activity in 14+ days ||**Close Date Accuracy**| [X]/25 | [X] deals with close date in past ||**Contact Coverage**| [X]/25 | [X] deals single-threaded |---## Priority Actions This Week### 1. [Highest Priority Deal]**Why:** [Reason — large, closing soon, at risk, etc.]
**Action:** [Specific next step]
**Impact:** $[X] if you close it
### 2. [Second Priority]**Why:** [Reason]
**Action:** [Next step]
### 3. [Third Priority]**Why:** [Reason]
**Action:** [Next step]
---## Deal Prioritization Matrix### Close This Week (Focus Time Here)| Deal | Amount | Stage | Close Date | Next Action ||------|--------|-------|------------|-------------|| [Deal] | $[X] | [Stage] | [Date] | [Action] |### Close This Month (Keep Warm)| Deal | Amount | Stage | Close Date | Status ||------|--------|-------|------------|--------|| [Deal] | $[X] | [Stage] | [Date] | [Status] |### Nurture (Check-in Periodically)| Deal | Amount | Stage | Close Date | Status ||------|--------|-------|------------|--------|| [Deal] | $[X] | [Stage] | [Date] | [Status] |---## Risk Flags### Stale Deals (No Activity 14+ Days)| Deal | Amount | Last Activity | Days Silent | Recommendation ||------|--------|---------------|-------------|----------------|| [Deal] | $[X] | [Date] | [X] | [Re-engage / Downgrade / Remove] |### Stuck Deals (Same Stage 30+ Days)| Deal | Amount | Stage | Days in Stage | Recommendation ||------|--------|-------|---------------|----------------|| [Deal] | $[X] | [Stage] | [X] | [Push / Multi-thread / Qualify out] |### Past Close Date| Deal | Amount | Close Date | Days Overdue | Recommendation ||------|--------|------------|--------------|----------------|| [Deal] | $[X] | [Date] | [X] | [Update date / Push to next quarter / Close lost] |
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
