What is dt-migration?

A Dynatrace migration guide for changing older entity-based DQL queries to Smartscape queries. Dynatrace is an application-monitoring platform, DQL is its query language, and Smartscape is its model of monitored components and their relationships.

Use it to convert classic entity types, selectors, relationship patterns, and functions such as entityName() or classicEntitySelector() into Smartscape-oriented DQL.

It helps update queries that use older entity names, attributes, selectors, or relationships so they use Smartscape concepts instead.

How israel-salgado/dt-mcp-server configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to israel-salgado/dt-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/israel-salgado/dt-mcp-server/main/.agents/skills/dt-migration/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/israel-salgado/dt-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-migration/github.svg)](https://agentmods.dev/skills/israel-salgado/dt-mcp-server/dt-migration)

Your own site

<a href="https://agentmods.dev/skills/israel-salgado/dt-mcp-server/dt-migration"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-migration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/israel-salgado/dt-mcp-server/dt-migration"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,768 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00067	$0.01768
Opus 5	$0.00034	$0.00884
Sonnet 5	$0.00013	$0.00354
Haiku 4.5	$0.00007	$0.00177

Measured 11d ago against content hash 7a21434c6e03, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dt-migration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/dt-migration/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Smartscape Migration Skill

This skill helps migrate Dynatrace classic and Gen2 entity-based DQL queries and query patterns to Smartscape-based equivalents.

Use it to:

convert classic entity types to Smartscape node types
rewrite classic entity DQL into Smartscape DQL
migrate entityName(), entityAttr(), classicEntitySelector(), and classic relationship patterns
explain how classic entity concepts map to Smartscape nodes, edges, fields, and IDs

Load the dt-dql-essentials skill before writing final DQL so the translated query also follows current DQL syntax rules.

This skill focuses on Smartscape-oriented DQL migration only. It does not cover asset-level migration workflows.

Use Cases

Load this skill when the user wants to:

Use case	What to do
Convert a classic entity query to Smartscape	Follow the migration workflow, use the mapping table, then load the relevant detailed references
Migrate `classicEntitySelector(...)` to Smartscape	Start from the constrained side, convert selector filters to node filters, and replace relationship selectors with `traverse`
Understand what a classic entity became in Smartscape	Check the entity mapping table and special cases before translating literally
Rewrite classic DQL functions such as `entityName()` or `entityAttr()`	Use the DQL construct guidance and function migration reference
Migrate classic topology navigation	Replace relationship fields and selectors with `smartscapeNodes`, `smartscapeEdges`, `traverse`, or `references`
Translate signal or event queries using `dt.entity.*` dimensions	Rewrite every entity dimension to the correct `dt.smartscape.*` field and adjust related helpers

Migration Workflow

Follow this order:

Identify the classic input pattern:
- fetch dt.entity.*
- classicEntitySelector(...)
- relationship field access such as belongs_to[...], runs[...], instance_of[...]
- signal or event queries using dt.entity.*
Identify the involved classic entity types.
Look up the Smartscape replacement in the core entity mapping table below.
Check which classic DQL constructs need explicit migration.
Rewrite the query using Smartscape primitives:
- smartscapeNodes
- smartscapeEdges
- traverse
- references
- getNodeName()
- getNodeField()
Check for special cases, unsupported entities, or ID assumptions.
Load the matching detailed references for the specific entity family or migration pattern.

Read the full file on GitHub · 135 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 135 lines · 67 tokens per session scan A 7a21434c6e03

Subscribe to this mod's changes

dt-migration is a skill published in the GitHub repository israel-salgado/dt-mcp-server (2 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,768 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

dt-mcp-server: Skill for Claude Code