Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add matellez/claude-skills --skill pipeline-health-reviewergit clone --depth 1 https://github.com/matellez/claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/matellez/claude-skills/pipeline-health-reviewer)<a href="https://agentmods.dev/skills/matellez/claude-skills/pipeline-health-reviewer"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/pipeline-health-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/matellez/claude-skills/pipeline-health-reviewer"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/pipeline-health-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00140 | $0.01640 |
| Opus 5 | $0.00070 | $0.00820 |
| Sonnet 5 | $0.00028 | $0.00328 |
| Haiku 4.5 | $0.00014 | $0.00164 |
Grade A, and why
pipeline-health-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- pipeline-health-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Health Reviewer: Velocity and Stage Diagnosis
This skill diagnoses why a B2B pipeline is stalling and delivers a prioritized set of structural fixes. It treats pipeline problems as systems problems, not sales performance problems, unless the evidence points clearly to the latter.
HOW TO SET UP THIS SKILL
This skill works best with specific data. Ask the user to provide as much of the following as possible:
- Total pipeline value and number of open deals
- Deal stage names and what percentage of pipeline sits in each
- Average days in each stage (or average total sales cycle length)
- Average deal size
- Win rate and loss rate
- Where most deals are lost (stage and reason if known)
- Whether they have a defined ICP and qualification framework
If no data is provided, run the diagnostic as a structured interview, asking for the key numbers before delivering conclusions.
The Pipeline Diagnostic Framework
A stalling pipeline has one of four root causes. Identify which one or which combination applies before recommending fixes.
Root cause 1: Stage definition problems
Deals appear to move but do not actually progress because stages are defined by time or activity rather than buyer behavior.
Signals:
- Deals sitting in "Discovery" or "Proposal" for 60+ days
- Reps moving deals forward to show activity rather than real progress
- Stage names that describe what the rep did, not what the buyer did
- No exit criteria that requires buyer confirmation before advancing
The fix: Redefine stages around buyer actions, not sales actions. A deal should not move to "Proposal" because the rep sent a proposal. It should move when the buyer has confirmed they received it, reviewed it, and have a specific next step scheduled. This is the distinction between deal stage theater and real pipeline visibility.
Root cause 2: ICP and qualification gaps
Pipeline is full but close rates are low because deals that should not be in the pipeline are in the pipeline. This inflates the number, destroys forecast accuracy, and wastes rep time on deals that will never close.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 212 lines · 140 tokens per session scan A 0101913f82e7
pipeline-health-reviewer is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 140 tokens to every session and 1,640 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
igce-builder-lh-tm
Trigger for: Labor-Hour IGCE, LH estimate, Time-and-Materials IGCE, T&M estimate, burdened hourly rate, burden multiplier, labor-category ceiling hours, materials estimate, proposed LH/T&M rate validation, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable LH/T&M estimates using BLS OEWS…
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.