CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-obs-aws

AWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization. Use when analyzing AWS infrastructure, resource inventory, security compliance, capacity planning, or cost savings. Trigger: "show EC2 instances", "find RDS databases", "VPC resources", "AWS cost optimization", "Lambda functions", "ECS services", "security groups", "unattached EBS volumes", "AWS load balancer topology", "publicly accessible databases", "AWS dashboards". Do NOT use for explaining existing queries, product documentation questions, generic host CPU/memory metrics (use dt-obs-hosts), application-level tracing (use dt-obs-tracing), or log analysis (use dt-obs-logs).

70

Quality

86%

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

72%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 highly actionable with executable DQL examples and excellent progressive disclosure across real reference files, but it is padded with redundant best-practice re-statements and lacks explicit validation checkpoints in its batch workflows.

Suggestions

Trim redundant restatement: the 'When to Load References' section duplicates the inline 'Load ... when' bullets already present and the reference purposes in the References list — keep one canonical mapping.

Add explicit validation checkpoints to batch workflows (e.g., after `parse aws.object` insert an `isNotNull()` guard in-line rather than only mentioning it in Best Practices).

Drop context Claude already knows, such as 'All AWS entities are automatically discovered and modeled in Dynatrace Smartscape', to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete DQL examples, but several sections restate context Claude already knows (e.g., 'All AWS entities are automatically discovered and modeled in Dynatrace Smartscape', repeated best-practice bullets) and the 'When to Load References' section repeats reference purposes already given inline.

3 / 5

Actionability

Eight copy-paste-ready DQL workflows plus a query-pattern table and concrete field lists give fully executable guidance covering the common cases, matching the anchor for copy-paste ready code.

5 / 5

Workflow Clarity

Workflows are well sequenced by task type, but operations like bulk resource filtering and cost allocation are batch-style with no validation/verification checkpoints (e.g., null-checks after parse are mentioned only in best practices, not in-line), so the workflow-clarity cap for batch operations without validation applies.

3 / 5

Progressive Disclosure

Clear overview body with well-signaled one-level-deep references to 12 real reference files, each tied to a 'Load ... when:' trigger condition and a consolidated reference list, making navigation easy.

5 / 5

Total

16

/

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 strong, well-scoped description that pairs concrete capabilities with natural trigger phrases and explicit boundary guidance against sibling skills. It satisfies all four completeness/specificity dimensions with minimal padding.

DimensionReasoningScore

Specificity

Lists many concrete actions and resources — 'monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization' plus inventory, security compliance, capacity planning — comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both 'what' (AWS resource monitoring across listed services) and 'when' (a dedicated 'Use when...' clause plus a 'Trigger:' list), matching the anchor for concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ('show EC2 instances', 'find RDS databases', 'security groups', 'unattached EBS volumes') plus negative boundary triggers pointing to sibling skills.

5 / 5

Distinctiveness Conflict Risk

Clear AWS/Dynatrace niche with explicit 'Do NOT use for...' boundary guidance redirecting hosts/tracing/logs to sibling skills, 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.

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.