Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
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.
Install Flow Metrics Interpreter
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/flow-metrics-interpreter .claude/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .claude/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/flow-metrics-interpreter .agents/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .agents/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/flow-metrics-interpreter .cursor/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .cursor/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/flow-metrics-interpreter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/flow-metrics-interpreter .gemini/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .gemini/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/flow-metrics-interpreter .github/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .github/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills flow-metrics-interpreter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/flow-metrics-interpreter .opencode/skills/flow-metrics-interpreter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "flow-metrics-interpreter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/flow-metrics-interpreter into .opencode/skills/flow-metrics-interpreter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-metrics-interpreter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
flow-metrics-interpreter- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 563 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 6 steps: Distributions over averages. Cycle… → Read metrics together. Rising cycle time… → WIP is the lever. Little's Law: cycle… → …
- Asked to interpret cycle time
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Read the Flow, Not… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Flow Metrics Interpreter is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Task management. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to interpret cycle time
- What do our flow/Actionable-Agile metrics mean
- Why is delivery slow
- Read our Kanban metrics
Example prompts
- “/flow-metrics-interpreter”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Distributions over averages. Cycle time's spread and tail (the 85th percentile) matter more than the mean — averages hide the pain.
- Read metrics together. Rising cycle time + flat throughput + high WIP = you're starting too much, not finishing. One metric alone lies.
- WIP is the lever. Little's Law: cycle time ≈ WIP ÷ throughput. Too much in progress is the most common, most fixable cause of slow delivery.
- Aging is the early warning. Items aging past their usual cycle time are today's problem; end-of-sprint is too late to notice.
- Baselines beat targets. Compare to your own trend, not an industry number; a "good" cycle time is context-specific.
- Watch for gaming. Any metric made a target gets gamed — smaller tickets to shrink cycle time, etc. Name it.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Flow Metrics Interpreter loads about 1.1k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 563 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 563 words, ~1,085 tokens.
Download SKILL.mdSave it as
.claude/skills/flow-metrics-interpreter/SKILL.md (or your agent's skills folder).- name
- flow-metrics-interpreter
- description
- 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.
Flow Metrics Interpreter
A dashboard of cycle time and throughput is useless until someone says what it means — is the flow healthy, where's it clogging, and what should the team try Monday. This reads the metrics together (they only make sense in relation), points at the likely bottleneck, and proposes specific experiments — while flagging the classic trap of optimising the number instead of the flow it's meant to measure.
What This Skill Produces
- The health read — per metric (cycle time, throughput, WIP, aging), what "good" looks like and where you are
- The bottleneck the numbers point to — read together, where work is actually stalling
- 2–3 process experiments — concrete, small, reversible things to try next (with what to watch)
- The gaming trap — how this metric gets optimised dishonestly, so you don't
Required Inputs
Ask for these if not provided:
- 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
Framework: Read the Flow, Not the Number
- Distributions over averages. Cycle time's spread and tail (the 85th percentile) matter more than the mean — averages hide the pain.
- Read metrics together. Rising cycle time + flat throughput + high WIP = you're starting too much, not finishing. One metric alone lies.
- WIP is the lever. Little's Law: cycle time ≈ WIP ÷ throughput. Too much in progress is the most common, most fixable cause of slow delivery.
- Aging is the early warning. Items aging past their usual cycle time are today's problem; end-of-sprint is too late to notice.
- Baselines beat targets. Compare to your own trend, not an industry number; a "good" cycle time is context-specific.
- Watch for gaming. Any metric made a target gets gamed — smaller tickets to shrink cycle time, etc. Name it.
Show full SKILL.md (225 more words)Show less
Output Format
Flow read — [team] · [period]
| Metric | Reading | Health |
|---|---|---|
| Cycle time (p50 / p85) | … | 🟢🟡🔴 |
| Throughput | … | |
| WIP | … | |
| Aging (items past usual) | … |
What the numbers point to: [likely bottleneck, from reading them together].
Experiments to try (pick 1–2)
- [e.g. set a WIP limit on 'In Review'] — watch: [what should move].
Don't game it: [how this metric gets faked, and the honest alternative].
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
- Comparison is to the team's own baseline, not an arbitrary target
- The gaming trap for the recommended metric is named
Anti-Patterns
- 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.
Example Trigger Phrases
- "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?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/flow-metrics-interpreter of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Flow Metrics Interpreter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Flow Metrics Interpreter this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Superset Agent Standupsuperset-sh/superset | 15k | — | ~712 | Automated safety check: Pass | Custom licence | |
| AgentRQ Workspace Agentagentrq/agentrq | 1.1k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| Markdown Task Managerioniks/MarkdownTaskManager | 535 | — | ~2.2k | Automated safety check: Pass | MPL-2.0 | |
| Pi Messenger Crewnicobailon/pi-messenger | 719 | — | ~3.7k | Automated safety check: Pass | None | |
| Codekanban CLIfy0/CodeKanban | 226 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
AgentRQ Workspace Agent
agentrq/agentrq
Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.
Markdown Task Manager
ioniks/MarkdownTaskManager
A skill your agent uses when managing tasks, the system is a Kanban task manager based on local Markdown files (kanban.md and archive.md).
Pi Messenger Crew
nicobailon/pi-messenger
Orchestrator reference for pi-messenger Crew planning, task management, configuration, and agent coordination.
Codekanban CLI
fy0/CodeKanban
Operate CodeKanban workflows, terminal sessions, and web sessions through the installable codekanban-cli command.
Kanban Video Orchestrator
Luciole-Studio/Misaka-Agent
Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Flow Metrics Interpreter
What does Flow Metrics Interpreter do?
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. Flow Metrics Interpreter is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Flow Metrics Interpreter?
Flow Metrics Interpreter fits situations like: asked to interpret cycle time; what do our flow/Actionable-Agile metrics mean; why is delivery slow; read our Kanban metrics.
How do I install Flow Metrics Interpreter in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a claude-code`. Or copy the skill folder (skills/flow-metrics-interpreter in mohitagw15856/pm-claude-skills) into .claude/skills/flow-metrics-interpreter in your project. Claude Code loads it when a task matches its description.
How do I install Flow Metrics Interpreter in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a codex`. Or copy the skill folder (skills/flow-metrics-interpreter in mohitagw15856/pm-claude-skills) into .agents/skills/flow-metrics-interpreter in your project. Codex loads it when a task matches its description.
Can I use Flow Metrics Interpreter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill flow-metrics-interpreter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flow-metrics-interpreter, .gemini/skills/flow-metrics-interpreter, .github/skills/flow-metrics-interpreter and .opencode/skills/flow-metrics-interpreter in your project.
What does Flow Metrics Interpreter need to run?
SKILL.md names no scripts, command-line tools or credentials: Flow Metrics Interpreter is instructions for the agent only.
Does Flow Metrics Interpreter access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Flow Metrics Interpreter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Flow Metrics Interpreter use?
Flow Metrics Interpreter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Flow Metrics Interpreter use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Flow Metrics Interpreter?
Skills that share tags, products or a category with Flow Metrics Interpreter: Superset Agent Standup (superset-sh/superset, 15k stars), AgentRQ Workspace Agent (agentrq/agentrq, 1.1k stars), Markdown Task Manager (ioniks/MarkdownTaskManager, 535 stars) and Pi Messenger Crew (nicobailon/pi-messenger, 719 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Flow Metrics Interpreter?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.