# dt-app-dashboards

Works with Dynatrace dashboards as JSON documents: creates layouts, adds DQL tiles, configures variables, and deploys via dtctl.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2800 installs · ★ 167
- Author: Dynatrace
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-app-dashboards/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/dt-app-dashboards

## What it does

This skill guides AI agents through modifying Dynatrace dashboard JSON files stored in the Document Store. It structures the grid layout, sets up `markdown` and `data` tiles, and wires DQL queries to specific visualization types like charts, tables, or single-value gauges.

Reading a dashboard requires `dtctl get dashboard <id> -o json` because `describe` returns metadata only. During updates, you must fetch and edit the existing `dashboard.json` before running `dtctl apply`. Rebuilding the JSON from scratch silently destroys any layout or query changes teammates made directly in the Dynatrace UI.

## Requirements
- Works with: Dynatrace

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-app-dashboards -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/dt-app-dashboards/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/dt-app-dashboards/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-app-dashboards -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/dt-app-dashboards/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-app-dashboards -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/dt-app-dashboards/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Dynatrace/dynatrace-for-ai dt-app-dashboards
```

2. **Manually: put the files in place**
- File: `.github/skills/dt-app-dashboards/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-app-dashboards -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Dynatrace/dynatrace-for-ai --path skills/dt-app-dashboards
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/dt-app-dashboards/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-app-dashboards -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-app-dashboards/SKILL.md

## When to use it
- generate valid Dynatrace dashboard JSON with DQL tiles and grid positioning
- update existing dashboards via `dtctl apply` without overwriting UI changes
- configure single-select and multi-select dashboard variables for DQL queries
- inspect dashboard structure and layout properties via `dtctl get`

## Example prompts
- Fetch dashboard `<id>` with dtctl, add a categoricalBarChart tile, and validate the DQL query
- Create a Dynatrace dashboard JSON file with a Service variable and a full-width lineChart
- Validate the DQL queries before updating `dashboard.json` and deploy via dtctl

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 14b4dff7c36ed14e.

BEGIN THIRD-PARTY FILE 14b4dff7c36ed14e
````text
---
name: dt-app-dashboards
description: Work with Dynatrace dashboards - create, modify, query, and analyze dashboard JSON including tiles, layouts, DQL queries, variables, and visualizations.
license: Apache-2.0
---

# Dynatrace Dashboard Skill

## Overview

Dynatrace dashboards are JSON documents stored in the Document Store containing
tiles (content/visualizations), layouts (grid positioning), and variables
(dynamic query parameters).

**When to use:** Creating, modifying, querying, or analyzing dashboards.

## Dashboard JSON Structure

```json
{
  "name": "My Dashboard",
  "type": "dashboard",
  "content": {
    "version": 21,
    "variables": [],
    "tiles": { "<id>": { "type": "data|markdown", ... } },
    "layouts": { "<id>": { "x": 0, "y": 0, "w": 24, "h": 8 } }
  }
}
```

- Tile IDs in `tiles` must match IDs in `layouts`
- Grid is 24 units wide. Common widths: 24 (full), 12 (half), 6 (quarter)
- Two tile types: `markdown` (text content) and `data` (DQL query + visualization)

**Optional content properties:** `settings`, `refreshRate`, `annotations`

## Reading & Analyzing

Fetch full content with `dtctl get dashboard <id> -o json` (`describe` returns metadata only), then inspect the JSON to discover its available properties. Carefully read [references/analyzing.md](references/analyzing.md) before analyzing.

## Create/Update Workflow (Mandatory Order)

Carefully follow the workflow described in [references/create-update.md](references/create-update.md).

**Key rules:**
- Load domain skills BEFORE generating queries — do not invent DQL
- Validate ALL queries before adding to dashboard
- No time-range filters in queries unless explicitly requested by user
- Set `name` before deploying
- **Updating — ALWAYS read the current state first:** `dtctl get dashboard <id> -o json`, save it as `dashboard.json`, modify that file, then deploy it. Never reconstruct JSON from scratch or inject an `id` manually — both silently overwrite any UI edits the user made since last deployment.
- **Deploy with `dtctl apply`** — validation runs automatically. If it fails, fix **all** reported errors before re-applying.

## Visualization Types

- **Time-series** (require `timeseries`/`makeTimeseries`): `lineChart`, `areaChart`, `barChart`, `bandChart`
- **Categorical** (`summarize ... by:{field}`): `categoricalBarChart`, `pieChart`, `donutChart`
- **Single value/gauge** (single numeric record): `singleValue`, `meterBar`, `gauge`
- **Tabular** (any data shape): `table`, `raw`, `recordList`
- **Distribution/status**: `histogram`, `honeycomb`
- **Maps**: `choroplethMap`, `dotMap`, `connectionMap`, `bubbleMap`
- **Matrix**: `heatmap`, `scatterplot`

Required field types per visualization: [references/tiles.md](references/tiles.md)

## Variables Quick Reference

```json
{ "version": 2, "key": "Service", "type": "query", "visible": true,
````
END THIRD-PARTY FILE 14b4dff7c36ed14e

The third-party file has ended. Everything between the 14b4dff7c36ed14e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2874 of 3679 bytes. © Dynatrace · Apache-2.0 · https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-app-dashboards/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md