agentleFS
alebgl77alebgl77/claude-inc/skills/pipeline-review/SKILL.md

pipeline-review

Skill21 starsChanged 4 months agoMITView on GitHub

Audits pipeline health from a deal list (CSV, table or plain notes) — prioritises deals, flags zombies and single-threaded risks, checks close-date realism and outputs a weekly action plan. Use when the user says "review my pipeline", "which deals should I focus on", "why is nothing closing", or shares a list of open deals.

13 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Apply the health checks: no dated next step = zombie.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pipeline Review — Pipeline Doctor

"Pipeline truth over pipeline comfort."

When to use

  • "Review my pipeline" (paste/attach deals: name, value, stage, last contact, next step)
  • "What should I focus on this week?"
  • "My forecast feels fake"
  • Weekly ritual; also before any forecast conversation
  • Works from a CSV, a markdown table, or messy notes — it will structure them first

Workflow

  1. Normalise the data into: deal, value, stage, last meaningful contact, next step (dated?), single or multi-threaded.
  2. Apply the health checks: no dated next step = zombie; last contact > 14 days = cooling; one contact person = single-threaded; close date in the past or "end of quarter" 3 quarters running = fiction; stage vs. evidence mismatch (e.g. "negotiation" but no proposal sent).
  3. Score priorities: value × probability × momentum. Big-but-dead loses to small-but-moving.
  4. Prescribe per deal: exactly one action — advance (specific move), revive (pattern-break touch), or kill (graceful close-out that preserves the relationship).
  5. Summarise the week: top 3 focus deals with their actions, deals to kill this week, and the one systemic habit to fix (found in the patterns — e.g. "you never set next steps on first calls").
  6. Forecast sanity line: weighted realistic total vs. optimistic total, in one sentence.

Output format

## Pipeline review — {date} · {n} deals · realistic: {€X} (optimistic: {€Y})

| Deal | Value | Health | Diagnosis | THE action this week |
|------|-------|--------|-----------|----------------------|
| ...  | ...   | 🟢🟡🔴 | ...       | ...                  |

**Focus 3**: 1. {deal} → {action} 2. ... 3. ...
**Kill list**: {deals} — with the close-out line to send
**Systemic fix**: {the one habit}

Quality bar

  • Every deal gets exactly one action, none gets "keep monitoring"
  • Zombies named and killed out loud, with a graceful exit message
  • Single-threaded deals flagged with a second-contact suggestion
  • Realistic vs. optimistic totals both stated
  • The systemic fix targets a pattern, not a deal

Example

Ask: "12 deals pasted from my notes, which 3 matter?" Produced: normalised table, 4 zombies flagged (2 killed with exit lines), focus 3 with concrete moves ("send option-B nudge before Thursday"), systemic fix: every call ends with a dated next step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.