CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dt-obs-predictive-analytics

Predictive analytics for Dynatrace — time series forecasting with the timeseries-forecast tool, capacity saturation planning, trend and anomaly detection across hosts, services, and infrastructure.

Quality

81%

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

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

A well-structured, highly actionable skill body: executable DQL patterns, an excellent tool-selection framework, and clean one-level-deep progressive disclosure into real, substantive reference files. The only notable improvements are trimming duplication with the reference files and making the analysis sequence and validation checkpoints more explicit.

DimensionReasoningScore

Conciseness

The body is dense and assumption-respecting — decision tables, a plain-language tool rule, and five copy-paste DQL queries with no general-knowledge padding. Minor trimmable redundancy exists: the result-presentation table and univariate-only constraint are repeated in references/forecasting-analyzer.md, and the fleet-wide pitfall is duplicated in references/anomaly-scoring.md.

4 / 5

Actionability

Five complete, executable DQL patterns (moving-average trend, saturation-risk classification, days-to-saturation, anomaly scoring, metric discovery) plus a question-to-tool mapping table and concrete parameter guidance (e.g. "timeseries-novelty-detection with TREND_IN_VALUES") make the common cases copy-paste ready.

5 / 5

Workflow Clarity

The analysis path is clear — discipline table, tool-choice table keyed to literal user questions, a decision rule, and a mandated output format with a Key Findings section — but the end-to-end sequence is implied rather than explicitly ordered, and result-validation checkpoints (e.g. checking forecast confidence before recommending action) are implicit. Operations are read-only, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

All five referenced files (forecasting-analyzer.md, capacity-forecasting.md, anomaly-scoring.md, novelty-detection.md, trend-detection.md) exist and are listed with one-line content descriptions; the body stays an overview with core patterns while details are one level deep, and the few sibling cross-references between reference files are supplementary pointers to real content, not buried chains.

5 / 5

Total

18

/

20

Passed

Description

66%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 specific, well-scoped description that names concrete capabilities and the target platform with strong natural trigger terms. Its main weakness is the absence of any "Use when…" guidance, leaving the triggering conditions entirely implicit.

Suggestions

Append a trigger clause such as "Use when the user asks to forecast metrics, plan capacity or saturation dates, or detect trends and anomalies in Dynatrace data" to satisfy the missing 'when' dimension.

Add natural trigger synonyms like "predict", "projection", and "when will we run out of capacity" to broaden keyword coverage.

Mention change/novelty detection explicitly (e.g. "detect when a metric's behavior changed") to distinguish it from generic anomaly-detection skills and complete the capability list.

DimensionReasoningScore

Specificity

Lists several concrete, tool-anchored actions — "time series forecasting with the timeseries-forecast tool", "capacity saturation planning", "trend and anomaly detection" — but compresses two disciplines into one phrase and omits novelty/signal-characterization work, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clearly stated (forecasting, capacity planning, trend/anomaly detection across hosts, services, infrastructure), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("forecast", "capacity", "saturation", "trend", "anomaly", "predictive analytics"), giving good keyword coverage, though common synonyms like "predict", "projection", or "outlier" are missing.

4 / 5

Distinctiveness Conflict Risk

"for Dynatrace" plus the named timeseries-forecast tool establishes a clear niche with minimal conflict risk; minor overlap remains with related host/service/anomaly observability skills since the description also spans "hosts, services, and infrastructure".

4 / 5

Total

15

/

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-obs-predictive-analytics/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.