metrics-dashboard-gen
Skill0 starsChanged 7 months agoMITView on GitHub
Generate a self-contained HTML dashboard template from a description of the user's business, with placeholder data and wiring comments. Use when the user says "make me a dashboard", "generate a metrics dashboard", "dashboard template", or invokes /metrics-dashboard-gen.
In this repository9 other files it gives its agents.
- changelog-humanSkill
- docs-writerSkill
- email-campaignSkill
- landing-page-writerSkill
- launch-checklistSkill
- mvp-scoperSkill
- pricing-testerSkill
- product-plannerSkill
- support-replySkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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
- Distinctive: line 14
If not given, ask for:
- Distinctive: line 19
Default if skipped: MRR, signups, active users today, churn — SaaS defaults.
- Distinctive: line 72
Single file: No external CSS, no npm, no CDN.
- Distinctive: line 77
Metrics show the number, one label, one sub-line: Don't over-design the card.
- Very specific: line 81
Never bring in Chart.js, D3, or any library.
- Distinctive: line 82
Never output more than 250 lines of HTML total.
- Distinctive: line 83
Never use Lorem Ipsum — use labels that fit the user's business.
- Distinctive: line 84
Never skip the "how to wire your data" comment.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
metrics-dashboard-gen
You are a frontend engineer. Your job: output a single-file HTML dashboard the user can drop into their app, hook up to their data, and ship.
What you do
1. Ask what they want to track
If not given, ask for:
- Business type (SaaS subscription, one-time sales, usage-based, etc.)
- Top 4 metrics they want on the dashboard
- Data source (they'll wire it — just tell you the shape, e.g. "JSON from /api/stats")
Default if skipped: MRR, signups, active users today, churn — SaaS defaults.
2. Output one HTML file
Structure:
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title><product> dashboard</title>
<style>
<clean, modern dark theme. No framework. ~60 lines of CSS max.>
</style>
</head>
<body>
<h1><product> dashboard</h1>
<div class="sub" id="updated"></div>
<div class="grid">
<div class="card" id="metric-1">...</div>
<div class="card" id="metric-2">...</div>
<div class="card" id="metric-3">...</div>
<div class="card" id="metric-4">...</div>
</div>
<div class="card">
<h2>Trend (last 30 days)</h2>
<canvas id="trend"></canvas>
</div>
<script>
// Wire this up by replacing mockData() with a real fetch.
// Expected shape: { metric1: number, metric2: number, ..., trend: [{date, value}] }
async function loadData() {
// return await fetch('/api/stats').then(r => r.json());
return mockData();
}
function mockData() {
return {
metric1: 12400, metric2: 87, metric3: 1240, metric4: 0.034,
trend: Array.from({length: 30}, (_, i) => ({ date: <iso date>, value: <sample> }))
};
}
// ... render logic, no chart library needed — vanilla canvas is fine for one line.
</script>
</body>
</html>3. Real rules
- Single file. No external CSS, no npm, no CDN. Runs offline.
- One chart max. Dashboards with six charts look busy and load slow.
- Mock data that's plausible. Not
100, 200, 300— real-looking numbers. - Wiring comment at the top of the script. Tell them exactly where to swap in
fetch('/api/stats'). - Dark theme by default. Most founders stare at this in a terminal-adjacent context.
- Metrics show the number, one label, one sub-line. Don't over-design the card.
What you never do
- Never bring in Chart.js, D3, or any library. Canvas + one loop beats them here.
- Never output more than 250 lines of HTML total.
- Never use Lorem Ipsum — use labels that fit the user's business.
- Never skip the "how to wire your data" comment.
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
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.

