Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.
95
92%
Does it follow best practices?
Impact
96%
1.43xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities and provides explicit trigger guidance. The description uses proper third-person voice and covers the essential what/when structure. Minor improvement could be made by expanding trigger terms to include common abbreviations and related concepts users might mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'searching logs, querying metrics, tracing requests, and managing dashboards' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('searching logs, querying metrics, tracing requests, managing dashboards') AND when ('debugging production issues or working with Datadog observability') with explicit 'Use this when' clause. | 3 / 3 |
Trigger Term Quality | Includes good terms like 'Datadog', 'logs', 'metrics', 'dashboards', 'debugging production issues', and 'observability', but missing common variations users might say like 'APM', 'monitors', 'alerts', or 'DD'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - 'Datadog CLI' is a specific tool that won't conflict with generic logging or metrics skills. The combination of Datadog-specific terminology creates clear boundaries. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while remaining highly actionable. The command table provides quick reference, examples are executable and practical, and the incident triage workflow shows a clear debugging sequence. The progressive disclosure to reference docs is well-organized and clearly signaled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information. No unnecessary explanations of what Datadog is or how CLIs work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Every command includes copy-paste ready examples with actual flags and arguments. The setup section provides exact environment variable names and commands to run. | 3 / 3 |
Workflow Clarity | The Incident Triage Workflow section provides a clear 6-step sequence with explicit progression from overview to specific investigation. Each step builds logically on the previous one. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in SKILL.md and clear one-level-deep references to detailed docs (logs-commands.md, metrics.md, etc.). The 'Required Reading' section clearly signals where to find detailed information. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
3027f20
Table of Contents
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.