CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-obs-frontends

Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via `user.events`, `user.sessions`, and `dt.frontend.*` metrics. Does NOT cover synthetic monitoring (HTTP/browser/network checks) — that's a separate domain.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/dt-obs-frontends/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, token-efficient skill body with excellent progressive disclosure and concrete data-model guidance. The main gap is the lack of executable DQL query examples inline, which slightly limits actionability.

Suggestions

Add one or two short executable DQL examples (a `fetch user.events` and a `timeseries dt.frontend.*` snippet) in the body to make guidance copy-paste ready.

Tighten the discursive frontend.name/Smartscape paragraph to its essential rule for marginal conciseness gains.

DimensionReasoningScore

Conciseness

Dense, information-packed body with minimal padding that assumes Claude's competence; a few discursive passages (e.g., the frontend.name/Smartscape guidance) could be tightened.

4 / 5

Actionability

Concrete field names, filter patterns, characteristic filters, a real policy statement, and quick-reference thresholds, but no copy-paste-ready DQL query examples in the body itself (those live in references).

4 / 5

Workflow Clarity

The Drill-Down Pattern gives a clear numbered sequence and the Workflows table maps domains to references; no destructive/batch operations apply, but validation checkpoints are implicit rather than explicit feedback loops.

4 / 5

Progressive Disclosure

Concise overview in SKILL.md with a clean Workflows table signaling one-level-deep references; all 11 referenced files exist and match the body, with no nested references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

75%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 with comprehensive capabilities and a strong explicit boundary. Its main gap is the absence of a positive 'Use when...' trigger clause, which limits completeness.

Suggestions

Add an explicit 'Use when ...' clause with concrete trigger phrases users would naturally say (e.g., 'Use when investigating Core Web Vitals, page load performance, mobile crashes, or frontend errors from real users').

Include natural synonyms and file/format-style terms to broaden trigger_term_quality toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain plus a comprehensive catalog of concrete capabilities ('Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking') and concrete query sources ('user.events, user.sessions, and dt.frontend.* metrics').

5 / 5

Completeness

Has a clear 'what' (capabilities and query sources) but no explicit positive 'Use when...' trigger clause; the missing trigger guidance caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('Core Web Vitals', 'user sessions', 'mobile crashes', 'frontend errors') but phrasing reads as a capability catalog rather than natural user utterances, with no file extensions or common synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (RUM on Dynatrace frontends) with an explicit boundary ('Does NOT cover synthetic monitoring... that's a separate domain') minimizing conflict with sibling skills.

5 / 5

Total

17

/

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.

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