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.

69

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured skill that efficiently communicates dashboard structure, workflow rules, and visualization options while delegating detailed procedures to clearly referenced files. Its main weakness is that the core create/update workflow is almost entirely delegated to a reference file, meaning the SKILL.md itself doesn't contain fully executable step-by-step guidance. The conciseness and progressive disclosure are excellent.

Suggestions

Include the essential create/update workflow steps (at least a numbered summary) directly in SKILL.md rather than fully delegating to the reference file, so Claude has actionable guidance without needing to load additional context.

Add a minimal complete tile JSON example showing a data tile wired to a DQL query with its corresponding layout entry, making the tile creation process copy-paste ready.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It avoids explaining what Dynatrace is or how JSON works, assumes Claude's competence, and every section delivers only the information needed to act. No unnecessary padding or concept explanations.

3 / 3

Actionability

The skill provides concrete JSON structures, specific commands (dtctl get/apply), and clear rules, but the core create/update workflow is delegated to a reference file rather than being directly executable here. The visualization types list is informative but lacks concrete tile JSON examples showing how to wire a query to a visualization.

2 / 3

Workflow Clarity

The create/update workflow has a mandatory order with explicit validation steps (validate ALL queries before adding, deploy with dtctl apply which runs validation automatically). The update path includes a clear feedback loop: download first, modify, then deploy. Key constraints like 'never reconstruct from scratch' and 'always download first' serve as guardrails against destructive operations.

3 / 3

Progressive Disclosure

The skill provides a clear overview with quick references inline and well-signaled one-level-deep references via a structured table. Each reference file has a clear 'When to Load' trigger, making navigation intuitive. Content is appropriately split between the overview and detailed reference files.

3 / 3

Total

11

/

12

Passed

Description

82%

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

This is a strong description with excellent specificity and distinctiveness, clearly identifying the Dynatrace dashboard domain with concrete actions and relevant sub-components. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.

Suggestions

Add a 'Use when...' clause such as 'Use when the user mentions Dynatrace dashboards, DQL, dashboard JSON, or needs to create/modify Dynatrace visualizations.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'create, modify, query, and analyze dashboard JSON' and further specifies sub-elements like 'tiles, layouts, DQL queries, variables, and visualizations.'

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions and components, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Dynatrace', 'dashboards', 'dashboard JSON', 'tiles', 'layouts', 'DQL queries', 'variables', 'visualizations'. These cover the domain well and match how users would naturally describe their needs.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific mention of 'Dynatrace' as the platform and 'DQL queries' as a Dynatrace-specific query language. Very unlikely to conflict with other dashboard or monitoring skills.

3 / 3

Total

11

/

12

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.

Validation11 / 11 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.