CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dt-platform-costs

Query and analyze a Dynatrace tenant's ACTUAL billing and usage data with DQL on dt.system.events — DPS consumption breakdown, cost-normalized spend ranking, included volume deduction, chargeback/showback, cost drivers, spending trends, cost investigation, log import cost, metrics ingest optimization, drop/remove a metric or dimension from ingestion, reduce metric cardinality, metric usage, query cost attribution, workflow total cost, entity cost drill-down (RUM, hosts, synthetic, K8s), AI/LLM cost (AI Units, AI Function Standard Calls). Directs licensing/entitlement questions (am I entitled to use X?) to docs (not via DQL). USE ONLY for the tenant's actual consumption. Do NOT use for conceptual 'explain' questions about how DPS billing/pricing works or what units/weights/the rate card mean — see Dynatrace docs. Do NOT use for tuning DQL queries to be faster or cheaper to run (query optimization, reducing scanned data/consumption per run, filter-early best practices) — that belongs to dt-dql-essentials.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An exceptionally actionable, well-sequenced routing skill with flawless progressive disclosure — every pointer verified, every workflow gated by a pre-flight check, and error-recovery paths spelled out. The single weakness is repetition: the scope guardrail and cost presentation rules are restated across multiple sections, and consolidating them would cut tokens without losing precision.

Suggestions

Consolidate the scope guardrail, which currently appears in four places (opening ⛔ banner, Billing Concepts — STOP, and two intent-mapping rows) — keep the STOP section with its prescribed response text and reduce the banner and table entries to one-line pointers to it.

Merge the rated/unrated presentation rules that are duplicated between the Usage vs Cost Distinction table and Cost Ranking Rules steps 1–2 (e.g. the triple-repeated "drop cost_weight before presenting" and the sorting expressions) into a single authoritative location referenced from the other.

Trim redundancy inside Cost Ranking Rules step 3 (disclaimer placement restated for rated, unrated, single-capability, and zero-rated cases) by stating the general rule once with a compact variant table.

DimensionReasoningScore

Conciseness

The body teaches nothing Claude already knows and the intent table is dense signal, but the scope guardrail is repeated in four places (opening banner, Billing Concepts — STOP section, two intent-table rows) and the rated/unrated presentation rules are duplicated between the Usage vs Cost Distinction table and Cost Ranking Rules steps 1–2 ("drop cost_weight before presenting" appears three times), so it could be meaningfully tightened rather than having only minor trims.

3 / 5

Actionability

The body gives a copy-paste Quick Start DQL query, exact executable pipeline fragments ("| filter isNotNull(cost_weight) | sort cost_weight desc | fields event.type, capability_usage, cost_weight"), exact sort expressions, verbatim response templates, and per-intent routing that names the exact reference query to run — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Cost Ranking Rules is a numbered 0–4 checklist with an explicit pre-flight validation gate, clear rated/unrated decision branches, and enumerated exceptions; error-recovery loops are present (empty results → run the discovery query, the 14-day window limit with a concrete 2.7× failure example, "sample first, then run drill-down query"). The skill is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

All 8 reference files exist, are cataloged in the Knowledge Base Structure table, and every section anchor cited in the body (e.g. "#unit-conversion-table", "#pre-flight-detection", "#how-often-did-the-workflow-run") resolves to a real heading; references are one level deep with self-contained content, and SKILL.md is a routing overview with the ~4,300 lines of detail appropriately split into references.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A highly specific, well-bounded description that states concrete capabilities, explicit use and do-not-use triggers, and clear disambiguation from sibling skills. Its only weakness is that a handful of natural cost-related phrasings users might say (e.g. "reduce costs", "spending spike") are absent from the trigger coverage, and its length, while dense with signal, is at the upper end.

DimensionReasoningScore

Specificity

The description lists over a dozen concrete, specific actions ("DPS consumption breakdown, cost-normalized spend ranking, included volume deduction, chargeback/showback, cost drivers... entity cost drill-down (RUM, hosts, synthetic, K8s), AI/LLM cost (AI Units, AI Function Standard Calls)") that map one-to-one onto the skill body's use cases, with comprehensive coverage and no visible gaps.

5 / 5

Completeness

Both "what" ("Query and analyze a Dynatrace tenant's ACTUAL billing and usage data with DQL on dt.system.events") and "when" ("USE ONLY for the tenant's actual consumption", "Do NOT use for conceptual 'explain' questions... see Dynatrace docs", "that belongs to dt-dql-essentials") are answered explicitly with concrete trigger phrases in both positive and negative directions.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("cost drivers", "spending trends", "chargeback/showback", "reduce metric cardinality", "workflow total cost", "AI Units") plus concrete negative triggers, but a few natural user phrasings like "reduce costs", "save money", "spending spike", or "why is my bill high" are missing, so it falls short of the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — actual tenant consumption queried via DQL — and explicitly disambiguates against sibling skills ("that belongs to dt-dql-essentials" for query tuning; entitlement questions routed to docs rather than DQL), giving minimal conflict risk with related skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Dynatrace/dynatrace-for-ai

Path

skills/dt-platform-costs/SKILL.md

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.