dt-obs-logs

Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product documentation questions, distributed tracing or span analysis (use dt-obs-tracing).

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The body is a strong, actionable DQL reference with comprehensive executable examples and clear workflow structure. Its main weakness is mild section redundancy and a monolithic single-file layout that could delegate the function/pattern reference to a bundle file.

Suggestions

Consolidate 'What This Skill Covers', 'Use Cases', and 'Integration Points' to remove overlap and tighten the token budget (boosts conciseness).

Extract the 'Key Functions' and 'Common Patterns' sections into a references/ file (e.g. dql-patterns.md) referenced one level deep, leaving SKILL.md as a leaner overview (boosts progressive_disclosure).

Add explicit validation checkpoints to the Core Workflows (e.g., 'If no logs returned, widen the time window per the troubleshooting table') to close the workflow_clarity gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and Dynatrace-specific (no generic 'what is a log' padding), but 'What This Skill Covers' overlaps with 'Use Cases' and 'Integration Points' recapitulates 'Key Concepts/Functions', so minor trimming is possible. Not 5 due to this redundancy; not 3 because nearly every section earns its tokens.	4 / 5
Actionability	Multiple complete, copy-paste-ready DQL queries cover the common cases — error filtering, aggregation, pattern detection, JSON parsing, error-rate calculation, top errors — with specific functions and syntax.	5 / 5
Workflow Clarity	Three core workflows give clear numbered sequences paired with executable examples, and a troubleshooting table provides error-recovery guidance; lacks explicit validation checkpoints, but log querying is read-only so the destructive-operation cap does not apply. Not 5 due to absent explicit verify steps.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and a clearly signaled one-level-deep cross-skill reference (the smartscape-topology-navigation.md blockquote), but all ~256 lines are inlined monolithically with no bundle files splitting the function/pattern reference. Not 5 because content is not split across files; not 3 because structure and navigation are good.	4 / 5
	Total	17 / 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.

The description is exemplary: third-person voice, concrete actions, a rich set of natural trigger phrases, and explicit negative boundary guidance. It cleanly answers both 'what' and 'when' with minimal padding.

Dimension	Reasoning	Score
Specificity	Names four concrete actions — 'Log querying, filtering, pattern analysis, and error rate calculation' — covering the domain comprehensively, matching the 5-anchor multi-action example.	5 / 5
Completeness	Explicitly states what ('Log querying, filtering, pattern analysis, and error rate calculation') and when ('Use when searching application or infrastructure logs...') with a dedicated concrete Trigger list.	5 / 5
Trigger Term Quality	Twelve natural user phrases ('show error logs', 'log error rate', 'parse JSON logs', 'log trends over time', etc.) provide comprehensive coverage of how users actually request log analysis.	5 / 5
Distinctiveness Conflict Risk	Clear Dynatrace log niche with explicit boundary guidance — 'Do NOT use for... distributed tracing or span analysis (use dt-obs-tracing)' — minimizing sibling-skill conflict.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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-logs/SKILL.md
Commit: 3287f9d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.