CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-dql-essentials

Core DQL syntax rules, common pitfalls, and query patterns. Load this skill when you need to write, build, or fix a DQL query — it prevents syntax errors and guides correct usage. Covers fetch commands, data models, field namespaces, time alignment, entity patterns, metric discovery, and smartscape topology navigation. Trigger: "write a DQL query", "build me a query", "DQL syntax", "how do I query logs/spans/metrics in Dynatrace", "create a timeseries", "fix my DQL", "fetch logs", "smartscapeNodes", "query optimization". Do NOT use for explaining an existing query or answering Dynatrace product questions — those do not require query-construction guidance.

83

1.95x
Quality

86%

Does it follow best practices?

Impact

96%

1.95x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a strong, comprehensive DQL reference skill with excellent actionability through concrete code examples and an outstanding syntax pitfalls table. Its main weaknesses are the duplicated makeTimeseries section, the very large inline DQL Reference Index that could be offloaded, and the lack of an explicit step-by-step query construction workflow with validation checkpoints.

Suggestions

Remove the duplicated makeTimeseries section (appears twice with slightly different formatting) and consolidate into a single authoritative section.

Move the large DQL Reference Index table to a separate reference file (e.g., references/dql-function-index.md) and replace with a brief pointer — this table alone consumes significant tokens.

Add a brief step-by-step query construction workflow (e.g., 1. Identify data object from fetch table, 2. Check field names in semantic dictionary, 3. Write query, 4. Verify against syntax pitfalls) to guide the overall process.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with table-based formats and concrete examples, but there is some redundancy — the makeTimeseries section appears twice with slightly different content, and the DQL Reference Index is an extremely long catalog that could be offloaded to a reference file. Some sections like 'Modifying Time' explain concepts Claude likely knows (timestamp arithmetic basics).

2 / 3

Actionability

The skill provides highly actionable, executable DQL snippets throughout — from fetch commands, timeseries queries, lookup patterns, metric discovery, to makeTimeseries examples. The syntax pitfalls table with wrong vs. right columns is exceptionally concrete and copy-paste ready.

3 / 3

Workflow Clarity

The skill covers many individual patterns clearly but lacks explicit multi-step workflow sequences with validation checkpoints. For a query-construction skill, there's no 'build a query' workflow (e.g., 1. identify data object, 2. check fields, 3. write query, 4. validate). The chained lookup pattern comes closest to a sequenced workflow but lacks error recovery steps.

2 / 3

Progressive Disclosure

The skill has excellent progressive disclosure with a clear reference routing table at the top, well-signaled one-level-deep references throughout (semantic dictionary, optimization, smartscape topology, summarization, iterative expressions, operators), and inline content kept to essential patterns. The DQL Reference Index provides a comprehensive function-to-file routing table.

3 / 3

Total

10

/

12

Passed

Description

100%

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 an excellent skill description that covers all key dimensions thoroughly. It provides specific capabilities, comprehensive natural trigger terms, clear 'what' and 'when' guidance, and even includes explicit exclusion criteria to prevent misuse. The description is well-structured, concise, and uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and capabilities: fetch commands, data models, field namespaces, time alignment, entity patterns, metric discovery, smartscape topology navigation, and explicitly mentions writing, building, and fixing DQL queries.

3 / 3

Completeness

Clearly answers both 'what' (core DQL syntax rules, common pitfalls, query patterns covering fetch commands, data models, etc.) and 'when' (explicit trigger list plus a 'Do NOT use' exclusion clause that further clarifies appropriate usage boundaries).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'write a DQL query', 'build me a query', 'DQL syntax', 'how do I query logs/spans/metrics in Dynatrace', 'create a timeseries', 'fix my DQL', 'fetch logs', 'smartscapeNodes', 'query optimization'. These are highly natural and varied.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (DQL query construction for Dynatrace) and explicitly delineates boundaries with a 'Do NOT use' clause that separates it from skills that might explain existing queries or answer general Dynatrace product questions.

3 / 3

Total

12

/

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.