create-dashboard

create-dashboard is a skill for Claude Code from amplitude/mcp-marketplace. It costs 40 tokens per session (844 once invoked), scanned A, original, MIT.

A guide for building organized Amplitude dashboards, which are collections of charts used to review product or business information.

In plain words
What is it for?
Use it to create reporting dashboards, arrange existing charts, fill measurement gaps, and prepare views for regular reviews.
Why use it?
It brings related charts together so a team can monitor a goal or initiative in one place.

Skill for Claude Code

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

Part of the amplitude plugin — 37 skills shipped together

Good fit Use it to create reporting dashboards, arrange existing charts, fill measurement gaps, and prepare views for regular reviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amplitude/mcp-marketplace/create-dashboard
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 amplitude/mcp-marketplace --skill create-dashboard
Clone the repo
git clone --depth 1 https://github.com/amplitude/mcp-marketplace

Made for: Claude Code.

Or install amplitude, the plugin that ships this one along with the rest of its 37 skills.

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 create-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/create-dashboard/github.svg)](https://agentmods.dev/skills/amplitude/mcp-marketplace/create-dashboard)
Your own site
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/create-dashboard"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/create-dashboard/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 create-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/create-dashboard"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/create-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 844 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.00040 $0.00844
Opus 5 $0.00020 $0.00422
Sonnet 5 $0.00008 $0.00169
Haiku 4.5 $0.00004 $0.00084

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

Security

Grade A, and why

create-dashboard 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 5d 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.

plugins/amplitude/skills/create-dashboard/SKILL.md · 111 lines

How it starts

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

Create Dashboard

Create new team or initiative dashboards, organize scattered charts, build executive reporting, or set up review cadence dashboards.

Instructions

Step 0: Discovery (if unfamiliar with the feature)

Before building, understand what you're tracking:

  • Search for existing dashboards/charts related to the topic
  • Inspect the connected catalog and use its taxonomy search/read capabilities to find relevant events and segmentation properties; never guess names or scopes
  • Ask user for clarification on primary goals, key segments, or time horizons

Step 1: Define Dashboard Purpose

Clarify:

  • Who is the audience?
  • What decisions will it inform?
  • How frequently will it be reviewed?
  • What's the narrative structure?

Step 2: Gather or Create Charts

If existing charts found (>5 relevant):

  • Use Amplitude:search_amp_entities to find relevant existing charts
  • Use Amplitude:get_amplitude_charts with include: "definition" to retrieve their definitions
  • Identify gaps that need new charts

If few/no charts exist (<5 relevant):

  • Switch to "greenfield build" mode
  • Use Amplitude:query_amplitude_data to create needed charts
  • Keep the returned chart edit IDs; use_amp_dashboards promotes them when creating the dashboard
  • Consider searching for relevant events first with entityTypes: ["EVENT", "CUSTOM_EVENT"]

Creating new charts:

  • Prototype with query_amplitude_data to verify data
  • Collect the returned chart edit IDs before creating the dashboard

Step 3: Plan the Layout

Organize into logical sections:

  1. Summary Row: Key metrics at a glance (headline view)
  2. Trend Section: How things are changing
  3. Breakdown Section: Segments and dimensions
  4. Detail Section: Supporting analyses

Step 4: Create the Dashboard

Use Amplitude:use_amp_dashboards with action: "create" and:

  • Clear, descriptive name
  • Rows with appropriate heights (375, 500, 625, or 750px)
  • Charts sized appropriately (3-12 columns)
  • Rich text headers for sections
  • Chart display configurations in chartMetas:
    • metric_only: Headline KPIs (single number)
    • series: Trend lines (default view)
    • converted: Funnels (conversion view)
    • table: Data tables

Read the full file on GitHub · 111 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. 5d ago Changed 5b244a4f8132
  2. 11d ago First seen · 111 lines · 40 tokens per session scan A 5027e32ef73d

Subscribe to this mod's changes

create-dashboard is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 844 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens