dashboard

Solid

Comprehensive usage analytics and epistemic coverage dashboard across all sessions.

AI & Automation 125 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Dashboard Skill Analyze all Claude Code session data to produce a comprehensive usage analytics dashboard with epistemic protocol coverage metrics, friction analysis, growth timeline, and actionable improvement recommendations. ## When to Use Invoke this skill when: - A user wants to see overall epistemic protocol usage metrics across all sessions - Evaluating protocol coverage: which situations occurred vs. which protocols were used - Tracking usage growth, friction patterns, and satisfaction trends over time - After running `/onboard` for deeper, full-dataset analysis Skip when: - User wants protocol recommendations (use `/onboard` instead) - Quick single-protocol question (answer directly) - No session history exists ## Workflow Overview ``` COLLECT → AGGREGATE → ANALYZE → PRESENT ``` | Phase | Owner | Tool | Decision Point | |-------|-------|------|----------------| | 1. Collect | Main | Glob | Inventory + path decision | | 2. Aggregate | Subagent (coverage-scanner) | Bash, Read, Grep, Glob | Batch data collection | | 3. Analyze | Main | — | 7 computations | | 4. Present | Main | Write, Bash | HTML dashboard + console summary | ## Data Sources ### Primary: Usage Data Cache | Source | Method | Extracts | |--------|--------|----------| | `~/.claude/usage-data/facets/{session_id}.json` | Glob + Read | friction_counts, friction_detail, goal_categories, session_type, outcome, user_satisfaction_counts | | `~/.claude/usage-data/session-meta/{session_id}.json` | Glob ...

Details

Author
jongwony
Repository
jongwony/epistemic-protocols
Created
7 months ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

usage-analysis

Use when the user asks an interpretive question about their Claude Code token spend — what's interesting, what's anomalous, what to change. This skill produces insights and questions; it does NOT enumerate top consumers (the dashboard does that). Use `usage-dashboard` for "show me the numbers." Use `claude-audit` for "audit my config overlap." Use this skill for "tell me what's interesting / what should I change." Trigger phrases: "am I close to my Claude limit", "how much Sonnet am I using", "where are my Claude tokens going", "what's eating my Claude budget", "why is my Claude spend so high", "what should I change about my Claude setup".

1 Updated 1 weeks ago
glitchwerks
Data & Documents Listed

usage-dashboard

Use when the user explicitly asks to regenerate, rebuild, or refresh the `claude-prospector` token-usage dashboard with no interpretive question attached — runs `python -m claude_prospector dashboard`, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use `usage-analysis` instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-prospector dashboard", "refresh the token dashboard", "regen the prospector dashboard".

1 Updated 1 weeks ago
glitchwerks
Data & Documents Solid

report

Generate Growth Map (epistemic profile + insights integration) from session patterns and workflow data.

125 Updated today
jongwony