pipeline-health-analyzer

pipeline-health-analyzer is a skill for Claude Code, Codex from microsoft/dataverse-business-skills. It costs 73 tokens per session (4,055 once invoked), scanned A, original, MIT.

A sales pipeline review tool that examines open deals for signs of risk, such as stalled progress, missing next steps, weak qualification, or uneven stages. A sales pipeline is the set of potential deals currently being worked on.

In plain words
What is it for?
Use it to review all open opportunities or filtered groups, find stuck or at-risk deals, check deal information, and decide what action should happen next.
Why use it?
It turns a manual pipeline review into a prioritized list of problems and suggested follow-ups. Teams can focus attention on deals most likely to need intervention.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to review all open opportunities or filtered groups, find stuck or at-risk deals, check deal information, and decide what action should happen next.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/dataverse-business-skills/pipeline-health-analyzer
About the project

Dataverse Business Skills is a collection of natural-language instructions that teach AI agents how to follow business processes, policies, and domain knowledge for Microsoft Dataverse. Organizations use the skills with Dataverse environments connected to products such as Power Apps, Dynamics 365, or Power Platform. The catalogue entries are skills from this collection.

microsoft/dataverse-business-skills · 50 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/dataverse-business-skills --skill pipeline-health-analyzer
Clone the repo
git clone --depth 1 https://github.com/microsoft/dataverse-business-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for pipeline-health-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer/github.svg)](https://agentmods.dev/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer)
Your own site
<a href="https://agentmods.dev/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer"><img src="https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer/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.

agentmods 80×15 button for pipeline-health-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer"><img src="https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/pipeline-health-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,055 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.04055
Opus 5 $0.00036 $0.02027
Sonnet 5 $0.00015 $0.00811
Haiku 4.5 $0.00007 $0.00405

Measured 12d ago against content hash c99e9eac7b25, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pipeline-health-analyzer 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.

skills/pipeline-health-analyzer/SKILL.md · 454 lines

How it starts

The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pipeline Health Analyzer

Sales teams often review pipelines weekly to identify at-risk deals manually. This skill automates that process by analyzing opportunity records against configurable health criteria, flagging issues, and providing prioritized recommendations to improve deal progression.

Instructions

Step 1: Determine Analysis Scope

Identify the pipeline scope to analyze:

Option A - Full Pipeline:

  • All open opportunities (statecode = 0)

Option B - Filtered View:

  • By owner (specific sales rep or team)
  • By time period (opportunities created/modified in range)
  • By value threshold (deals above $X)
  • By sales stage

Query Example for Full Pipeline:

SELECT opportunityid, name, estimatedvalue, estimatedclosedate, createdon, modifiedon,
       salesstage, stepname, customerid, accountid, contactid, ownerid,
       budgetstatus, need, purchasetimeframe, purchaseprocess, decisionmaker,
       msdyn_opportunityscore, msdyn_opportunitygrade, msdyn_forecastcategory,
       closeprobability, description, currentsituation, customerneed, customerpainpoints
FROM opportunity
WHERE statecode = 0
Step 2: Analyze Individual Opportunity Health

For each opportunity, evaluate against these health dimensions:

2.1 Stuck Deal Detection Query activity history for each opportunity:

SELECT activityid, activitytypecode, createdon, actualend, statecode
FROM activitypointer
WHERE regardingobjectid = '[opportunityid]'
ORDER BY createdon DESC

Stuck Deal Criteria:

Stage Days Without Activity = Warning Days Without Activity = Critical
Qualify 7 days 14 days
Develop 10 days 21 days
Propose 5 days 10 days
Close 3 days 7 days

Flag as Stuck if:

  • No activities in threshold period
  • Only automated activities (emails) but no calls/meetings
  • Last activity was over 2 weeks ago regardless of stage

2.2 Missing Next Steps Analysis Check for scheduled future activities:

SELECT activityid, activitytypecode, scheduledstart, scheduledend, subject, statecode
FROM activitypointer
WHERE regardingobjectid = '[opportunityid]'
AND statecode = 0

Read the full file on GitHub · 454 lines

Changes

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.

  1. 12d ago First seen · 454 lines · 73 tokens per session scan A c99e9eac7b25

Subscribe to this mod's changes

pipeline-health-analyzer is a skill published in the GitHub repository microsoft/dataverse-business-skills (50 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 4,055 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens