agentleFS
Sign inStart free
emotixcoemotixco/claude-skills-founder/skills/metrics-dashboard/SKILL.md

metrics-dashboard

Skill796 starsChanged 40 days agoMITView on GitHub

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.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use strategy-red-team.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

    line 14
  2. Distinctive:

    Check each tool's current free tier and link its pricing page.

    line 63
  3. Distinctive:

    If the founder plans to raise in the next 6 months:

    line 86
  4. Distinctive:

    Every metric has a specific target.

    line 94
  5. Distinctive:

    Keep total output under 1500 words.

    line 97

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

StageFocusKey metrics
Pre-launchValidationWaitlist signups, interview conversion, survey responses
Post-launch (0-100 users)EngagementActivation rate, D1/D7 retention, core action completion
Growth (100-1000 users)Retention and revenueMRR, churn, NPS, CAC, feature adoption
Scale (1000+ users)Efficiency and expansionLTV/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:

NeedToolCostSetup 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free