CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-obs-ext-monitors

3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/). Use when sending external synthetic test outcomes, CI monitor data, or third-party check results to Dynatrace. Covers token scope, full event schema for external_test_run and external_test_step (including dt.security_context, ci.*, trace correlation, and pipeline-added fields), curl and Java DTO examples, and DQL verification. Triggers: "ingest test results", "send monitor results", "third party monitor", "external test ingestion", "send synthetic results to Grail", "external test run event schema". Not for Dynatrace-native Synthetic Monitoring browser/HTTP checks, or RUM (use dt-obs-frontends). For migrating from the deprecated POST /api/v1/synthetic/ext/tests API, load dt-upgrade instead.

77

Quality

96%

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

93%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, action-oriented skill body that is lean for a complex domain API and uses a single clearly-signaled reference file for depth. The only gap is the absence of an explicit error-recovery feedback loop anchored to the verification step.

DimensionReasoningScore

Conciseness

The body is lean: it explains only Dynatrace-specific behaviour (OpenPipeline metric extraction, EXT_TEST Smartscape nodes, Davis Problems) that Claude would not already know, with concrete curl/DQL examples and a dense Key Constraints list — every token earns its place.

5 / 5

Actionability

Provides a copy-paste-ready curl POST with clear placeholders, a concrete token-scope table (including the 'events.ingest' wrong-guess warning), an executable DQL verification query, and explicit field constraints — fully executable guidance covering the common case.

5 / 5

Workflow Clarity

The section ordering implies a clear auth → send → verify sequence and includes an explicit 'Verify in Grail' checkpoint plus a constraints troubleshooting list, but there is no explicit error-recovery feedback loop tied to verification (e.g. 'if the event does not appear, check token scope / endpoint existence'), so it sits just below the top anchor.

4 / 5

Progressive Disclosure

The body is a focused overview that keeps a minimal quick-start inline and pushes the full schema, extended examples, Java DTO shapes, and DQL queries to a single one-level-deep, clearly-signaled real reference (references/event-ingestion.md), with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

100%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-triggered description that explicitly covers both what the skill does and when to use it, with proactive boundary guidance to sibling skills. No vague fluff or over-claims; third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'ingestion into Dynatrace Grail via the platform events ingest API', token scope, 'full event schema for external_test_run and external_test_step', 'curl and Java DTO examples', and 'DQL verification' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It clearly answers 'what' (the ingest mechanism and schema/example coverage) and 'when' (both a 'Use when sending...' clause and a dedicated concrete Triggers list), matching the anchor for explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

An explicit Triggers block supplies six natural phrases users would say ('ingest test results', 'send monitor results', 'third party monitor', 'external test ingestion', 'send synthetic results to Grail', 'external test run event schema') alongside a 'Use when sending...' clause, covering synonyms comprehensively.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Dynatrace-Grail external-ingestion niche and proactively disambiguates by routing native Synthetic/RUM to dt-obs-frontends and the deprecated POST /api/v1/synthetic/ext/tests migration to dt-upgrade, minimizing conflict risk.

5 / 5

Total

20

/

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