Skip to content
Sales
Skill

/sales-report

- **Title:** Sales Pipeline Report Generator - **Invocation:** `/sales report` - **Input:** None (scans current directory for prospect analysis files) - **Output:** `SALES-REPORT.md` written to the current working directory

BOOST
From plugin
ai-sales-team-claude
1.4k13 skills5 agents
Install
$ npx -y skills add zubair-trabzada/ai-sales-team-claude --skill sales-report --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sales-report

Context preview

The summary Claude sees to decide when to auto-load this skill.

- **Title:** Sales Pipeline Report Generator - **Invocation:** `/sales report` - **Input:** None (scans current directory for prospect analysis files) - **Output:** `SALES-REPORT.md` written to the current working directory

SKILL.md

sales-report.SKILL.md

Sales Pipeline Report Generator

Metadata

  • **Title:** Sales Pipeline Report Generator
  • **Invocation:** `/sales report`
  • **Input:** None (scans current directory for prospect analysis files)
  • **Output:** `SALES-REPORT.md` written to the current working directory

---

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:

  • `PROSPECT-ANALYSIS.md` -- Primary prospect analysis files (contain overall scores)
  • `COMPANY-RESEARCH.md` -- Company research subagent output
  • `LEAD-QUALIFICATION.md` -- Opportunity assessment output
  • `DECISION-MAKERS.md` -- Contact intelligence output
  • `OUTREACH-SEQUENCE.md` -- Outreach strategy output

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 | Del
Read more
Ships withai-sales-team-claude

AI-powered sales team for Claude Code. Research prospects, qualify leads (BANT + MEDDIC), find decision makers, generate outreach sequences, prepare for meetings, write proposals, and produce PDF pipeline reports — 14 skills, 5 parallel agents.

Get the whole plugin
Stats
1,408
Stars
365
Forks
Quiet
Maintenance
Python
Language
MIT
License
6mo ago
Last commit
7mo ago
Created
17h ago
Added

Repo: zubair-trabzada/ai-sales-team-claude

Other skills on ai-sales-team-claude.