Metrics
menkesu/awesome-pm-skills
Builds your north star metric, a metric tree with owned input metrics and guardrails, and a review cadence, as a one-page metrics spec you can paste into a doc.
Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions.
Install Metrics Dashboard
$ npx skills add borghei/Claude-Skills --skill metrics-dashboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills metrics-dashboard --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .claude/skills/metrics-dashboard && 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 "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .claude/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboardType 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 borghei/Claude-Skills --skill metrics-dashboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills metrics-dashboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .agents/skills/metrics-dashboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .agents/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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 borghei/Claude-Skills --skill metrics-dashboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills metrics-dashboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .cursor/skills/metrics-dashboard && 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 "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .cursor/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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/borghei/Claude-Skills.git --path project-management/discovery/metrics-dashboard--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 borghei/Claude-Skills --skill metrics-dashboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills metrics-dashboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .gemini/skills/metrics-dashboard && 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 "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .gemini/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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 borghei/Claude-Skills metrics-dashboardInstalls 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 borghei/Claude-Skills --skill metrics-dashboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .github/skills/metrics-dashboard && 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 "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .github/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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 borghei/Claude-Skills --skill metrics-dashboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills metrics-dashboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/discovery/metrics-dashboard .opencode/skills/metrics-dashboard && 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 "metrics-dashboard" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/metrics-dashboard into .opencode/skills/metrics-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metrics-dashboard", 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
metrics-dashboard- GitHub stars
- 886
- Token cost
- ~1.8k tokens
- SKILL.md length
- 848 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions.
- Works in 7 steps: Confirm the North Star → Decompose to input metrics → Identify guardrails → …
- Building dashboard architecture: layers
- SKILL.md covers When to use this skill, The 4 dashboard layers, Clarify First and Workflow, plus 5 more sections
- Runs Python scripts from its folder; calls python3
What it does
Metrics Dashboard is an agent skill from borghei/Claude-Skills. Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions. Use when building dashboard architecture: layers, owners, cadence, and visualization.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/dashboard_spec_template.md`, `references/dashboard-anti-patterns.md` and `references/dashboard-architecture.md`).
It sits in Product & Project Management, covering Product metrics and LLM guardrails. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Building dashboard architecture: layers
- Tasks that involve Product metrics
- Tasks that involve LLM guardrails
Example prompts
- “/metrics-dashboard”
Requirements
- Python 3
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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
Metrics Dashboard loads about 1.8k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 848 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); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 848 words, ~1,777 tokens.
Download SKILL.mdSave it as
.claude/skills/metrics-dashboard/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- metrics-dashboard
- description
- Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions. Use when building dashboard architecture: layers, owners, cadence, and visualization.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- product-discovery
- metadata.updated
- 2026-05-27
- metadata.python-tools
- dashboard_designer.py
- metadata.tech-stack
- metrics, dashboard, north-star, hexagonal-metrics
Metrics Dashboard
A dashboard architecture skill: which metrics go where, at which cadence, for which audience, with which visualization. Focused on producing the ONE artifact a team uses to make decisions — not the 30-chart dashboard nobody opens.
When to use this skill
- New product / feature launch — what to instrument and watch
- Existing dashboard audit — what to cut, add, refactor
- Team-level OKR tracking — operational dashboard for the team
- Exec readouts — board / monthly business review dashboard
- Cross-functional alignment — what does "success" look like?
The 4 dashboard layers
- North Star — 1 metric that summarizes value delivered
- Input metrics (3-5) — the drivers of NS
- Guardrails (3-5) — what we DON'T want to sacrifice (counter-metrics)
- Operational metrics (4-8 per team) — what we actually act on weekly
A dashboard ≠ all metrics. A dashboard = these 11-22 metrics presented for fast decision-making.
Clarify First
Before designing the dashboard, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- North Star metric — defined or not (it is the root of all 4 layers; if undefined, define it first via
north-star-metric) - Audience — board/exec / functional team / all-hands / IC (sets the max top-level metric count, 5-8 down to 1-3)
- Team structure — which teams act on this (operational metrics are 4-8 per team with named owners)
- Available instrumentation — what data you actually capture (you can't show a metric you don't measure; bounds refresh cadence)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Workflow
Step 1 — Confirm the North Star
Already defined? Use it. Not defined? See project-management/execution/north-star-metric.
A good NS:
- Behavioral or business
- Moves week-over-week
- Hard to game without delivering real value
- One number
Step 2 — Decompose to input metrics
For each NS, identify 3-5 inputs whose combined movement drives it.
Example for NS "Weekly Active Companies × Messages Sent per Company":
- Acquisition rate
- Activation rate (% reaching 50 messages in 14 days)
- Retention rate (W4 cohort)
- Expansion (adds users / channels)
Step 3 — Identify guardrails
What could move the NS up while damaging the underlying value?
Example guardrails:
- Spam rate (if NS = messages, more messages can include spam)
- User-reported complaints
- Power-user churn (vs total churn)
- Support ticket volume
- Latency / error rate
Step 4 — Identify operational metrics per team
The 4-8 metrics each team needs to act weekly:
- Growth team: funnel conversion, channel CAC, signup quality
- Retention team: cohort retention, save-room saves
- Platform team: SLO posture, on-call health, deploy freq
- Trust & safety: spam reports, removed accounts, false-positive rate
Step 5 — Define visualization + cadence per metric
Each metric needs:
- Visualization: line chart / funnel / cohort heatmap / bar
- Comparison: vs prior period / vs target / vs cohort baseline
- Refresh cadence: real-time / hourly / daily / weekly / monthly
- Owner: named team
Step 6 — Run dashboard_designer.py
Audit: too many top-level metrics, no guardrails, vanity metrics, missing owners, missing comparisons.
python3 project-management/discovery/metrics-dashboard/scripts/dashboard_designer.py \
--input dashboard_spec.json --format markdownStep 7 — Sunset stale metrics
Quarterly: kill metrics no team looked at. Dashboards rot; pruning is healthy.
Decision frameworks
Top-level metric count
| Audience | Max top-level | Why |
|---|---|---|
| Board / exec | 5-8 | Limited attention; high signal/noise |
| Functional team | 4-8 | Actionable; weekly review |
| All-hands | 3-5 | Communicable; team rallies |
| Individual contributor | 1-3 | Their direct impact |
Show full SKILL.md (326 more words)Show less
Visualization fit
| Question | Best visualization |
|---|---|
| Is it changing over time? | Line chart |
| How much vs target? | Gauge / bullet |
| Drop-off at each step? | Funnel |
| Retention over time? | Cohort heatmap |
| Distribution? | Histogram |
| Composition? | Stacked area / pie (rare) |
| Comparison across groups? | Grouped bar |
| Relationship? | Scatter |
Avoid pie charts beyond 3 slices. Avoid 3D charts always.
Vanity vs actionable test
For each candidate metric: "If this moved up 10% next week, what would we do?"
- Have answer → actionable; keep
- No answer → vanity; cut
Comparison discipline
Every chart needs a comparison anchor:
- vs prior period (week / month / quarter)
- vs target
- vs cohort baseline
- vs competitor benchmark (rare; usually unreliable)
A chart with no comparison is a number floating in space.
Common engagements
"Build us a dashboard for the new product line"
- Confirm North Star.
- Decompose to 3-5 inputs.
- Identify 3-5 guardrails.
- Per team: 4-8 operational metrics.
- Spec viz + cadence + owner per metric.
- Pilot for 4 weeks; cut what nobody opens.
"Audit our existing dashboard"
- List every metric currently shown.
- Tag each: NS / input / guardrail / operational / vanity.
- Cut all vanity.
- Cut operational that no team looks at.
- Add missing guardrails.
- Limit each audience to its max.
"Help us track an OKR"
- Map OKR to metric: KR → metric.
- KR should be the metric.
- Inputs = what moves the KR.
- Guardrails = what we won't sacrifice.
Anti-patterns to avoid
- 30+ metrics on one screen. Decision-making dies.
- No guardrails. NS optimization without counter-balance.
- All metrics for all audiences. Exec doesn't need eng team metrics.
- No comparisons. Numbers without context.
- Real-time everything. Most metrics don't need it (and it's expensive).
- No owner per metric. Orphan metrics rot.
- Vanity metrics (page views, signups alone). Not action-driving.
- No cadence on review. Dashboard exists; team doesn't use it.
References
references/dashboard-architecture.md— layers, cadence, visualization patternsreferences/dashboard-anti-patterns.md— common failures + fixes
Related skills
project-management/execution/north-star-metric— define THE one numberproduct-team/product-analytics— metric tree + cohort + funnelproduct-team/ab-test-setup— experimentationc-level-advisor/chief-data-officer-advisor— platform context
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in project-management/discovery/metrics-dashboard of borghei/Claude-Skills.
- SKILL.md
- assets/dashboard_spec_template.md
- references/dashboard-anti-patterns.md
- references/dashboard-architecture.md
- scripts/dashboard_designer.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Metrics Dashboard 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 |
|---|---|---|---|---|---|---|
| Metrics Dashboard this skillborghei/Claude-Skills | 886 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Metricsmenkesu/awesome-pm-skills | 433 | — | ~5k | Automated safety check: Pass | Custom licence | |
| Kpi Frameworkericrisco/rsc-harness | 174 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Swarmaglitch-rabin/swarma | 173 | — | ~4.4k | Automated safety check: Notes | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| AI Product Strategy InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Kpi Framework
ericrisco/rsc-harness
A skill your agent uses when a team must decide what to measure before building anything — picking one north-star metric, separating leading input drivers from lagging outputs, adding guardrails so…
Swarma
glitch-rabin/swarma
Agent teams that run growth experiments and build their own playbook.
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
AI Product Strategy Interviewer
PrepLabsAI/InterviewMentor
A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.
App Spec Packager
instructa/agent-skills
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Questions about Metrics Dashboard
What does Metrics Dashboard do?
Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions. Metrics Dashboard is an agent skill from borghei/Claude-Skills. Design a product metrics dashboard — North Star, input metrics, and guardrails — that a team actually uses to make decisions.
When should I use Metrics Dashboard?
Metrics Dashboard fits situations like: building dashboard architecture: layers; tasks that involve Product metrics; tasks that involve LLM guardrails.
How do I install Metrics Dashboard in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill metrics-dashboard -a claude-code`. Or copy the skill folder (project-management/discovery/metrics-dashboard in borghei/Claude-Skills) into .claude/skills/metrics-dashboard in your project. Claude Code loads it when a task matches its description.
How do I install Metrics Dashboard in Codex?
Run `npx skills add borghei/Claude-Skills --skill metrics-dashboard -a codex`. Or copy the skill folder (project-management/discovery/metrics-dashboard in borghei/Claude-Skills) into .agents/skills/metrics-dashboard in your project. Codex loads it when a task matches its description.
Can I use Metrics Dashboard 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 borghei/Claude-Skills --skill metrics-dashboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metrics-dashboard, .gemini/skills/metrics-dashboard, .github/skills/metrics-dashboard and .opencode/skills/metrics-dashboard in your project.
What does Metrics Dashboard need to run?
Going by SKILL.md and its folder, Metrics Dashboard needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Metrics Dashboard 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 Metrics Dashboard 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Metrics Dashboard use?
Metrics Dashboard is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Metrics Dashboard use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Metrics Dashboard?
Skills that share tags, products or a category with Metrics Dashboard: Metrics (menkesu/awesome-pm-skills, 433 stars), Kpi Framework (ericrisco/rsc-harness, 174 stars), Swarma (glitch-rabin/swarma, 173 stars) and Prd (juanandresgs/claude-ctrl, 193 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Metrics Dashboard?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/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.