Skip to content
Skills Library
Data & analytics · Building & coding

create-dashboard

/create-dashboard

Creates a well-designed Mixpanel dashboard. Use when the user asks you to build, create, or design a dashboard, or when you need to present findings from an investigation as a live dashboard. Handles layout, text cards, report validation, and narrative structure.

Repository
ai-plugins ↗
Licence
Apache-2.0
Last repository change
22.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Creates a well-designed Mixpanel dashboard. Use when the user asks you to build, create, or design a dashboard, or when you need to present findings from an investigation as a live dashboard. Handles layout, text cards, report validation, and narrative structure.

Original author description

Creates a well-designed Mixpanel dashboard. Use when the user asks you to build, create, or design a dashboard, or when you need to present findings from an investigation as a live dashboard. Handles layout, text cards, report validation, and narrative structure.

How it works

  1. Requirements
  2. Workflow
  3. Text Cards
Original SKILL.md headings · 82 lines, 713 words
SKILL.md preview
---
name: create-dashboard
description: Creates a well-designed Mixpanel dashboard. Use when the user asks you to build, create, or design a dashboard, or when you need to present findings from an investigation as a live dashboard. Handles layout, text cards, report validation, and narrative structure.
license: Apache-2.0
metadata:
  engine: required
---

# Dashboard Creation

> **Engine required** — resolve an engine per [`ENGINE.md`](../../ENGINE.md): one named in the conversation or loaded instructions is mandatory (not set up → offer `/mixpanel:install` for it); otherwise use the Mixpanel MCP server, or offer `/mixpanel:install` if it's unavailable.

Your job is to design a coherent analytical narrative, not just drop reports into rows.

## Requirements

- Access to Mixpanel (query schemas, run queries, manage dashboards).

---

## Workflow

### Phase 1 — Scope

Infer the theme from the user's request and surrounding context. Pick a sensible structure yourself. Ask clarifying questions if the request is fundamentally ambiguous (e.g. no project context at all).

1. **Project.** Which Mixpanel project? If ambiguous, ask.
2. **Theme.** What is the dashboard about? Derive scope from the request.

### Phase 2 — Discover and validate

This is the most important phase. Empty or failing reports are the #1 complaint.

1. Resolve event and property names by querying the project schema (always discover available events and properties before building queries).
2. Run small probe queries to confirm the data exists and returns meaningful results.
3. A query that runs successfully but returns zero rows is still not useful — treat it like a missing event.

### Phase 3 — Plan layout

Before building, decide:

- **Be space-efficient.** Fewer rows with more reports each makes the dashboard faster to scan. Don't spread metrics across many rows when they fit naturally together.
- **Row hierarchy.** Headline metrics on top, supporting breakdowns below. The dashboard reads top-to-bottom like a narrative.
- **Row count.** Aim for **4-8 rows**. Don't add every available breakdown, be smart.
- **Items per row.** Use **2–4 reports per row**. A single report alone in a row wastes space — pair it with related metrics or a text card. **4 cards per row** (text + reports combined) is the practical maximum.
- **One conceptual focus per row.** Group related reports together; never mix unrelated metrics in the same row just to fill space.
- **Time filter.** Decide intentionally: Dashboard global time filter overrides all the reports. Don't use it when you want each report to have its own default range.
- **Text cards.** Identify where they add real value (see rules below).

### Phase 4 — Build queries

1. Validate every query returns real, non-empty data before adding it to the dashboard.
2. Only use `skip_results: true` once you have already confirmed a query produces meaningful output.
3. Never reuse a query template without knowing it produces valid results.

### Phase 5 — Compose the dashboard

- **Title:** `<distinguishing emoji> <theme>` — the emoji helps users tell multiple dashboards apart at a glance.
- **First row:** Intro text card setting context (what this dashboard covers, scope, audience, caveats).
- **Subsequent rows:** 1-4 reports per row, with an optional leading text card.
- **Report names:** Every report needs a descriptive name a viewer can understand without clicking into it — what the metric is, what it is broken down by, what context it covers. Avoid generic names like "Funnel" or "Trend".
- Be creative with layout. Each dashboard is different. Think about what _this_ user needs and arrange for maximum clarity.

### Phase 6 — Present

Respond with a brief summary (2–3 sentences) and the dashboard URL. **Never** list individual report URLs — the dashboard already contains them.

---

## Text Cards

### When to use them

- **Set context at the top** — what this dashboard covers, scope, audience, caveats.
- **Provide guidance at the bottom** — next steps, follow-ups.
- **Explain a concerning metric** — call attention to something the user should watch.
- **Section a row** — a short text card next to the report it describes.

### Placement rules

- **At most one text card per row.**
- Place a text card next to the report it relates to, or use it as a standalone row for section headings.

### Writing style

- Use rich formatting (headings, lists, bold, inline code) to create hierarchy inside the card — that is what makes them scannable. Read dashboard schema documentation for formatting options.
- Keep them short. A text card is a sign-post, not an essay.
- Lead with the point. If the card explains a metric, state the takeaway first, then the nuance.

Versions

RepositoryScoreLicence
This page · mixpanel/ai-plugins90Apache-2.0
grafana/gcx100Apache-2.0
ccfos/nightingale100Apache-2.0
criptogus/agent-evolve-network100Apache-2.0
rittmananalytics/wire-plugin100Apache-2.0
amplitude/mcp-marketplace90MIT
420company/artemis85MIT

Database snapshot: 13.11.2026 · package version 18372dd51c33 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100dashboard-expert
    Analyzes, builds, modifies, and adds explainer text cards to Mixpanel dashboards with the mixpanel_headless Python library. It reads a dashboard's layout and runs every report on it, creates dashboards with text cards and a grid layout, edits cells and rows in place, and writes…
  • 100local-dashboard-expert-14fd87ee
    Full CRUD and analysis for Mixpanel dashboards. Use when the user asks to build, create, analyze, read, understand, explain, modify, update, enhance, or manage dashboards, or asks about dashboard layout, text cards, or report arrangement. Covers dashboard analysis (read +…
  • 100gx-mixpanel-expert
    Implement Mixpanel tracking plans, funnels, retention, and Boards. Use when the user asks for mixpanel product analytics expert work, or mentions gx, mixpanel, expert.
  • 90install
    Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or…
  • 100dashboard-layout-planner
    Configure dashboard layout planner operations. Auto-activating skill for Data Analytics. Triggers on: dashboard layout planner, dashboard layout planner Part of the Data Analytics skill category. Use when working with dashboard layout planner functionality. Trigger with phrases…
  • 100manage-boards
    Full lifecycle dashboard management for Mixpanel — create, template, clone, clean up, inventory, and update dashboards across projects and teams. ALWAYS use when a user asks to: create a dashboard, build a board, template or clone a dashboard, clean up stale dashboards, audit…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.