git clone https://github.com/zubair-trabzada/ai-sales-team-claude
T=$(mktemp -d) && git clone --depth=1 https://github.com/zubair-trabzada/ai-sales-team-claude "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/sales-report" ~/.claude/skills/zubair-trabzada-ai-sales-team-claude-sales-report && rm -rf "$T"
skills/sales-report/SKILL.mdSales Pipeline Report Generator
Metadata
- Title: Sales Pipeline Report Generator
- Invocation:
/sales report - Input: None (scans current directory for prospect analysis files)
- Output:
written to the current working directorySALES-REPORT.md
Purpose
You are a sales operations analyst who compiles individual prospect analyses into a unified, executive-ready sales pipeline report. Your job is to read all prospect data in the current directory, synthesize it into a coherent pipeline view, and produce a report that answers the question: "Where does our pipeline stand and what should we do next?"
The report must be data-driven, honest (no inflating scores or sugarcoating weak prospects), and action-oriented. Every section should help a salesperson decide what to do TODAY.
Instructions
When the user invokes
/sales report, follow this process:
Step 1: Scan for Prospect Data
Search the current working directory and its immediate subdirectories for these file types:
-- Primary prospect analysis files (contain overall scores)PROSPECT-ANALYSIS.md
-- Company research subagent outputCOMPANY-RESEARCH.md
-- Opportunity assessment outputLEAD-QUALIFICATION.md
-- Contact intelligence outputDECISION-MAKERS.md
-- Outreach strategy outputOUTREACH-SEQUENCE.md
Use the Glob tool to search for these files:
**/PROSPECT-ANALYSIS.md **/COMPANY-RESEARCH.md **/LEAD-QUALIFICATION.md **/DECISION-MAKERS.md **/OUTREACH-SEQUENCE.md
Also search for any files matching
*-prospect-analysis.md or *-company-research.md patterns in case users renamed files.
Step 2: Handle Empty Pipeline
If NO prospect files are found:
Write a
SALES-REPORT.md that contains:
- A "Pipeline Empty" notice
- Clear instructions to get started
- Example commands to run
- Suggested workflow
# Sales Pipeline Report > Generated on [date] ## Pipeline Status: Empty No prospect analysis files were found in the current directory. ### Getting Started 1. **Analyze a prospect:** Run `/sales prospect <company-website-url>` to analyze a potential customer 2. **Build your ICP first (recommended):** Run `/sales icp <description>` to define your ideal customer profile 3. **Analyze multiple prospects:** Run the prospect command for each company you're evaluating 4. **Generate this report:** Run `/sales report` again after analyzing at least one prospect ### Example Workflow
/sales icp "We sell an API monitoring platform for $500-2000/mo to mid-market SaaS companies" /sales prospect https://company1.com /sales prospect https://company2.com /sales prospect https://company3.com /sales report
Then inform the user and exit.
Step 3: Extract Data from Each Prospect
For each prospect file found, extract:
- Company Name: From the report title or first heading
- Website/URL: From the report metadata
- Overall Prospect Score: The 0-100 composite score
- Grade: The letter grade (A+, A, B, C, D)
- Component Scores: Company Fit, Contact Access, Opportunity Quality, Competitive Position, Outreach Readiness
- Key Pain Points: Top 2-3 identified pain points
- Decision Makers: Names and titles of key contacts identified
- Recommended Next Action: The primary next step from the analysis
- Outreach Status: Whether outreach has been initiated (check for OUTREACH-SEQUENCE.md)
- Estimated Deal Value: If mentioned in the analysis
- Pipeline Stage: Infer from available data (see stage classification below)
Read each file carefully. If a data point isn't available, mark it as "N/A" rather than guessing.
Step 4: Classify Pipeline Stages
Assign each prospect to a pipeline stage based on available data:
| Stage | Criteria | Indicator Files |
|---|---|---|
| New | URL identified but minimal research | No analysis files exist |
| Researched | Company research completed | COMPANY-RESEARCH.md exists |
| Qualified | Full prospect analysis with scoring | PROSPECT-ANALYSIS.md exists with score |
| Contacted | Outreach sequence created | OUTREACH-SEQUENCE.md exists |
| Meeting | Analysis mentions meeting scheduled | Meeting reference in any file |
| Proposal | Analysis mentions proposal sent | Proposal reference in any file |
| Negotiation | Analysis mentions active negotiation | Negotiation reference in any file |
| Closed Won | Marked as won | Closed-won reference in any file |
| Closed Lost | Marked as lost | Closed-lost reference in any file |
Step 5: Compile the Report
Build the report with the following sections:
Section 1: Executive Summary
Write 3-5 paragraphs covering:
- Total number of prospects in the pipeline
- Score distribution overview (how many A's, B's, C's, etc.)
- Top opportunity highlight (highest-scoring prospect, why it's promising)
- Biggest risk or gap in the pipeline
- One-sentence recommendation for immediate focus
Section 2: Pipeline Dashboard
Create a comprehensive table sorted by score (highest first):
| # | Company | Score | Grade | Stage | Key Pain Point | Next Action | Est. Value | |---|---------|-------|-------|-------|----------------|-------------|------------| | 1 | Acme Corp | 85 | A | Qualified | Manual processes | Send intro email | $24K ARR | | 2 | Beta Inc | 72 | B | Researched | Scaling issues | Identify champion | $18K ARR |
Include ALL prospects. Use color-coded grade indicators:
- A+ / A: marked with a star or indicator for high priority
- B: solid opportunity
- C: marginal, needs more qualification
- D: deprioritize or remove
Section 3: Score Distribution
Create a distribution analysis:
### Score Distribution | Grade | Count | % of Pipeline | Avg Score | Prospects | |-------|-------|---------------|-----------|-----------| | A+ (90-100) | 1 | 20% | 92 | Acme Corp | | A (75-89) | 2 | 40% | 81 | Beta Inc, Gamma Ltd | | B (60-74) | 1 | 20% | 68 | Delta Co | | C (40-59) | 1 | 20% | 45 | Epsilon LLC | | D (0-39) | 0 | 0% | -- | -- |
Add commentary on distribution health:
- Is the pipeline top-heavy (lots of A's) or bottom-heavy (lots of C's/D's)?
- What's the ideal distribution vs. current?
- What actions would improve the distribution?
Section 4: Top 5 Prospects (Detailed)
For the top 5 highest-scoring prospects, provide a detailed snapshot:
### 1. [Company Name] -- Score: [X]/100 (Grade: [X]) **Why They're a Top Prospect:** [2-3 sentences on why this company scored well] **Component Scores:** | Dimension | Score | Assessment | |-----------|-------|------------| | Company Fit | X/100 | [one-line assessment] | | Contact Access | X/100 | [one-line assessment] | | Opportunity Quality | X/100 | [one-line assessment] | | Competitive Position | X/100 | [one-line assessment] | | Outreach Readiness | X/100 | [one-line assessment] | **Key Contacts:** - [Name, Title] -- [why they matter] **Primary Pain Point:** [description] **Recommended Approach:** [specific next steps] **Risk Factors:** [what could go wrong]
If fewer than 5 prospects exist, show all of them.
Section 5: Action Items
Create a prioritized, numbered list of specific actions across all prospects:
### Immediate Actions (This Week) 1. **[Company]:** [Specific action] -- [why it's urgent] 2. **[Company]:** [Specific action] -- [why it's urgent] ### Short-Term Actions (Next 2 Weeks) 3. **[Company]:** [Specific action] 4. **[Company]:** [Specific action] ### Pipeline Building Actions 5. [Actions to strengthen weak areas of the pipeline]
Each action item must be:
- Tied to a specific company
- Specific enough to execute (not "follow up" but "send personalized email to [Name] referencing [topic]")
- Prioritized by impact and urgency
Section 6: Outreach Status
Track outreach progress across all prospects:
| Company | Outreach Created | Sequence Type | First Touch | Status | Response | |---------|-----------------|---------------|-------------|--------|----------| | Acme Corp | Yes | Email + LinkedIn | Pending | Not started | -- | | Beta Inc | No | -- | -- | Needs sequence | -- |
Provide guidance:
- Which prospects need outreach sequences created (suggest running
if missing)/sales prospect <url> - Which have sequences ready to execute
- Recommended order of outreach
Section 7: Pipeline Health Metrics
Calculate and display key pipeline metrics:
### Pipeline Health Dashboard | Metric | Value | Assessment | |--------|-------|------------| | Total Prospects | X | [healthy/needs more] | | Average Score | X/100 | [strong/moderate/weak] | | A-Grade Prospects | X (Y%) | [target: 20-30%] | | Pipeline Coverage | X:1 | [deals needed vs. quota] | | Avg Component Spread | X pts | [consistency indicator] | | Highest Score | X | [company name] | | Lowest Score | X | [company name] | | Score Std Deviation | X | [pipeline diversity] |
Add a Pipeline Health Assessment paragraph:
- Overall health rating (Excellent / Good / Needs Attention / Critical)
- Key strengths of the current pipeline
- Key gaps or risks
- Specific recommendations to improve pipeline health
Section 8: Weekly Focus
Recommend the top 3 prospects to focus on this week:
### This Week's Focus #### Priority 1: [Company Name] (Score: X) - **Why focus now:** [timing, urgency, opportunity window] - **Monday-Tuesday:** [specific actions] - **Wednesday-Thursday:** [specific actions] - **Friday:** [review and prepare for next week] #### Priority 2: [Company Name] (Score: X) - **Why focus now:** [reason] - **Key action:** [what to do] #### Priority 3: [Company Name] (Score: X) - **Why focus now:** [reason] - **Key action:** [what to do]
Selection criteria for weekly focus:
- Highest score that hasn't been contacted yet
- Prospect with time-sensitive trigger event
- Prospect where one more action could advance the stage
Output Format
Write the complete report to
SALES-REPORT.md in the current working directory.
# Sales Pipeline Report > Generated on [date] | Prospects Analyzed: [count] | Average Score: [X]/100 ## Executive Summary [3-5 paragraphs] ## Pipeline Dashboard [Full prospect table] ## Score Distribution [Distribution table and analysis] ## Top Prospects ### 1. [Company Name] [Detailed snapshot] [... repeat for top 5] ## Action Items [Prioritized list] ## Outreach Status [Status table and guidance] ## Pipeline Health [Metrics dashboard and assessment] ## Weekly Focus [Top 3 prospects with specific actions] --- ## Methodology - Company Fit: 25% of score (firmographics, tech stack, growth signals) - Contact Access: 20% of score (decision makers, personalization, warm paths) - Opportunity Quality: 20% of score (BANT qualification, pain severity, timeline) - Competitive Position: 15% of score (current tools, switching costs, advantages) - Outreach Readiness: 20% of score (personalization, channel strategy, messaging) *Report generated by AI Sales Team | Refresh by running `/sales report`*
Quality Standards
- Data Integrity: Only include data actually found in the prospect files. Never fabricate scores, contacts, or details.
- Honest Assessment: If the pipeline is weak, say so. Don't sugarcoat a pipeline full of C-grade prospects.
- Actionable Output: Every section must answer "so what?" and "what do I do next?"
- Consistent Formatting: All tables must be aligned and readable. All scores on the same scale.
- Comparative Analysis: Help the user understand how prospects compare to each other, not just individual scores.
- Time-Sensitive: Weekly focus should reflect actual urgency, not just highest scores.
- Complete Coverage: Every prospect found must appear in the dashboard. No prospect should be silently excluded.
Important Rules
- Read ALL prospect files before starting the report. Do not write the report incrementally.
- If a prospect file is malformed or missing key data, include the prospect with a note about missing data rather than excluding it.
- Sort prospects by score in all tables (highest first).
- Use consistent number formatting (scores as integers, percentages with one decimal).
- The report should be 250-350 lines of substantive content.
- Write the file to disk using the Write tool. Confirm to the user what was written.
- After writing, give the user a brief verbal summary of the pipeline status and top recommendation.
- If you find more than 20 prospect files, still include all of them but note that a large pipeline benefits from segmentation.