What do I need to use Flow Metrics Interpreter?

The metrics; The baseline; Team context; What prompted this.

Is Flow Metrics Interpreter free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Flow Metrics Interpreter

Q: How do I know the Flow Metrics Interpreter output is good?

The skill verifies itself against its own quality checks: Cycle time is read as a distribution (p85/tail), not just an average; Metrics are interpreted together, not in isolation; WIP / Little's Law is considered as the likely lever for slow flow; Aging/stuck work is surfaced as the early signal.

🔵 Stable🕐 updated 2026-08-04 🔷 SkillSpec L3 pm-delivery

Read your team's flow metrics — cycle time, throughput, WIP, aging work — and say what they actually mean and what to try, not just restate the numbers. Use when asked to interpret cycle time, what do our flow/Actionable-Agile metrics mean, why is delivery slow, or read our Kanban metrics. Produces the health read per metric, the likely bottleneck the numbers point to, 2–3 concrete process experiments to run next, and the trap-to-avoid so the team doesn't game the metric instead of fixing the flow.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Interpret our cycle time and throughput — is delivery healthy?”“What do these Actionable Agile metrics actually mean for us?”“Why does our delivery feel slow? Here are our flow numbers.”“Read our Kanban metrics and suggest experiments.”“Our WIP is high and cycle time is climbing — what do we do?”

What to give it

▸The metrics — cycle time (distribution, not just average), throughput per period, current WIP, and any aging/stuck items

▸The baseline — a few periods of history if you have it (a single number can't show a trend)

▸Team context — team size, work type, and any recent changes (reorg, new process, holidays) that explain a shift

▸What prompted this — a felt slowdown, a planning question, a stakeholder asking

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Cycle time is read as a distribution (p85/tail), not just an average

✓Metrics are interpreted together, not in isolation

✓WIP / Little's Law is considered as the likely lever for slow flow

✓Aging/stuck work is surfaced as the early signal

✓Comparison is to the team's own baseline, not an arbitrary target

✓The gaming trap for the recommended metric is named

⚠️ What it refuses to do

**Restating the numbers** without interpreting them.

**Averages only** — hiding the painful tail of cycle time.

**One metric in isolation** — throughput without WIP tells you nothing about health.

**Industry-target worship** — "cycle time should be 3 days" ignores your context.

**Recommending a metric as a target** without warning how it gets gamed.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="flow-metrics-interpreter"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Flow Metrics Interpreter is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog