CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-migration

Migrate Dynatrace classic and Gen2 entity-based DQL to Smartscape equivalents. Covers three scenarios. (1) mass data queries filtered by classic entity conditions — migrate to direct dimension filters first, Smartscape only as fallback; (2) mass data queries using entity subqueries for filtering — same dimension-first strategy; (3) pure entity list queries — migrate fetch dt.entity.* to smartscapeNodes. Also handles entityName, entityAttr, classicEntitySelector, and classic relationship patterns.

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-migration/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 well-structured and actionable, with strong progressive disclosure pointing to verified reference files. Workflow clarity is good but could surface validation checkpoints more explicitly inline rather than delegating them to referenced files.

Suggestions

Add explicit inline validation/verification checkpoints (e.g., a 'Verify equivalence' step) directly within the 7-step Migration Workflow rather than only referencing them in mass-data-filtering-strategy.md.

Inline one short before/after DQL example in the body to make the migration pattern immediately executable without loading references/examples.md.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using compact tables and step lists without explaining DQL basics; only minor sections could be tightened further.

4 / 5

Actionability

Concrete guidance via exact construct names, replacement primitives (smartscapeNodes, traverse, getNodeField()), and explicit mapping tables; some operational detail is deferred to reference files, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 'Start here' classification branches into a 7-step Migration Workflow with referenced verification gates (fieldsSnapshot gates, equivalence verification); inline validation checkpoints within the 7-step list itself are mostly implicit rather than explicit.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references; every referenced file exists, content is appropriately split, and a dedicated References section lists each file with a one-line description.

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 highly distinct, naming concrete migration actions and domain terms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits the completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers (e.g., 'Use when migrating Dynatrace classic or Gen2 entity-based DQL queries to Smartscape').

Include common user-facing synonyms or phrasings beyond the technical terms to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three named scenarios — 'migrate to direct dimension filters first', 'migrate fetch dt.entity.* to smartscapeNodes', plus handling entityName/entityAttr/classicEntitySelector/relationship patterns — giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clear and detailed across three scenarios, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong domain keywords a user would actually say (Dynatrace classic/Gen2, Smartscape, mass data queries, fetch dt.entity.*, smartscapeNodes) with some synonyms, but lacks conversational entry phrasing beyond the technical terms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Dynatrace DQL → Smartscape migration) with distinct, specific triggers and minimal overlap risk with other 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.