Agent skill

Dd Monitors

by datadog-labs in datadog-labs/agent-skills

Monitor management - list, search, file-based create, and alerting best practices.

Install Dd Monitors

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/dd-monitors .claude/skills/dd-monitors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .claude/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/dd-monitors .agents/skills/dd-monitors && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .agents/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/dd-monitors .cursor/skills/dd-monitors && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .cursor/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/datadog-labs/agent-skills.git --path dd-monitors

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/dd-monitors .gemini/skills/dd-monitors && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .gemini/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/dd-monitors .github/skills/dd-monitors && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .github/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add datadog-labs/agent-skills --skill dd-monitors -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install datadog-labs/agent-skills dd-monitors --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/datadog-labs/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/dd-monitors .opencode/skills/dd-monitors && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dd-monitors" agent skill from https://github.com/datadog-labs/agent-skills/tree/main/dd-monitors into .opencode/skills/dd-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-monitors", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dd-monitors
GitHub stars: 177
Token cost: ~1.2k tokens
SKILL.md length: 242 words
Files: 1
Skills in repo: 39
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Monitor management - list, search, file-based create, and alerting best practices.

Works in 4 steps: Avoid Alert Fatigue → Use Proper Scoping → Set Recovery Thresholds → …
DevOps & Cloud work in your project
SKILL.md covers Prerequisites, Command Execution Order…, Quick Start and Common Operations, plus 7 more sections
Calls jq

What it does

Dd Monitors is an agent skill from datadog-labs/agent-skills. Monitor management - list, search, file-based create, and alerting best practices.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. The repository describes itself as: Public repository for Datadog Agent Skills. The licence is MIT.

When your agent uses it

DevOps & Cloud work in your project

Example prompts

“/dd-monitors”

Requirements

Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Avoid Alert Fatigue
Use Proper Scoping
Set Recovery Thresholds
Include Context in Messages

What it can do on your machine

Read from SKILL.md and the folder at commit d2411cc. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- docs.datadoghq.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dd Monitors loads about 1.2k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 242 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~24
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from datadog-labs/agent-skills at commit d2411cc, republished under its MIT licence (© datadog-labs). 242 words, ~1,209 tokens.

Download SKILL.mdSave it as .claude/skills/dd-monitors/SKILL.md (or your agent's skills folder).

name: dd-monitors
description: Monitor management - list, search, file-based create, and alerting best practices.
metadata.version: 1.0.1
metadata.author: datadog-labs
metadata.repository: https://github.com/datadog-labs/agent-skills
metadata.tags: datadog,monitors,alerting,alerts,dd-monitors
metadata.globs: **/datadog*.yaml,**/*monitor*
metadata.alwaysApply: false

Datadog Monitors

Create, manage, and maintain monitors for alerting.

Prerequisites

This requires pup in your path. See Setup Pup.

Command Execution Order (Token-Efficient)

For scoped commands, use this order:

Check context first (prior outputs, conversation, saved values).
If a required value is missing, run a discovery command first.
If still ambiguous, ask the user to confirm.
Then run the target command.
Avoid speculative commands likely to fail.

Quick Start

bash

pup auth login

Common Operations

List Monitors

bash

pup monitors list
pup monitors list --tags "team:platform"

Get Monitor

bash

pup monitors get <id>

Create Monitor

bash

pup monitors create --file monitor.json

Silence Alerts (Downtime)

bash

# No pup monitors mute/unmute commands.
# Use downtime payloads to silence monitor notifications.
pup downtime create --file downtime.json
pup downtime cancel <downtime_id>

Monitor Creation Best Practices

1. Avoid Alert Fatigue

Rule	Why
No flapping alerts	Use `last_Xm` not `last_1m`
Meaningful thresholds	Based on SLOs, not guesses
Actionable alerts	If no action needed, don't alert
Include runbook	`@runbook-url` in message

python

# WRONG - will flap constantly
query = "avg(last_1m):avg:system.cpu.user{*} > 50"  # ❌ Too sensitive

# CORRECT - stable alerting
query = "avg(last_5m):avg:system.cpu.user{env:prod} by {host} > 80"  # ✅ Reasonable window

2. Use Proper Scoping

python

# WRONG - alerts on everything
query = "avg(last_5m):avg:system.cpu.user{*} > 80"  # ❌ No scope

# CORRECT - scoped to what matters
query = "avg(last_5m):avg:system.cpu.user{env:prod,service:api} by {host} > 80"  # ✅

3. Set Recovery Thresholds

python

monitor = {
    "query": "avg(last_5m):avg:system.cpu.user{env:prod} > 80",
    "options": {
        "thresholds": {
            "critical": 80,
            "critical_recovery": 70,  # ✅ Prevents flapping
            "warning": 60,
            "warning_recovery": 50
        }
    }
}

4. Include Context in Messages

python

message = """
## High CPU Alert

Host: {{host.name}}
Current Value: {{value}}
Threshold: {{threshold}}

### Runbook
1. Check top processes: `ssh {{host.name}} 'top -bn1 | head -20'`
2. Check recent deploys
3. Scale if needed

@slack-ops @pagerduty-oncall
"""

NEVER Delete Monitors Directly

Use safe deletion workflow (same as dashboards):

python

def safe_mark_monitor_for_deletion(monitor_id: str, client) -> bool:
    """Mark monitor instead of deleting."""
    monitor = client.get_monitor(monitor_id)
    name = monitor.get("name", "")
    
    if "[MARKED FOR DELETION]" in name:
        print(f"Already marked: {name}")
        return False
    
    new_name = f"[MARKED FOR DELETION] {name}"
    client.update_monitor(monitor_id, {"name": new_name})
    print(f"✓ Marked: {new_name}")
    return True

Monitor Types

Type	Use Case
`metric alert`	CPU, memory, custom metrics
`query alert`	Complex metric queries
`service check`	Agent check status
`event alert`	Event stream patterns
`log alert`	Log pattern matching
`composite`	Combine multiple monitors
`apm`	APM metrics

Audit Monitors

bash

# Find monitors without owners
pup monitors list | jq '.[] | select(.tags | contains(["team:"]) | not) | {id, name}'

# Find noisy monitors (high alert count)
pup monitors list | jq 'sort_by(.overall_state_modified) | .[:10] | .[] | {id, name, status: .overall_state}'

Downtime vs Muting

Use	When
Downtime	Any planned silence window
Monitor edit	Query/threshold behavior changes

bash

# Downtime (preferred)
pup downtime create --file downtime.json

Failure Handling

Problem	Fix
Alert not firing	Check query returns data, thresholds
Too many alerts	Increase window, add recovery threshold
No data alerts	Check agent connectivity, metric exists
Auth error	`pup auth refresh`

References

Files

Just SKILL.md in dd-monitors of datadog-labs/agent-skills.

Open the folder on GitHubat commit d2411cc

Compare with similar skills

Dd Monitors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dd Monitors compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dd Monitors this skilldatadog-labs/agent-skills	177	—	~1.2k	Automated safety check: Pass	MIT	today
Monitor CInrwl/nx	29k	6 repos	~4.7k	Automated safety check: Pass	MIT	today
Terraform and OpenTofu Guideagentscope-ai/QwenPaw	36k	6 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Vercel Optimize Auditvercel-labs/agent-skills	32k	8 repos	~4.3k	Automated safety check: Pass	None	1 mo ago
Analyze GitHub Action Logswithastro/astro	63k	1 repos	~1.3k	Automated safety check: Pass	Custom licence	today
Openclaw Live Updateropenclaw/openclaw	392k	—	~3.7k	Automated safety check: Pass	MIT	today

Similar skills

Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
29k GitHub starsUsed in 6 repos~4.7k tokens
DevOps & CloudAuto-check passed
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
36k GitHub starsUsed in 6 repos~4.2k tokens
DevOps & CloudAuto-check passed
Vercel Optimize Audit
vercel-labs/agent-skills
Official
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
32k GitHub starsUsed in 8 repos~4.3k tokens
DevOps & CloudAuto-check passed
Analyze GitHub Action Logs
withastro/astro
Official
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
63k GitHub starsUsed in 1 repo~1.3k tokens
DevOps & CloudAuto-check passed
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
392k GitHub stars~3.7k tokensUpdated today
DevOps & CloudAuto-check passed
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
81k GitHub stars~2k tokensUpdated today
DevOps & CloudAuto-check passed

More from datadog-labs/agent-skills

All 39 skills in this repo

Agent Observability Experiment Bootstrap
datadog-labs/agent-skills
Bootstrap a reproducible LLM Observability experiment through the Python ddtrace SDK or the Node dd-trace SDK.
177 GitHub stars~2.3k tokensUpdated today
Auto-check passed
Dd Account Setup
datadog-labs/agent-skills
Ensure the user has an authenticated Datadog account with a valid DDAPIKEY on the right region before any Datadog setup or instrumentation.
177 GitHub stars~4.5k tokensUpdated today
Auto-check: notes
Dd Orchestrator
datadog-labs/agent-skills
Entry point for Datadog onboarding. An agent skill from datadog-labs/agent-skills.
177 GitHub stars~6.7k tokensUpdated today
Auto-check passed
Dd Apm
datadog-labs/agent-skills
APM - install, onboard, instrument, enable, set up, configure, traces, services, dependencies, performance analysis, Data Streams Monitoring (DSM), queue lag, pipeline latency.
177 GitHub stars~2k tokensUpdated today
Auto-check passed
Agent Install
datadog-labs/agent-skills
Install the Datadog Agent on Kubernetes using the Datadog Operator — required before enabling Single Step Instrumentation (SSI), which automatically instruments applications for APM without code…
177 GitHub stars~2.1k tokensUpdated today
Auto-check: warnings
Dd AWS Integration
datadog-labs/agent-skills
Set up the Datadog AWS integration with Terraform - creates the cross-account IAM role Datadog assumes (external ID, no stored credentials), attaches the permission policies Datadog publishes, and…
177 GitHub stars~6.8k tokensUpdated today
Auto-check: notes

Questions about Dd Monitors

What does Dd Monitors do?

Monitor management - list, search, file-based create, and alerting best practices. Dd Monitors is an agent skill from datadog-labs/agent-skills. Monitor management - list, search, file-based create, and alerting best practices.

When should I use Dd Monitors?

Dd Monitors fits situations like: devOps & Cloud work in your project.

How do I install Dd Monitors in Claude Code?

Run `npx skills add datadog-labs/agent-skills --skill dd-monitors -a claude-code`. Or copy the skill folder (dd-monitors in datadog-labs/agent-skills) into .claude/skills/dd-monitors in your project. Claude Code loads it when a task matches its description.

How do I install Dd Monitors in Codex?

Run `npx skills add datadog-labs/agent-skills --skill dd-monitors -a codex`. Or copy the skill folder (dd-monitors in datadog-labs/agent-skills) into .agents/skills/dd-monitors in your project. Codex loads it when a task matches its description.

Can I use Dd Monitors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add datadog-labs/agent-skills --skill dd-monitors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dd-monitors, .gemini/skills/dd-monitors, .github/skills/dd-monitors and .opencode/skills/dd-monitors in your project.

What does Dd Monitors need to run?

Going by SKILL.md and its folder, Dd Monitors needs the command-line tools its instructions call (jq). Our summary lists: Python 3.

Does Dd Monitors access the network?

SKILL.md names 1 domain. As links in the text: docs.datadoghq.com. This is read from the text; nothing was executed.

Is Dd Monitors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dd Monitors use?

Dd Monitors is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dd Monitors use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dd Monitors?

Skills that share tags, products or a category with Dd Monitors: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dd Monitors?

datadog-labs (a GitHub organization) maintains it in datadog-labs/agent-skills, which has 177 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 8, 2026.

Source: datadog-labs/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dd Monitors

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Datadog Monitors

Prerequisites

Command Execution Order (Token-Efficient)

Quick Start

Common Operations

List Monitors

Get Monitor

Create Monitor

Silence Alerts (Downtime)

Monitor Creation Best Practices

1. Avoid Alert Fatigue

2. Use Proper Scoping

3. Set Recovery Thresholds

4. Include Context in Messages

NEVER Delete Monitors Directly

Monitor Types

Audit Monitors

Downtime vs Muting

Failure Handling

References

Files

Compare with similar skills

Similar skills

More from datadog-labs/agent-skills

Related

Questions about Dd Monitors