Pipeline Inspector

---
name: pipeline-inspector
description: Inspect a CRM pipeline export (CSV or pasted table) and return stage-age outliers, hygiene failures by rep, coverage by segment, and a commit/best-case forecast call with reasoning. Use when the user pastes or pipes deal data, asks for a pipeline review, a forecast call, slipped deals, stale deals, or rep hygiene. Not for single-deal qualification (see meddpicc-qualifier), for writing back to the CRM (see hubspot-crm-ops), or for territory design.
version: 1.0.0
license: Licensed per buyer — https://gtm-skills.com/terms
source: https://gtm-skills.com/skills/pipeline-inspector
---

# Pipeline Inspector

A pipeline export is a list of claims. Every row says a deal exists, has a size, sits in a stage, and will close on a date. Most rows are partly wrong. This skill reads the export the way a good RevOps lead reads it on Monday morning: it finds the rows that cannot be true, names the rep who owns each one, computes whether the quarter is covered, and produces a forecast call you can defend in one sentence. Output in, report out, no CRM access required. Winging it means a manager reads 140 rows in a meeting and calls the number from memory.

## When to use / When not to

**Use when**
- A manager, RevOps lead, or founder pastes or pipes a deal export and asks what is wrong with it.
- Someone needs a forecast number for a call today and wants the reasoning written down.
- A weekly pipeline review is coming and the agenda needs to be built from the data.
- A rep asks which of their deals will get flagged before the manager flags them.

**Not for**
- Qualifying one deal in depth. Use meddpicc-qualifier.
- Writing fixes back to HubSpot or Salesforce. Produce the fix list here, execute with hubspot-crm-ops.
- Quota setting, territory carving, comp design.
- Exports with no stage or close date columns. Say so and stop.

## Inputs the agent should collect

| Input | Required | If missing |
|---|---|---|
| Deal export (CSV, TSV, or pasted table) | Yes | Ask for it. Do not proceed on a description of the pipeline. |
| Column mapping: deal name, owner, stage, amount, close date, created date, last activity date, next step, stage entry date | Yes for the first five | Infer from headers. Confirm the mapping back in one line before analyzing. If stage entry date is absent, use last modified and say precision is reduced. |
| Stage order and which stages count as commit / best case | Yes | Ask. If the user shrugs, use the default map in `references/forecast-method.md` and label it as assumed. |
| Quarter end date and team quota | Yes for coverage and the call | Ask. Without quota, report pipeline totals but no coverage ratio. |
| Segment (SMB / mid-market / enterprise) per deal or per rep | No | Default to one segment. Coverage targets differ by segment, so say which one you applied. |
| Prior forecast snapshot | No | Enables variance analysis. Skip that section if absent. |

Never invent a deal, an amount, a rep, or a date. If a column is empty, the finding is "field missing," not a guess at the value.

## Process