metrics-dashboard · emotixco — Claude Code skill: metrics and setup
The metrics-dashboard Claude Code skill selects startup metrics and builds a tracking plan. It activates when a founder asks what to measure or how to report results to investors.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a claude-codeWhat metrics-dashboard does
The skill identifies the startup’s stage and picks exactly five metrics for weekly tracking. Each gets a precise definition, a current value or calculation method, targets for 30, 60, and 90 days, and a concrete response if it falls short. It also flags vanity metrics and suggests what to monitor instead.
It reads founder/facts.md, founder/product-brief.md, founder/mvp-scope.md, founder/pricing-strategy.md, and founder/go-to-market.md, then writes the result to founder/metrics-dashboard.md. It needs the product, its stage, and any current figures. The output includes a lean setup for analytics, revenue, feedback, and a dashboard, plus events to track and a weekly review template. If fundraising is planned within the next 6 months, it adds investor-facing metrics and benchmark links with publication years. The weekly review is designed to take under 15 minutes.
What it helps with
- choose five metrics for a startup’s current stage
- set targets and responses for metrics that fall behind
- replace vanity metrics with decision-making measures
- plan basic event and revenue tracking
- prepare a weekly metrics report for investors
Example prompts for the agent
- Choose five metrics for our product’s current stage and save the plan to
founder/metrics-dashboard.md. - Create a weekly review template for the metrics investors will ask about.
- Use our current figures to set targets for the next 30, 60, and 90 days.
How to install metrics-dashboard
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a claude-code2Manually: put the files in place
~/.claude/skills/metrics-dashboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/metrics-dashboard/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a codex2Manually: put the files in place
.agents/skills/metrics-dashboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a cursor2Manually: put the files in place
.cursor/skills/metrics-dashboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/metrics-dashboard2Manually: put the files in place
.github/skills/metrics-dashboard/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/metrics-dashboardManually: put the files in place
.devin/skills/metrics-dashboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about metrics-dashboard
How do I install metrics-dashboard in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill metrics-dashboard -a claude-code. The skill file is placed at ~/.claude/skills/metrics-dashboard/SKILL.md.
What does metrics-dashboard do?
It selects five metrics based on a startup’s stage and gives each a definition, targets, and an action for falling short. It also creates a tracking plan and a weekly review template.
What information does metrics-dashboard need?
Provide the product, its stage, and any current figures. The skill also reads files in founder/, including founder/facts.md and founder/product-brief.md.
Source text
SKILL.md · MIT
---
name: metrics-dashboard
description: Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors.
argument-hint: "[your product, stage, and current metrics]"
allowed-tools: Read Edit(founder/**) WebSearch WebFetch
---
You are a startup analytics advisor. You know which metrics drive decisions at each stage and which ones only look good.
Input: $ARGUMENTS
## Before you start
Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it.
- Reads: `founder/facts.md`, `founder/product-brief.md`, `founder/mvp-scope.md`, `founder/pricing-strategy.md`, `founder/go-to-market.md`
- Needs: the product, the stage, and any current numbers
- Saves to: `founder/metrics-dashboard.md`
## Instructions
### 1. Stage assessment
| Stage | Focus | Key metrics |
|-------|-------|-------------|
| Pre-launch | Validation | Waitlist signups, interview conversion, survey responses |
| Post-launch (0-100 users) | Engagement | Activation rate, D1/D7 retention, core action completion |
| Growth (100-1000 users) | Retention and revenue | MRR, churn, NPS, CAC, feature adoption |
| Scale (1000+ users) | Efficiency and expansion | LTV/CAC, net revenue retention, payback period |
Say which stage the founder is in and tailor everything below to it.
### 2. The five metrics
Exactly 5 metrics to track weekly. For each:
- **Name** and exact definition (for example "Activation rate = % of signups who complete [specific action] within 7 days")
- **Current value,** or how to calculate it
- **Target** for 30, 60, and 90 days
- **Why this metric:** the decision it informs
- **If below target:** a specific action, not "improve it"
### 3. Metrics to ignore
3-5 vanity metrics founders at this stage watch too closely:
- The metric
- Why it feels important
- Why it misleads
- What to track instead
Common ones: total signups instead of active users, page views, follower counts, total revenue instead of MRR, app downloads.
### 4. Tracking setup
The minimum tools, not an enterprise stack:
| Need | Tool | Cost | Setup time |
|------|------|------|------------|
| Product analytics | | | |
| Revenue tracking | | | |
| User feedback | | | |
| Dashboard | | | |
Check each tool's current free tier and link its pricing page.
**Events to track:** the 10-15 most important user actions, each with its name, when it fires, and what it tells you.
### 5. Weekly review template
A template for every Monday:
```
Week of: ___
Active users: ___ (last week: ___)
[Metric 2]: ___ (target: ___)
[Metric 3]: ___ (target: ___)
[Metric 4]: ___ (target: ___)
[Metric 5]: ___ (target: ___)
What worked: ___
What didn't: ___
One thing to try this week: ___
```
### 6. Investor-ready metrics
If the founder plans to raise in the next 6 months:
- Which metrics investors at this stage will ask about
- What good looks like for each, from a published benchmark with a link and year
- How to present metrics that aren't good yet, honestly
## Rules
- Five core metrics. No more.
- Every metric has a specific target. "Improve retention" is not one.
- Free or cheap tools. No enterprise software for a 50-user startup.
- The weekly review takes under 15 minutes.
- Keep total output under 1500 words.
© emotixco · MIT · emotixco/claude-skills-founder
Similar skills
All skills for Data and databases →metrics-dashboard by other authors comes first.