# Prospect Pipeline Check

> Sweeps a CRM pipeline export for prospect-stage deals with no real two-way engagement from the prospect side — the earliest "is this even a deal" gate, before budget, buyer, or pain are even in scope. Use when auditing a prospect-stage pipeline for zombie deals a rep is carrying forward on outbound activity alone, or before a pipeline review to separate real opportunities from unanswered outreach.

- **Type:** Skill
- **Install:** `agentstack add skill-zime-ai-zime-gtm-skills-prospect-pipeline-check`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [zime-ai](https://agentstack.voostack.com/s/zime-ai)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [zime-ai](https://github.com/zime-ai)
- **Source:** https://github.com/zime-ai/zime-gtm-skills/tree/main/skills/prospect-pipeline-check
- **Website:** https://zime.ai

## Install

```sh
agentstack add skill-zime-ai-zime-gtm-skills-prospect-pipeline-check
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# GTM Prospect Pipeline Check

Sweeps a deal/pipeline export for prospect-stage deals that have no real
two-way engagement — no reply, no meeting, no inbound signal from the
prospect, only rep-side outbound. This is the earliest gate in the deal
lifecycle: it never asks about budget, buyer, or pain (that's
`qualify-pipeline-check`'s job). It only asks whether a human on the other
side has engaged at all. Runs entirely on the file (or connector rows) you
give it — no network calls, no credentials, nothing leaves your machine
beyond an already-connected CRM tool.

## When to use this

- RevOps or a sales manager wants to find prospect-stage deals a rep is
  carrying forward on outbound activity alone, with no prospect response.
- Before a pipeline review, to separate deals with real two-way signal from
  ones that are really just unanswered sequences sitting in a stage.
- A rep wants a gut-check on their own prospect list before it goes stale.

## How to run it

```
claude "run prospect-pipeline-check on ./exports/pipeline.csv"
```

**Input.** A `.csv` deal/pipeline export. There is no transcript mode for
this skill. If the conversation has a connector tool that can list
opportunities/deals, you may use it instead and treat the returned rows
exactly like CSV rows — CSV is the default path.

**Column detection.** Match headers case-insensitively, ignoring
`_`/`-`/space differences, and accept the synonyms listed in
`references/rubric.md`. If a column a check needs is missing, that check
reports **Unknown (column missing)** for every row — state this once up
front, and never infer the value from another column.

**Stage filter.** Operate only on rows whose stage fuzzy-matches "Prospect"
(e.g. `Prospect`, `Prospecting`, `Prospect pipeline`). Report how many rows
were in scope against how many the export held in total.

**Checks.** Run all six checks in `references/rubric.md` against every
in-scope row. Each check returns **Flagged**, **Clean**, or **Unknown**.
Every flagged row must cite the column name and the actual cell value that
triggered it (e.g. `close_date = 2026-01-14`, or `champion = (empty)`) — a
flag with no cited cell does not ship.

Before finalizing, run the reads-well-too check in `references/rubric.md`
— if a deal that clearly has a real, responsive prospect on the other end
still comes back flagged, the rubric is reading too strictly.

**Output.** One markdown table, flagged deals first, most flags first:

| Deal | Flags | Evidence | Suggested action |

Close with exactly two lines: `N of M deals in Prospect pipeline flagged`
and the single most common flag across the flagged deals. Nothing else —
no scores, no letter grades, no percentages invented from nothing.

## Sample data

`assets/sample-pipeline-prospect-pipeline-check.csv` — a synthetic
prospect-stage pipeline export with several deals that deliberately trigger
flags and at least two genuinely healthy deals. Run against it first.

## What this does not do

No CRM connection beyond an already-connected tool the conversation
provides, no API calls of its own, no telemetry, no data retention beyond
the current session. It reads the file (or rows) you point it at and
nothing else.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [zime-ai](https://github.com/zime-ai)
- **Source:** [zime-ai/zime-gtm-skills](https://github.com/zime-ai/zime-gtm-skills)
- **License:** MIT
- **Homepage:** https://zime.ai

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-zime-ai-zime-gtm-skills-prospect-pipeline-check
- Seller: https://agentstack.voostack.com/s/zime-ai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.