Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmetrics-dashboardExecute the skills CLI command in your project's root directory to begin installation:
Fetches metrics-dashboard from phuryn/pm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate metrics-dashboard. Access via /metrics-dashboard in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
9.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.6K
stars
Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.
You are designing a metrics dashboard for $ARGUMENTS.
If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first.
Metrics vs KPIs vs NSM: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period. North Star Metric = a single customer-centric KPI that is a leading indicator of business success.
4 criteria for a good metric (Ben Yoskovitz, Lean Analytics): (1) Understandable — creates a common language. (2) Comparative — over time, not a snapshot. (3) Ratio or Rate — more revealing than whole numbers. (4) Behavior-changing — the Golden Rule: "If a metric won't change how you behave, it's a bad metric."
8 metric types: Vanity vs Actionable (only actionable metrics change behavior), Qualitative vs Quantitative (WHAT vs WHY — you need both; never stop talking to customers), Exploratory vs Reporting (explore data to uncover unexpected insights), Lagging vs Leading (leading indicators enable faster learning cycles, e.g. customer complaints predict churn).
5 action steps: (1) Audit metrics against the 4 good-metric criteria. (2) Update dashboards — ensure all key metrics are good ones. (3) Identify vanity metrics — be careful how you use them. (4) Classify leading vs lagging indicators. (5) Pick one problem and dig deep into the data.
For case studies and more detail: Are You Tracking the Right Metrics? by Ben Yoskovitz
Identify the metrics framework — organize metrics into layers:
North Star Metric: The single metric that best captures core value delivery
Input Metrics (3-5): The levers that drive the North Star
Health Metrics: Guardrails that ensure overall product health
Business Metrics: Revenue, cost, and unit economics
For each metric, define:
| Metric | Definition | Data Source | Visualization | Target | Alert Threshold |
|---|---|---|---|---|---|
| [Name] | [Exact calculation: numerator/denominator, time window] | [Where the data comes from] | [Line chart / Bar / Number / Funnel] | [Goal value] | [When to trigger an alert] |
Design the dashboard layout:
┌─────────────────────────────────────────────┐
│ NORTH STAR: [Metric] — [Current Value] │
│ Trend: [↑/↓ X% vs last period] │
├──────────────────┬──────────────────────────┤
│ Input Metric 1 │ Input Metric 2 │
│ [Sparkline] │ [Sparkline] │
├──────────────────┼──────────────────────────┤
│ Input Metric 3 │ Input Metric 4 │
│ [Sparkline] │ [Sparkline] │
├──────────────────┴──────────────────────────┤
│ HEALTH: [Latency] [Error Rate] [NPS] │
├─────────────────────────────────────────────┤
│ BUSINESS: [MRR] [CAC] [LTV] [Churn] │
└─────────────────────────────────────────────┘
Set review cadence:
Define alerts:
Recommend tools based on the user's context:
Think step by step. Save the dashboard specification as a markdown document.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: metrics-dashboard is the kind of skill you can hand to a new teammate without a long onboarding doc.
metrics-dashboard has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for metrics-dashboard matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: metrics-dashboard is focused, and the summary matches what you get after install.
Keeps context tight: metrics-dashboard is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: metrics-dashboard is focused, and the summary matches what you get after install.
metrics-dashboard reduced setup friction for our internal harness; good balance of opinion and flexibility.
metrics-dashboard has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend metrics-dashboard for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: metrics-dashboard is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 68