dashboard-builder

dashboard-builder is a skill for Claude Code from reatlat/fullstory-claude-plugin. It costs 46 tokens per session (1,377 once invoked), scanned A, original, MIT.

A tool for creating saved dashboards of important measurements, such as users, revenue, or error counts, and checking them on a daily or weekly schedule.

In plain words
What is it for?
Use it to choose a main success metric, supporting KPIs, and quick health checks for product, engineering, or leadership reviews.
Why use it?
It avoids rebuilding the same metric report each time and gives you a consistent way to see whether a product is healthy and changing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the fullstory-claude-plugin plugin — 46 skills, 3 agents, 1 MCP server shipped together

Good fit Use it to choose a main success metric, supporting KPIs, and quick health checks for product, engineering, or leadership reviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reatlat/fullstory-claude-plugin/dashboard-builder
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add reatlat/fullstory-claude-plugin --skill dashboard-builder
Clone the repo
git clone --depth 1 https://github.com/reatlat/fullstory-claude-plugin

Made for: Claude Code.

Or install fullstory-claude-plugin, the plugin that ships this one along with the rest of its 46 skills, 3 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for dashboard-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/dashboard-builder/github.svg)](https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/dashboard-builder)
Your own site
<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/dashboard-builder"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/dashboard-builder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dashboard-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/dashboard-builder"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/dashboard-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,377 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01377
Opus 5 $0.00023 $0.00688
Sonnet 5 $0.00009 $0.00275
Haiku 4.5 $0.00005 $0.00138

Measured 11d ago against content hash 57eb2060e767, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

dashboard-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/dashboard-builder/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dashboard Builder

Set up recurring metric dashboards — define key metrics, save them for reuse, and generate daily or weekly snapshots.

When to Use

  • "Set up a product health dashboard"
  • "What metrics should I track weekly?"
  • "Create a KPI dashboard for the leadership team"
  • "I want to check the same metrics every Monday — automate it"
  • "What's our north star metric and supporting KPIs?"

Mental Model

A dashboard is a curated set of metrics you check regularly. It answers "how are we doing?" at a glance. Good dashboards have:

  1. North star metric: The one number that measures success (e.g., weekly active users, monthly revenue, tasks completed)
  2. Supporting KPIs: 3-5 metrics that explain the north star (e.g., conversion rate, retention, error rate)
  3. Health indicators: Quick sanity checks (traffic volume, error count, rage click count)
  4. Trend context: Week-over-week or month-over-month change

Workflow

Step 1: Interview the user

Ask what matters:

  • "What's the primary goal of your product? (revenue, engagement, retention, growth)"
  • "Who is this dashboard for? (PM, engineering lead, exec, yourself)"
  • "How often will you check it? (daily, weekly, monthly)"
  • "What would make you panic? (conversion drops 20%, errors spike, traffic crashes)"

Step 2: Design the dashboard

Based on the answers, propose a dashboard structure:

For a PM:

North star: Weekly active users
|— New user signups (trend)
|— Feature adoption rate (single_number)
|— User retention (Day 7, Day 30)
|— Top frustrations (from opportunities)
|— Conversion funnel (checkout or activation)
Health checks: error rate, page view volume

For an engineering lead:

North star: Error-free session rate
|— Top errors (by frequency)
|— API error rate (by endpoint)
|— Rage click count (trend)
|— Deploy frequency and success rate
|— Page load performance (slowest pages)
Health checks: traffic volume, session count

For an exec:

North star: Revenue or conversion
|— Conversion rate (trend)
|— Revenue impact of top UX issues
|— New vs returning user split
|— Feature adoption (key features)
|— CSAT proxy (frustration rate)
Health checks: traffic, session count, error rate

Read the full file on GitHub · 158 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 158 lines · 46 tokens per session scan A 57eb2060e767

Subscribe to this mod's changes

dashboard-builder is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 46 tokens to every session and 1,377 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.