dt-migration
Migrate Dynatrace classic and Gen2 entity-based DQL, topology navigation, and classic entity selectors to Smartscape equivalents. Use this skill when users want to convert classic entities to Smartscape nodes, rewrite entityName, entityAttr, or classicEntitySelector patterns, or map old relationships to Smartscape traversal.
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dt-migration/SKILL.mdQuality
Discovery
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 clearly defines a narrow, specific domain (Dynatrace classic-to-Smartscape migration) with concrete actions and explicit trigger guidance. It uses third-person voice correctly, includes domain-specific trigger terms that users would naturally use, and has a well-structured 'Use this skill when...' clause covering multiple trigger scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrate classic and Gen2 entity-based DQL, topology navigation, and classic entity selectors to Smartscape equivalents; convert classic entities to Smartscape nodes; rewrite entityName, entityAttr, classicEntitySelector patterns; map old relationships to Smartscape traversal. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate classic/Gen2 DQL, topology navigation, and entity selectors to Smartscape equivalents) and 'when' (explicit 'Use this skill when...' clause with specific trigger scenarios like converting entities, rewriting patterns, or mapping relationships). | 3 / 3 |
Trigger Term Quality | Includes highly specific natural keywords a Dynatrace user would use: 'Dynatrace', 'classic', 'Gen2', 'DQL', 'Smartscape', 'entityName', 'entityAttr', 'classicEntitySelector', 'topology navigation', 'Smartscape traversal'. These are the exact terms a user working on this migration would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and domain-specific to Dynatrace Smartscape migration. The combination of specific Dynatrace terminology (classicEntitySelector, entityName, entityAttr, Smartscape) makes it virtually impossible to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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-organized migration reference skill with strong progressive disclosure and useful mapping tables. Its main weaknesses are the lack of inline before/after DQL code examples (forcing reliance on reference files for any concrete guidance) and the absence of validation/verification steps in the migration workflow. The content could also be tightened by removing the redundant use-case table.
Suggestions
Add at least one or two inline before/after DQL migration examples (e.g., a classic `fetch dt.entity.host` query rewritten to Smartscape) so the skill is actionable without loading references.
Add an explicit validation step to the migration workflow, such as 'Run the rewritten query and verify it returns the expected shape and cardinality before finalizing.'
Consider removing or condensing the 'Use Cases' table, as it largely restates what the migration workflow already covers, to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary explanation (e.g., 'This skill helps migrate...' preamble, the 'Use Cases' table largely restates the workflow). The mapping tables and construct tables are efficient, but the surrounding prose could be tightened. Some redundancy between the use-case table and the migration workflow section. | 2 / 3 |
Actionability | The skill provides structured mapping tables and a clear migration workflow sequence, but lacks any concrete executable DQL code examples showing before/after transformations. Without at least one complete example inline, Claude must load references to see actual query syntax, making the main skill body incomplete for direct execution. | 2 / 3 |
Workflow Clarity | The 7-step migration workflow is clearly sequenced and logical, but lacks explicit validation checkpoints or feedback loops. For a migration task where incorrect translations could produce broken queries, there's no 'validate the output' or 'test the rewritten query' step. Step 6 mentions checking special cases but doesn't define how to verify correctness. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main skill provides a compact overview with core mapping tables, then clearly signals one-level-deep references for detailed guides (entity-specific guides, function migration, special cases, examples). Navigation is well-organized with a references section and entity-focused guides clearly listed with descriptions of what each contains. | 3 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dynatrace/dynatrace-for-ai
- Commit
4991356
- 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.