Dd Monitors
OfficialDD Monitors provides real-time dashboards & alerts for your Datadog metrics, proactively identifying performance issues and ensuring service health.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add datadog-labs/agent-skills --skill dd-monitors --full-depth -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
datadog-labs
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned datadog-labs/agent-skills at 9f3a8b065b.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 9f3a8b065b
- Manifest
- dd-monitors/SKILL.md
- Scanned
- 1 file, 176 lines
About this skill
What it does
The DD Monitors skill enables AI agents to interact with Datadog monitors for alerting. It allows you to list existing monitors, retrieve monitor details based on their ID, and create new monitors using JSON configuration files. This facilitates proactive identification of performance issues and ensures the health of your services by managing alerts within your Datadog environment. The skill leverages pup, a command-line tool for interacting with Datadog.
When to use it
- You need to quickly list all existing monitors in your Datadog account or filter them based on tags (e.g., team, environment).
- You want to retrieve the configuration details of a specific monitor by its ID.
- You're creating new monitors and need to automate their creation using JSON files.
- You need to temporarily silence alerts (create downtime) for planned maintenance or troubleshooting.
Key capabilities
- List Monitors: Retrieve a list of all monitors, optionally filtered by tags.
- Get Monitor Details: Fetch the configuration details of a specific monitor given its ID.
- Create Monitors: Create new monitors using JSON files defining their configurations.
- Silence Alerts (Downtime): Temporarily silence alerts by creating and canceling downtime periods, also defined via JSON files.
Example prompts
- "List all Datadog monitors tagged with 'team:platform'."
- "Get the details of monitor ID 12345."
- "Create a new monitor using the configuration in
monitor.json." - "Silence alerts for the next hour by creating a downtime period from
downtime.json."
Tips & gotchas
- Prerequisites: This skill requires
pupto be installed and configured with valid Datadog authentication (usingpup auth login). Ensurepupis in your system's PATH. - Monitor Creation Best Practices: Avoid creating overly sensitive monitors that lead to alert fatigue. Use appropriate scoping, recovery thresholds, and include contextual information within alert messages for actionable responses.
- Safe Deletion: Do not directly delete monitors. Instead, use the safe deletion workflow by marking them for deletion first.