Agent skill

Dashboarding

by Kilo-Org in Kilo-Org/kilo-marketplace

Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting.

Apache-2.0Auto-check passedDevOps & Cloud

Install Dashboarding

skills CLI
$ npx skills add Kilo-Org/kilo-marketplace --skill dashboarding -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Kilo-Org/kilo-marketplace dashboarding --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Kilo-Org/kilo-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dashboarding .claude/skills/dashboarding && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dashboarding
GitHub stars
189
Token cost
~2.4k tokens
SKILL.md length
391 words
Files
2
Skills in repo
87
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting.

  • The user asks to create a Grafana dashboard
  • SKILL.md covers Dashboard JSON structure, Panel types and when to use them, Panel JSON structure and Useful unit identifiers, plus 7 more sections
  • Calls curl and jq; needs API_KEY
  • Configure a time series

What it does

Dashboarding is an agent skill from Kilo-Org/kilo-marketplace. Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting. Use when the user asks to create a Grafana dashboard, add a panel, configure a time series or stat panel, add template variables, set up dashboard linking, use transformations, configure thresholds, build a dashboard for a service, or export dashboard JSON. Triggers on phrases like "create dashboard", "add panel", "time series panel", "Grafana dashboard JSON", "template variables", "dashboard variable"…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in DevOps & Cloud, covering Monitoring and alerting and Forecasting and time series. It works with Grafana. The repository describes itself as: Kilo Marketplace - A curated collection of Skills, MCP Servers, and Modes for enhancing AI agent capabilities across the Kilo ecosystem—including Kilo Code (VS Code extension)… The licence is Apache-2.0.

When your agent uses it

  • The user asks to create a Grafana dashboard
  • Configure a time series
  • Add template variables
  • Set up dashboard linking

Example prompts

  • “create dashboard”
  • “add panel”
  • “time series panel”
  • “/dashboarding”

Requirements

  • A credential in API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit ff51758. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • grafana.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dashboarding loads about 2.4k tokens when it runs. Until then it costs about 160 tokens; SKILL.md has 391 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~160
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Kilo-Org/kilo-marketplace at commit ff51758, republished under its Apache-2.0 licence (© Kilo-Org). 391 words, ~2,409 tokens.

Download SKILL.mdSave it as .claude/skills/dashboarding/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dashboarding
description
Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting. Use when the user asks to create a Grafana dashboard, add a panel, configure a time series or stat panel, add template variables, set up dashboard linking, use transformations, configure thresholds, build a dashboard for a service, or export dashboard JSON. Triggers on phrases like "create dashboard", "add panel", "time series panel", "Grafana dashboard JSON", "template variables", "dashboard variable", "panel transformation", "threshold", "stat panel", "table panel", "Grafana annotations", or "dashboard folder".
metadata.category
observability

Grafana Dashboard Authoring

Dashboards are JSON documents stored in Grafana. Every dashboard has panels, variables, time range, and refresh settings. Understanding the JSON schema lets you programmatically create and modify dashboards via the API or Grafana Assistant tools.


Dashboard JSON structure

json
{
  "title": "My Dashboard",
  "uid": "my-dashboard-v1",
  "tags": ["service", "production"],
  "time": { "from": "now-1h", "to": "now" },
  "refresh": "30s",
  "timezone": "browser",
  "schemaVersion": 41,
  "templating": { "list": [] },
  "annotations": { "list": [] },
  "panels": []
}

Key fields:

  • uid - stable identifier used in URLs and API calls; keep it short and meaningful
  • schemaVersion - use 41 for Grafana 11+
  • time.from / to - supports relative (now-1h, now-7d) and absolute ISO timestamps
  • refresh - auto-refresh interval ("30s", "1m", "5m", "" for off)

Panel types and when to use them

PanelUse case
Time seriesAny metric over time; the default choice for counters, rates, gauges
StatSingle current value with optional sparkline (e.g. uptime, current RPS)
GaugePercent or value against a min/max (e.g. disk usage %)
Bar gaugeCompare multiple values side by side (e.g. top 10 services by RPS)
TableMulti-column data (e.g. alert list with labels)
HeatmapDistribution over time (e.g. request duration histogram)
LogsLoki log streams
TracesTempo trace search
TextMarkdown documentation panels
CandlestickOHLC/financial data (or min/max/avg patterns)
Node graphService dependency graphs

Panel JSON structure

json
{
  "id": 1,
  "type": "timeseries",
  "title": "Request Rate",
  "gridPos": { "x": 0, "y": 0, "w": 12, "h": 8 },
  "datasource": { "type": "prometheus", "uid": "${datasource}" },
  "targets": [
    {
      "expr": "sum(rate(http_requests_total{job=\"$job\"}[5m])) by (status_code)",
      "legendFormat": "{{status_code}}",
      "refId": "A"
    }
  ],
  "fieldConfig": {
    "defaults": {
      "unit": "reqps",
      "thresholds": {
        "mode": "absolute",
        "steps": [
          { "color": "green", "value": null },
          { "color": "yellow", "value": 1000 },
          { "color": "red", "value": 5000 }
        ]
      }
    },
    "overrides": []
  },
  "options": {
    "legend": { "calcs": ["mean", "max", "last"], "displayMode": "table", "placement": "bottom" },
    "tooltip": { "mode": "multi", "sort": "desc" }
  }
}

gridPos: The dashboard uses a 24-column grid. Common widths: full-width=24, half=12, third=8, quarter=6. Height in grid units (1 unit ≈ 30px).


Useful unit identifiers

# Rates
"reqps"      -- requests per second
"ops"        -- operations per second
"Bps"        -- bytes per second
"percentunit" -- 0.0-1.0 as percentage

# Storage
"bytes"      -- bytes (auto-scales to KB/MB/GB)
"decbytes"   -- decimal bytes (1 KB = 1000 B)

# Time
"ms"         -- milliseconds
"s"          -- seconds
"dtdurationms" -- duration in ms (shows as "1h 2m 3s")

# Counts
"short"      -- compact number (1.2k, 3.4M)
"none"       -- raw number

Full list: Panel > Field > Unit dropdown in Grafana UI, or the units reference.


Show full SKILL.md (174 more words)Show less

Template variables

Variables make dashboards reusable across environments and services.

Query variable (populates from metric labels):

json
{
  "name": "job",
  "type": "query",
  "datasource": { "type": "prometheus", "uid": "prometheus" },
  "query": { "query": "label_values(up, job)", "refId": "A" },
  "refresh": 2,
  "includeAll": true,
  "multi": true,
  "label": "Service"
}

Constant variable:

json
{
  "name": "cluster",
  "type": "constant",
  "query": "production",
  "label": "Cluster"
}

Datasource variable (switch data sources without editing queries):

json
{
  "name": "datasource",
  "type": "datasource",
  "pluginId": "prometheus",
  "includeAll": false,
  "label": "Prometheus"
}

Use variables in queries:

promql
# Reference a variable in a PromQL query
rate(http_requests_total{job=~"$job"}[5m])

# Multi-value variable uses regex OR automatically
# When $job = ["api", "worker"], it becomes job=~"api|worker"

Chain variables (second variable filters based on first):

json
{
  "name": "pod",
  "query": "label_values(kube_pod_info{namespace=\"$namespace\"}, pod)"
}

Transformations

Transformations run client-side after data is fetched, reshaping results without changing queries.

Common transformations:

json
"transformations": [
  {
    "id": "merge",
    "options": {}
  },
  {
    "id": "organize",
    "options": {
      "renameByName": { "Value #A": "Request Rate", "Value #B": "Error Rate" },
      "excludeByName": { "Time": true }
    }
  },
  {
    "id": "calculateField",
    "options": {
      "alias": "Error %",
      "mode": "reduceRow",
      "reduce": { "reducer": "last" },
      "binary": {
        "left": "errors",
        "right": "total",
        "operator": "/"
      }
    }
  },
  {
    "id": "filterByValue",
    "options": {
      "filters": [{ "fieldName": "Error %", "config": { "id": "greater", "options": { "value": 0.01 } } }],
      "type": "include",
      "match": "any"
    }
  }
]

Key transformation IDs: merge, organize, rename, calculateField, filterByValue, groupBy, sortBy, limit, labelsToFields, seriesToRows, partitionByValues.


Dashboard linking

Panel link (click a panel to go somewhere):

json
"links": [
  {
    "title": "Go to details",
    "url": "/d/details-dashboard?var-service=${__field.labels.service}",
    "targetBlank": false
  }
]

Dashboard link (top-right corner links):

json
"links": [
  {
    "title": "Runbook",
    "url": "https://wiki.example.com/runbook/${job}",
    "icon": "external link",
    "targetBlank": true,
    "type": "link"
  }
]

Built-in variables for links:

  • ${__value.raw} - current data point value
  • ${__field.labels.job} - label value from current series
  • ${__url.params} - current URL query parameters (pass-through)
  • ${__from} / ${__to} - current time range as Unix ms

Annotations

Show events overlaid on time series panels (deployments, incidents, etc.).

Query annotation from Loki:

json
{
  "datasource": { "type": "loki", "uid": "loki" },
  "expr": "{job=\"deployments\"} |= \"deployed\"",
  "name": "Deployments",
  "iconColor": "blue",
  "titleFormat": "{{service}} deployed",
  "textFormat": "{{version}} by {{author}}"
}

Query annotation from Prometheus:

json
{
  "datasource": { "type": "prometheus", "uid": "prometheus" },
  "expr": "changes(kube_deployment_status_observed_generation{namespace=\"production\"}[5m]) > 0",
  "step": "60s",
  "name": "Deployments",
  "iconColor": "blue",
  "titleFormat": "Deploy: {{deployment}}"
}

Dashboard via API

bash
# Create or update a dashboard
curl -s -X POST \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  "https://myorg.grafana.net/api/dashboards/db" \
  -d '{
    "dashboard": { <dashboard JSON> },
    "folderUid": "my-folder",
    "overwrite": true,
    "message": "Updated via API"
  }'

# Get a dashboard by UID
curl -s -H "Authorization: Bearer <API_KEY>" \
  "https://myorg.grafana.net/api/dashboards/uid/my-dashboard-v1" | jq '.dashboard'

# Search dashboards
curl -s -H "Authorization: Bearer <API_KEY>" \
  "https://myorg.grafana.net/api/search?query=kubernetes&type=dash-db" | \
  jq '.[] | {uid, title, folderTitle}'

# Create a folder
curl -s -X POST \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  "https://myorg.grafana.net/api/folders" \
  -d '{"uid": "platform-team", "title": "Platform Team"}'

Grafana scenes (app plugins)

For dashboards embedded in app plugins, use @grafana/scenes instead of raw JSON. See the grafana-o11y:grafana-scenes skill for the React-based scenes API.


References

© Kilo-Org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/dashboarding of Kilo-Org/kilo-marketplace.

  • SKILL.md
  • LICENSE

Open the folder on GitHubat commit ff51758

Compare with similar skills

Dashboarding next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dashboarding compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dashboarding this skillKilo-Org/kilo-marketplace189—~2.4kAutomated safety check: PassApache-2.0
ML AIgrafana/skills278—~1.3kAutomated safety check: PassApache-2.0
K6 Trend Analysisgrafana/skills278—~4.8kAutomated safety check: PassApache-2.0
Promql CLIsamber/cc-skills228—~1.9kAutomated safety check: PassMIT
Timeseries DBFerroxLabs/wayland608—~4.1kAutomated safety check: PassApache-2.0
Magic MouthHmbown/Wizards-of-the-Ghosts109—~836Automated safety check: PassCC0-1.0

Similar skills

  • ML AI

    grafana/skills

    Official

    Turn on AI + ML features in Grafana Cloud — Grafana Assistant (NL → PromQL/LogQL/TraceQL, dashboard build, incident investigation, MCP integration), Dynamic Alerting (Prophet forecasting + DBSCAN…

    278 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • K6 Trend Analysis

    grafana/skills

    Official

    Analyze Grafana Cloud k6 test run trends over time. An agent skill from grafana/skills.

    278 GitHub stars~4.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Promql CLI

    samber/cc-skills

    CLI for querying Prometheus and PromQL-compatible engines (Thanos, Cortex, VictoriaMetrics, Grafana Mimir, Grafana Tempo...) — instant queries, range queries, metric discovery (metrics/labels/meta…

    228 GitHub stars~1.9k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • Timeseries DB

    FerroxLabs/wayland

    Time-series database design and operations covering InfluxDB, TimescaleDB, and QuestDB patterns, data retention policies, continuous aggregates, downsampling strategies, compression techniques…

    608 GitHub stars~4.1k tokensUpdated yesterday
    DatabasesAuto-check passed
  • Magic Mouth

    Hmbown/Wizards-of-the-Ghosts

    Magic Mouth is trigger → message. An agent skill from Hmbown/Wizards-of-the-Ghosts.

    109 GitHub stars~836 tokensUpdated 6 mo ago
    Backend & APIsAuto-check passed
  • Axiom Dashboard Builder

    openclaw/clawhub

    Designs and deploys Axiom dashboards through the API, choosing chart types and writing APL or metrics queries, with templates and migration notes for Splunk and Grafana.

    9.5k GitHub stars~4.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from Kilo-Org/kilo-marketplace

All 87 skills in this repo
  • AzureML Project Scaffolding

    Kilo-Org/kilo-marketplace

    Sets up and maintains AzureML-ready Python projects as uv workspaces with devcontainers, a Makefile and job YAML, so local runs match cloud jobs and experiments stay reproducible.

    189 GitHub stars~3.1k tokensUpdated 9 days ago
    Auto-check: notes
  • Jupyter Notebook Builder

    Kilo-Org/kilo-marketplace

    Creates, inspects, edits and runs Jupyter notebooks, scaffolding experiment or tutorial notebooks from templates and preferring a Jupyter MCP server over raw JSON edits.

    189 GitHub stars~1.3k tokensUpdated 9 days ago
    Auto-check passed
  • Tableau Dashboard Creator

    Kilo-Org/kilo-marketplace

    Takes a plain-language dashboard request through brand setup, data exploration, planning, an interactive HTML mock and a Tableau implementation spec.

    189 GitHub stars~3.8k tokensUpdated 9 days ago
    Auto-check: notes
  • Elasticsearch File Ingest

    Kilo-Org/kilo-marketplace

    Ingest and transform data files (CSV/JSON/Parquet/Arrow IPC) into Elasticsearch with stream processing and custom transforms.

    189 GitHub stars~2.8k tokensUpdated 9 days ago
    Auto-check passed
  • Nifi Flow Layout

    Kilo-Org/kilo-marketplace

    A skill your agent uses when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.

    189 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check passed
  • Splunk Ingest Processor Setup

    Kilo-Org/kilo-marketplace

    Render Cisco Data Fabric ingest-time routing workflows and Splunk Cloud Platform Ingest Processor setup plans with SPL2 pipelines, source types, destinations, lifecycle handoffs, queue and…

    189 GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed

Works with

Questions about Dashboarding

What does Dashboarding do?

Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting. Dashboarding is an agent skill from Kilo-Org/kilo-marketplace. Create, modify, and organise Grafana dashboards including panels, variables, transformations, and alerting.

When should I use Dashboarding?

Dashboarding fits situations like: the user asks to create a Grafana dashboard; configure a time series; add template variables; set up dashboard linking.

How do I install Dashboarding in Claude Code?

Run `npx skills add Kilo-Org/kilo-marketplace --skill dashboarding -a claude-code`. Or copy the skill folder (skills/dashboarding in Kilo-Org/kilo-marketplace) into .claude/skills/dashboarding in your project. Claude Code loads it when a task matches its description.

How do I install Dashboarding in Codex?

Run `npx skills add Kilo-Org/kilo-marketplace --skill dashboarding -a codex`. Or copy the skill folder (skills/dashboarding in Kilo-Org/kilo-marketplace) into .agents/skills/dashboarding in your project. Codex loads it when a task matches its description.

Can I use Dashboarding in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Kilo-Org/kilo-marketplace --skill dashboarding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dashboarding, .gemini/skills/dashboarding, .github/skills/dashboarding and .opencode/skills/dashboarding in your project.

What does Dashboarding need to run?

Going by SKILL.md and its folder, Dashboarding needs the command-line tools its instructions call (curl and jq) and credentials named API_KEY. Our summary lists: A credential in API_KEY.

Does Dashboarding access the network?

SKILL.md names 1 domain. As links in the text: grafana.com. This is read from the text; nothing was executed.

Is Dashboarding safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dashboarding use?

Dashboarding is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dashboarding use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dashboarding?

Skills that share tags, products or a category with Dashboarding: ML AI (grafana/skills, 278 stars), K6 Trend Analysis (grafana/skills, 278 stars), Promql CLI (samber/cc-skills, 228 stars) and Timeseries DB (FerroxLabs/wayland, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dashboarding?

Kilo-Org (a GitHub organization) maintains it in Kilo-Org/kilo-marketplace, which has 189 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on September 28, 2026.

Source: Kilo-Org/kilo-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.