Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jmsktm avatar

Kpi Dashboard Builder

  • 215 installs
  • 8 repo stars
  • Updated January 22, 2026
  • jmsktm/claude-settings

Define KPIs, design dashboard layouts, specify metrics queries, and structure reporting views that track revenue, retention, conversion, and operational health for teams.

About

KPI dashboard builder skill guides Claude to define meaningful metrics, design dashboard structures, specify data queries, and assemble reporting views that surface revenue, retention, conversion, and operational performance.

  • KPI definition frameworks
  • Dashboard layout design
  • Metric query specification
  • Retention and funnel tracking
  • Executive reporting views

Kpi Dashboard Builder by the numbers

  • 215 all-time installs (skills.sh)
  • Ranked #636 of 2,064 Data Science & ML skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jmsktm/claude-settings --skill kpi-dashboard-builder

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs215
repo stars8
Last updatedJanuary 22, 2026
Repositoryjmsktm/claude-settings

What it does

Define KPIs, design dashboard layouts, specify metrics queries, and structure reporting views that track revenue, retention, conversion, and operational health for teams.

Files

SKILL.mdMarkdownGitHub ↗

/verify - Unified Verification Skill

A comprehensive verification skill that chains static analysis, tests, and visual verification. Inspired by Boris Cherny's "verify-app" subagent pattern.

Trigger

  • /verify - Run full verification suite
  • /verify quick - Static analysis only
  • /verify visual - Browser-based visual verification
  • /verify [component] - Verify specific component/feature

Philosophy

"The most important thing to get great results out of Claude Code -- give Claude a way to verify its work."
— Boris Cherny, Creator of Claude Code

This skill provides that verification loop. It should be run: 1. After completing a feature 2. Before creating a PR 3. After merging from main 4. When debugging issues

Verification Layers

┌─────────────────────────────────────┐
│  Layer 1: Static Analysis           │
│  - TypeScript compilation           │
│  - ESLint/Biome linting             │
│  - Prettier formatting check        │
├─────────────────────────────────────┤
│  Layer 2: Unit Tests                │
│  - Jest/Vitest unit tests           │
│  - Component tests                  │
│  - Utility function tests           │
├─────────────────────────────────────┤
│  Layer 3: Integration Tests         │
│  - API route tests                  │
│  - Database integration             │
│  - Service layer tests              │
├─────────────────────────────────────┤
│  Layer 4: E2E Tests                 │
│  - Playwright browser tests         │
│  - Critical user flows              │
│  - Cross-browser verification       │
├─────────────────────────────────────┤
│  Layer 5: Visual Verification       │
│  - Live browser inspection          │
│  - Screenshot comparison            │
│  - Console error detection          │
│  - Network request validation       │
├─────────────────────────────────────┤
│  Layer 6: Build Verification        │
│  - Production build succeeds        │
│  - Bundle size check                │
│  - No build warnings                │
└─────────────────────────────────────┘

Execution Protocol

Full Verification (/verify)

1. STATIC ANALYSIS
   ├── Run: npm run type-check || npx tsc --noEmit
   ├── Run: npm run lint
   └── GATE: Must pass before continuing

2. UNIT TESTS
   ├── Run: npm test
   ├── Collect: Coverage report
   └── GATE: Must pass before continuing

3. E2E TESTS (if playwright.config exists)
   ├── Run: npx playwright test
   └── GATE: Must pass before continuing

4. VISUAL VERIFICATION (using Playwright MCP)
   ├── Start dev server if not running
   ├── Navigate to key pages
   ├── Take screenshots
   ├── Check console for errors
   ├── Verify no network failures
   └── GATE: No critical issues

5. BUILD
   ├── Run: npm run build
   └── GATE: Must succeed

6. REPORT
   └── Summary of all layers

Quick Mode (/verify quick)

Only runs Layer 1 (Static Analysis).

Visual Mode (/verify visual)

Only runs Layer 5 (Visual Verification) using Playwright MCP.

Playwright MCP Integration

For visual verification, use these MCP tools:

// 1. Start by checking if dev server is running
mcp__playwright-server__browser_navigate({ url: "http://localhost:3000" })

// 2. Capture page state
mcp__playwright-server__browser_snapshot()

// 3. Check for console errors
mcp__playwright-server__browser_console_messages({ level: "error" })

// 4. Take screenshot for visual record
mcp__playwright-server__browser_take_screenshot({ filename: "verify-{timestamp}.png" })

// 5. Check network requests
mcp__playwright-server__browser_network_requests()

// 6. Navigate to key routes and repeat

Key Pages to Verify

For Next.js apps, automatically check:

  • / - Homepage
  • /login or /auth - Authentication (if exists)
  • Key feature pages based on recent changes

Error Classification

SeverityAction
CRITICALStop verification, report immediately
ERRORLog and continue, fail at end
WARNINGLog and continue, pass with warnings
INFOLog for reference

Output Format

╔══════════════════════════════════════════════════════════╗
║                   VERIFICATION REPORT                     ║
╠══════════════════════════════════════════════════════════╣
║ Layer 1 - Static Analysis     ✅ PASS                    ║
║   TypeScript: 0 errors                                    ║
║   ESLint: 0 errors, 2 warnings                           ║
╠══════════════════════════════════════════════════════════╣
║ Layer 2 - Unit Tests          ✅ PASS                    ║
║   42 tests passed                                         ║
║   Coverage: 78%                                           ║
╠══════════════════════════════════════════════════════════╣
║ Layer 3 - E2E Tests           ✅ PASS                    ║
║   12 specs passed                                         ║
╠══════════════════════════════════════════════════════════╣
║ Layer 4 - Visual Verification ✅ PASS                    ║
║   3 pages checked                                         ║
║   0 console errors                                        ║
║   Screenshots: verify-20240102-143022.png                ║
╠══════════════════════════════════════════════════════════╣
║ Layer 5 - Build               ✅ PASS                    ║
║   Build time: 12.3s                                       ║
╠══════════════════════════════════════════════════════════╣
║                                                           ║
║ OVERALL: ✅ VERIFICATION PASSED                          ║
║                                                           ║
╚══════════════════════════════════════════════════════════╝

Integration with Other Skills

This skill works with:

  • /commit-push-pr - Run verify before creating PR
  • /test-verify - Subset focused on testing
  • code-reviewer subagent - Code quality checks

Automation Hook

Can be triggered automatically via Stop hook for long-running tasks:

# ~/.claude/hooks/stop/verify-on-complete.sh
# Runs /verify when Claude finishes a significant task

Related skills

Data Science & MLanalyticsdatabases

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.