CtrlK
BlogDocsLog inGet started
Tessl Logo

datadog-automation

Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/datadog-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured and actionable with concrete tool sequences and parameter guidance, but destructive operations lack explicit validation checkpoints and some pitfall content is duplicated across sections. Splitting the reference material into a bundled file would improve progressive disclosure.

Suggestions

Add an explicit validation/confirmation step before destructive calls (e.g. 'Confirm dashboard_id with the user before DATADOG_DELETE_DASHBOARD').

De-duplicate the timestamp and query-syntax pitfalls that appear both in per-workflow sections and the global 'Known Pitfalls' section.

Move the Quick Reference table and Common Patterns into a bundled reference file, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence, but pitfall content (timestamps, query syntax) is repeated between per-workflow 'Pitfalls' blocks and the global 'Known Pitfalls' section, which could be consolidated.

4 / 5

Actionability

Concrete tool slugs, key parameters, and executable query-syntax examples (e.g. 'avg(last_5m):avg:system.cpu.user{env:prod} > 90') give mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Workflows are sequenced with 'When to use' and tool orders, but destructive operations like DELETE dashboard ('irreversible', 'no undo') have no validation checkpoint before execution, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized into clear ## and ### sections with a useful Quick Reference table, though the ~230-line body is monolithic with no external reference files for the bulkier reference material.

4 / 5

Total

15

/

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.

The description is specific and distinctive with strong action coverage, but it lacks an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' sentence would lift the weakest dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to query Datadog metrics, search logs, or manage monitors, dashboards, events, or downtimes.'

Include natural synonyms such as 'alerts' (for monitors) or 'observability' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'query metrics, search logs, manage monitors/dashboards, create events and downtimes' — giving comprehensive coverage of the toolkit's capabilities.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the closing 'Always search tools first for current schemas' is operational guidance, not a usage trigger, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Good keyword coverage (Datadog, metrics, logs, monitors, dashboards, events, downtimes) but a few natural synonyms like 'alerts' or 'observability' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Datadog automation via Rube MCP (Composio) — with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.