CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-app-dashboards

Work with Dynatrace dashboards - create, modify, query, and analyze dashboard JSON including tiles, layouts, DQL queries, variables, and visualizations.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dt-app-dashboards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured overview: lean, actionable, with explicit validation in the deploy workflow and excellent one-level-deep progressive disclosure via a references table. The main gaps are minor verbosity in the visualization-type enumeration and delegation of error-recovery detail to a reference.

Suggestions

Trim the inline visualization-subtype enumeration (maps, matrix, distribution/status) and defer it to tiles.md to tighten conciseness.

Add a brief inline feedback loop for the create/update workflow (e.g. what to do when `dtctl apply` validation fails) so the body is self-contained for the common failure case.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding about what dashboards/DQL are; not 5 because the long enumeration of visualization subtypes (maps, matrix, distribution) partly duplicates detail that belongs in tiles.md and could be trimmed.

4 / 5

Actionability

Provides concrete executable commands ("dtctl get dashboard <id> -o json --plain", "dtctl apply") and concrete JSON examples with specific rules; not 5 because the full create/update procedure is delegated to the reference rather than given as copy-paste-ready steps inline.

4 / 5

Workflow Clarity

The create/update workflow has a mandatory order with explicit validation checkpoints ("Validate ALL queries before adding", "validation runs automatically"); not 5 because the error-recovery feedback loop on validation failure is delegated to the reference rather than stated inline. Validation is present, so the destructive-operation cap at 3 does not apply.

4 / 5

Progressive Disclosure

Clear overview with a well-signaled references table mapping each one-level-deep file (analyzing.md, create-update.md, tiles.md, variables.md — all verified present) to when to load it; not 4 because navigation is explicit and content is appropriately split with no nesting.

5 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, naming concrete actions and domain objects tied to a clear product niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when creating, modifying, querying, or analyzing Dynatrace dashboards, or when the user mentions DQL queries, tiles, layouts, or dashboard variables.'

Include a few synonymous user-facing verbs (e.g. 'edit', 'build') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("create, modify, query, and analyze") plus concrete domain objects ("tiles, layouts, DQL queries, variables, and visualizations"), giving comprehensive coverage; not score 4 because the action set and domain elements are broad rather than having minor gaps.

5 / 5

Completeness

The "what" is clearly and specifically stated, but the description lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3; not 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Natural Dynatrace-user terms are well covered ("Dynatrace dashboards", "dashboard JSON", "DQL queries", "variables", "visualizations"); not 5 because synonymous verbs like "edit"/"build" and any file-extension trigger are absent.

4 / 5

Distinctiveness Conflict Risk

"Dynatrace dashboards" is a clear, product-specific niche with distinct triggers and minimal conflict risk with other skills; not 4 because there is no meaningful overlap with closely related skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dynatrace/dynatrace-for-ai
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.