Sales pipeline report generator skill

- Title: Sales Pipeline Report Generator

by zubair-trabzada·MIT license·★ 1,400 Stars on the repo·GitHub ↗

Use now

Files of Sales pipeline report generator

zubair-trabzada/main1 file shown
SKILL.md
Show the full text365 lines

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 | 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 /sales prospect <url> if missing)
  • 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:

  1. Highest score that hasn't been contacted yet
  2. Prospect with time-sensitive trigger event
  3. 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

  1. Data Integrity: Only include data actually found in the prospect files. Never fabricate scores, contacts, or details.
  2. Honest Assessment: If the pipeline is weak, say so. Don't sugarcoat a pipeline full of C-grade prospects.
  3. Actionable Output: Every section must answer "so what?" and "what do I do next?"
  4. Consistent Formatting: All tables must be aligned and readable. All scores on the same scale.
  5. Comparative Analysis: Help the user understand how prospects compare to each other, not just individual scores.
  6. Time-Sensitive: Weekly focus should reflect actual urgency, not just highest scores.
  7. Complete Coverage: Every prospect found must appear in the dashboard. No prospect should be silently excluded.

Important Rules

  1. Read ALL prospect files before starting the report. Do not write the report incrementally.
  2. If a prospect file is malformed or missing key data, include the prospect with a note about missing data rather than excluding it.
  3. Sort prospects by score in all tables (highest first).
  4. Use consistent number formatting (scores as integers, percentages with one decimal).
  5. The report should be 250-350 lines of substantive content.
  6. Write the file to disk using the Write tool. Confirm to the user what was written.
  7. After writing, give the user a brief verbal summary of the pipeline status and top recommendation.
  8. If you find more than 20 prospect files, still include all of them but note that a large pipeline benefits from segmentation.
1# Sales Pipeline Report Generator
2 
3## Metadata
4- **Title:** Sales Pipeline Report Generator
5- **Invocation:** `/sales report`
6- **Input:** None (scans current directory for prospect analysis files)
7- **Output:** `SALES-REPORT.md` written to the current working directory
8 
9---
10 
11## Purpose
12 
13You 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?"
14 
15The 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.
16 
17---
18 
19## Instructions
20 
21When the user invokes `/sales report`, follow this process:
22 
23### Step 1: Scan for Prospect Data
24 
25Search the current working directory and its immediate subdirectories for these file types:
26 
27- `PROSPECT-ANALYSIS.md` -- Primary prospect analysis files (contain overall scores)
28- `COMPANY-RESEARCH.md` -- Company research subagent output
29- `LEAD-QUALIFICATION.md` -- Opportunity assessment output
30- `DECISION-MAKERS.md` -- Contact intelligence output
31- `OUTREACH-SEQUENCE.md` -- Outreach strategy output
32 
33Use the Glob tool to search for these files:
34```
35**/PROSPECT-ANALYSIS.md
36**/COMPANY-RESEARCH.md
37**/LEAD-QUALIFICATION.md
38**/DECISION-MAKERS.md
39**/OUTREACH-SEQUENCE.md
40```
41 
42Also search for any files matching `*-prospect-analysis.md` or `*-company-research.md` patterns in case users renamed files.
43 
44### Step 2: Handle Empty Pipeline
45 
46If NO prospect files are found:
47 
48Write a `SALES-REPORT.md` that contains:
49- A "Pipeline Empty" notice
50- Clear instructions to get started
51- Example commands to run
52- Suggested workflow
53 
54```markdown
55# Sales Pipeline Report
56 
57> Generated on [date]
58 
59## Pipeline Status: Empty
60 
61No prospect analysis files were found in the current directory.
62 
63### Getting Started
64 
651. **Analyze a prospect:** Run `/sales prospect <company-website-url>` to analyze a potential customer
662. **Build your ICP first (recommended):** Run `/sales icp <description>` to define your ideal customer profile
673. **Analyze multiple prospects:** Run the prospect command for each company you're evaluating
684. **Generate this report:** Run `/sales report` again after analyzing at least one prospect
69 
70### Example Workflow
71 
72```
73/sales icp "We sell an API monitoring platform for $500-2000/mo to mid-market SaaS companies"
74/sales prospect https://company1.com
75/sales prospect https://company2.com
76/sales prospect https://company3.com
77/sales report
78```
79```
80 
81Then inform the user and exit.
82 
83### Step 3: Extract Data from Each Prospect
84 
85For each prospect file found, extract:
86 
87- **Company Name:** From the report title or first heading
88- **Website/URL:** From the report metadata
89- **Overall Prospect Score:** The 0-100 composite score
90- **Grade:** The letter grade (A+, A, B, C, D)
91- **Component Scores:** Company Fit, Contact Access, Opportunity Quality, Competitive Position, Outreach Readiness
92- **Key Pain Points:** Top 2-3 identified pain points
93- **Decision Makers:** Names and titles of key contacts identified
94- **Recommended Next Action:** The primary next step from the analysis
95- **Outreach Status:** Whether outreach has been initiated (check for OUTREACH-SEQUENCE.md)
96- **Estimated Deal Value:** If mentioned in the analysis
97- **Pipeline Stage:** Infer from available data (see stage classification below)
98 
99Read each file carefully. If a data point isn't available, mark it as "N/A" rather than guessing.
100 
101### Step 4: Classify Pipeline Stages
102 
103Assign each prospect to a pipeline stage based on available data:
104 
105| Stage | Criteria | Indicator Files |
106|-------|----------|-----------------|
107| **New** | URL identified but minimal research | No analysis files exist |
108| **Researched** | Company research completed | COMPANY-RESEARCH.md exists |
109| **Qualified** | Full prospect analysis with scoring | PROSPECT-ANALYSIS.md exists with score |
110| **Contacted** | Outreach sequence created | OUTREACH-SEQUENCE.md exists |
111| **Meeting** | Analysis mentions meeting scheduled | Meeting reference in any file |
112| **Proposal** | Analysis mentions proposal sent | Proposal reference in any file |
113| **Negotiation** | Analysis mentions active negotiation | Negotiation reference in any file |
114| **Closed Won** | Marked as won | Closed-won reference in any file |
115| **Closed Lost** | Marked as lost | Closed-lost reference in any file |
116 
117### Step 5: Compile the Report
118 
119Build the report with the following sections:
120 
121#### Section 1: Executive Summary
122 
123Write 3-5 paragraphs covering:
124- Total number of prospects in the pipeline
125- Score distribution overview (how many A's, B's, C's, etc.)
126- Top opportunity highlight (highest-scoring prospect, why it's promising)
127- Biggest risk or gap in the pipeline
128- One-sentence recommendation for immediate focus
129 
130#### Section 2: Pipeline Dashboard
131 
132Create a comprehensive table sorted by score (highest first):
133 
134```markdown
135| # | Company | Score | Grade | Stage | Key Pain Point | Next Action | Est. Value |
136|---|---------|-------|-------|-------|----------------|-------------|------------|
137| 1 | Acme Corp | 85 | A | Qualified | Manual processes | Send intro email | $24K ARR |
138| 2 | Beta Inc | 72 | B | Researched | Scaling issues | Identify champion | $18K ARR |
139```
140 
141Include ALL prospects. Use color-coded grade indicators:
142- A+ / A: marked with a star or indicator for high priority
143- B: solid opportunity
144- C: marginal, needs more qualification
145- D: deprioritize or remove
146 
147#### Section 3: Score Distribution
148 
149Create a distribution analysis:
150 
151```markdown
152### Score Distribution
153 
154| Grade | Count | % of Pipeline | Avg Score | Prospects |
155|-------|-------|---------------|-----------|-----------|
156| A+ (90-100) | 1 | 20% | 92 | Acme Corp |
157| A (75-89) | 2 | 40% | 81 | Beta Inc, Gamma Ltd |
158| B (60-74) | 1 | 20% | 68 | Delta Co |
159| C (40-59) | 1 | 20% | 45 | Epsilon LLC |
160| D (0-39) | 0 | 0% | -- | -- |
161```
162 
163Add commentary on distribution health:
164- Is the pipeline top-heavy (lots of A's) or bottom-heavy (lots of C's/D's)?
165- What's the ideal distribution vs. current?
166- What actions would improve the distribution?
167 
168#### Section 4: Top 5 Prospects (Detailed)
169 
170For the top 5 highest-scoring prospects, provide a detailed snapshot:
171 
172```markdown
173### 1. [Company Name] -- Score: [X]/100 (Grade: [X])
174 
175**Why They're a Top Prospect:**
176[2-3 sentences on why this company scored well]
177 
178**Component Scores:**
179| Dimension | Score | Assessment |
180|-----------|-------|------------|
181| Company Fit | X/100 | [one-line assessment] |
182| Contact Access | X/100 | [one-line assessment] |
183| Opportunity Quality | X/100 | [one-line assessment] |
184| Competitive Position | X/100 | [one-line assessment] |
185| Outreach Readiness | X/100 | [one-line assessment] |
186 
187**Key Contacts:**
188- [Name, Title] -- [why they matter]
189 
190**Primary Pain Point:** [description]
191 
192**Recommended Approach:** [specific next steps]
193 
194**Risk Factors:** [what could go wrong]
195```
196 
197If fewer than 5 prospects exist, show all of them.
198 
199#### Section 5: Action Items
200 
201Create a prioritized, numbered list of specific actions across all prospects:
202 
203```markdown
204### Immediate Actions (This Week)
2051. **[Company]:** [Specific action] -- [why it's urgent]
2062. **[Company]:** [Specific action] -- [why it's urgent]
207 
208### Short-Term Actions (Next 2 Weeks)
2093. **[Company]:** [Specific action]
2104. **[Company]:** [Specific action]
211 
212### Pipeline Building Actions
2135. [Actions to strengthen weak areas of the pipeline]
214```
215 
216Each action item must be:
217- Tied to a specific company
218- Specific enough to execute (not "follow up" but "send personalized email to [Name] referencing [topic]")
219- Prioritized by impact and urgency
220 
221#### Section 6: Outreach Status
222 
223Track outreach progress across all prospects:
224 
225```markdown
226| Company | Outreach Created | Sequence Type | First Touch | Status | Response |
227|---------|-----------------|---------------|-------------|--------|----------|
228| Acme Corp | Yes | Email + LinkedIn | Pending | Not started | -- |
229| Beta Inc | No | -- | -- | Needs sequence | -- |
230```
231 
232Provide guidance:
233- Which prospects need outreach sequences created (suggest running `/sales prospect <url>` if missing)
234- Which have sequences ready to execute
235- Recommended order of outreach
236 
237#### Section 7: Pipeline Health Metrics
238 
239Calculate and display key pipeline metrics:
240 
241```markdown
242### Pipeline Health Dashboard
243 
244| Metric | Value | Assessment |
245|--------|-------|------------|
246| Total Prospects | X | [healthy/needs more] |
247| Average Score | X/100 | [strong/moderate/weak] |
248| A-Grade Prospects | X (Y%) | [target: 20-30%] |
249| Pipeline Coverage | X:1 | [deals needed vs. quota] |
250| Avg Component Spread | X pts | [consistency indicator] |
251| Highest Score | X | [company name] |
252| Lowest Score | X | [company name] |
253| Score Std Deviation | X | [pipeline diversity] |
254```
255 
256Add a Pipeline Health Assessment paragraph:
257- Overall health rating (Excellent / Good / Needs Attention / Critical)
258- Key strengths of the current pipeline
259- Key gaps or risks
260- Specific recommendations to improve pipeline health
261 
262#### Section 8: Weekly Focus
263 
264Recommend the top 3 prospects to focus on this week:
265 
266```markdown
267### This Week's Focus
268 
269#### Priority 1: [Company Name] (Score: X)
270- **Why focus now:** [timing, urgency, opportunity window]
271- **Monday-Tuesday:** [specific actions]
272- **Wednesday-Thursday:** [specific actions]
273- **Friday:** [review and prepare for next week]
274 
275#### Priority 2: [Company Name] (Score: X)
276- **Why focus now:** [reason]
277- **Key action:** [what to do]
278 
279#### Priority 3: [Company Name] (Score: X)
280- **Why focus now:** [reason]
281- **Key action:** [what to do]
282```
283 
284Selection criteria for weekly focus:
2851. Highest score that hasn't been contacted yet
2862. Prospect with time-sensitive trigger event
2873. Prospect where one more action could advance the stage
288 
289---
290 
291## Output Format
292 
293Write the complete report to `SALES-REPORT.md` in the current working directory.
294 
295```markdown
296# Sales Pipeline Report
297 
298> Generated on [date] | Prospects Analyzed: [count] | Average Score: [X]/100
299 
300## Executive Summary
301[3-5 paragraphs]
302 
303## Pipeline Dashboard
304[Full prospect table]
305 
306## Score Distribution
307[Distribution table and analysis]
308 
309## Top Prospects
310 
311### 1. [Company Name]
312[Detailed snapshot]
313 
314[... repeat for top 5]
315 
316## Action Items
317[Prioritized list]
318 
319## Outreach Status
320[Status table and guidance]
321 
322## Pipeline Health
323[Metrics dashboard and assessment]
324 
325## Weekly Focus
326[Top 3 prospects with specific actions]
327 
328---
329 
330## Methodology
331 
332- Company Fit: 25% of score (firmographics, tech stack, growth signals)
333- Contact Access: 20% of score (decision makers, personalization, warm paths)
334- Opportunity Quality: 20% of score (BANT qualification, pain severity, timeline)
335- Competitive Position: 15% of score (current tools, switching costs, advantages)
336- Outreach Readiness: 20% of score (personalization, channel strategy, messaging)
337 
338*Report generated by AI Sales Team | Refresh by running `/sales report`*
339```
340 
341---
342 
343## Quality Standards
344 
3451. **Data Integrity:** Only include data actually found in the prospect files. Never fabricate scores, contacts, or details.
3462. **Honest Assessment:** If the pipeline is weak, say so. Don't sugarcoat a pipeline full of C-grade prospects.
3473. **Actionable Output:** Every section must answer "so what?" and "what do I do next?"
3484. **Consistent Formatting:** All tables must be aligned and readable. All scores on the same scale.
3495. **Comparative Analysis:** Help the user understand how prospects compare to each other, not just individual scores.
3506. **Time-Sensitive:** Weekly focus should reflect actual urgency, not just highest scores.
3517. **Complete Coverage:** Every prospect found must appear in the dashboard. No prospect should be silently excluded.
352 
353---
354 
355## Important Rules
356 
3571. Read ALL prospect files before starting the report. Do not write the report incrementally.
3582. If a prospect file is malformed or missing key data, include the prospect with a note about missing data rather than excluding it.
3593. Sort prospects by score in all tables (highest first).
3604. Use consistent number formatting (scores as integers, percentages with one decimal).
3615. The report should be 250-350 lines of substantive content.
3626. Write the file to disk using the Write tool. Confirm to the user what was written.
3637. After writing, give the user a brief verbal summary of the pipeline status and top recommendation.
3648. If you find more than 20 prospect files, still include all of them but note that a large pipeline benefits from segmentation.
365 

Discussion

Alternatives

/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly. · MITPath A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Creator · MIT