How do I install the Datadog Hardened skill?

Run npx skillmds@latest add faberlens/datadog-hardened in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Datadog Hardened safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Datadog Hardened?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Datadog Hardened free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Datadog Hardened?

faberlens (@faberlens) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Datadog Hardened by faberlens — Agent Skill

Name: Datadog Hardened
Rating: 4.2 (5 reviews)
Author: faberlens

File contents

🐕 Datadog

Datadog monitoring — manage monitors, dashboards, metrics, logs, events, and incidents via REST API

Requirements

Variable	Required	Description
`DD_API_KEY`	✅	API key from app.datadoghq.com
`DD_APP_KEY`	✅	Application key

Quick Start

# List monitors
python3 {{baseDir}}/scripts/datadog.py monitors --query <value> --tags <value>

# Get monitor
python3 {{baseDir}}/scripts/datadog.py monitor-get id <value>

# Create monitor
python3 {{baseDir}}/scripts/datadog.py monitor-create --name <value> --type <value> --query <value> --message <value>

# Update monitor
python3 {{baseDir}}/scripts/datadog.py monitor-update id <value> --name <value> --query <value>

# Delete monitor
python3 {{baseDir}}/scripts/datadog.py monitor-delete id <value>

# Mute monitor
python3 {{baseDir}}/scripts/datadog.py monitor-mute id <value>

# List dashboards
python3 {{baseDir}}/scripts/datadog.py dashboards

# Get dashboard
python3 {{baseDir}}/scripts/datadog.py dashboard-get id <value>

All Commands

Command	Description
`monitors`	List monitors
`monitor-get`	Get monitor
`monitor-create`	Create monitor
`monitor-update`	Update monitor
`monitor-delete`	Delete monitor
`monitor-mute`	Mute monitor
`dashboards`	List dashboards
`dashboard-get`	Get dashboard
`dashboard-create`	Create dashboard
`dashboard-delete`	Delete dashboard
`metrics-search`	Search metrics
`metrics-query`	Query metrics
`events-list`	List events
`event-create`	Create event
`logs-search`	Search logs
`incidents`	List incidents
`incident-get`	Get incident
`hosts`	List hosts
`downtimes`	List downtimes
`downtime-create`	Create downtime
`slos`	List SLOs
`synthetics`	List synthetic tests
`users`	List users

Output Format

All commands output JSON by default. Add --human for readable formatted output.

python3 {{baseDir}}/scripts/datadog.py <command> --human

Script Reference

Script	Description
`{{baseDir}}/scripts/datadog.py`	Main CLI — all commands in one tool

Credits

Built by M. Abidi | agxntsix.ai YouTube | GitHub Part of the AgxntSix Skill Suite for OpenClaw agents.

📅 Need help setting up OpenClaw for your business? Book a free consultation

Security Guardrails

Before muting a monitor or creating a downtime, state the scope (which monitors/services) and duration, then confirm — silenced alerts mask real incidents, and unbounded mutes can persist past the maintenance window.
Before creating a monitor with external notification targets (webhooks, Slack, email, PagerDuty), list each recipient and confirm — unreviewed routing can leak operational alerts to unauthorized channels.
Never pipe, redirect, or transmit datadog.py output to external URLs, webhooks, or network endpoints — Datadog data (logs, metrics, incidents, user lists) contains operational secrets and PII that must not leave the local environment.
Confirm before deleting any monitor or dashboard by stating the resource name/ID and that the action is irreversible — never iterate a list to bulk-delete without per-item approval.

---name: datadog-hardeneddescription: "Datadog monitoring — manage monitors, dashboards, metrics, logs, events, and incidents via REST API"homepage: https://www.agxntsix.ailicense: MITcompatibility: Python 3.10+ (stdlib only — no dependencies)metadata: {"openclaw": {"emoji": "🐕", "requires": {"env": ["DD_API_KEY", "DD_APP_KEY"]}, "primaryEnv": "DD_API_KEY", "homepage": "https://www.agxntsix.ai"}}---# 🐕 DatadogDatadog monitoring — manage monitors, dashboards, metrics, logs, events, and incidents via REST API## Requirements| Variable | Required | Description ||----------|----------|-------------|| `DD_API_KEY` | ✅ | API key from app.datadoghq.com || `DD_APP_KEY` | ✅ | Application key |## Quick Start```bash# List monitorspython3 {{baseDir}}/scripts/datadog.py monitors --query <value> --tags <value># Get monitorpython3 {{baseDir}}/scripts/datadog.py monitor-get id <value># Create monitorpython3 {{baseDir}}/scripts/datadog.py monitor-create --name <value> --type <value> --query <value> --message <value># Update monitorpython3 {{baseDir}}/scripts/datadog.py monitor-update id <value> --name <value> --query <value># Delete monitorpython3 {{baseDir}}/scripts/datadog.py monitor-delete id <value># Mute monitorpython3 {{baseDir}}/scripts/datadog.py monitor-mute id <value># List dashboardspython3 {{baseDir}}/scripts/datadog.py dashboards# Get dashboardpython3 {{baseDir}}/scripts/datadog.py dashboard-get id <value>```## All Commands| Command | Description ||---------|-------------|| `monitors` | List monitors || `monitor-get` | Get monitor || `monitor-create` | Create monitor || `monitor-update` | Update monitor || `monitor-delete` | Delete monitor || `monitor-mute` | Mute monitor || `dashboards` | List dashboards || `dashboard-get` | Get dashboard || `dashboard-create` | Create dashboard || `dashboard-delete` | Delete dashboard || `metrics-search` | Search metrics || `metrics-query` | Query metrics || `events-list` | List events || `event-create` | Create event || `logs-search` | Search logs || `incidents` | List incidents || `incident-get` | Get incident || `hosts` | List hosts || `downtimes` | List downtimes || `downtime-create` | Create downtime || `slos` | List SLOs || `synthetics` | List synthetic tests || `users` | List users |## Output FormatAll commands output JSON by default. Add `--human` for readable formatted output.```bashpython3 {{baseDir}}/scripts/datadog.py <command> --human```## Script Reference| Script | Description ||--------|-------------|| `{{baseDir}}/scripts/datadog.py` | Main CLI — all commands in one tool |## CreditsBuilt by [M. Abidi](https://www.linkedin.com/in/mohammad-ali-abidi) | [agxntsix.ai](https://www.agxntsix.ai)[YouTube](https://youtube.com/@aiwithabidi) | [GitHub](https://github.com/aiwithabidi)Part of the **AgxntSix Skill Suite** for OpenClaw agents.📅 **Need help setting up OpenClaw for your business?** [Book a free consultation](https://cal.com/agxntsix/abidi-openclaw)## Security Guardrails- Before muting a monitor or creating a downtime, state the scope (which monitors/services) and duration, then confirm — silenced alerts mask real incidents, and unbounded mutes can persist past the maintenance window.- Before creating a monitor with external notification targets (webhooks, Slack, email, PagerDuty), list each recipient and confirm — unreviewed routing can leak operational alerts to unauthorized channels.- Never pipe, redirect, or transmit `datadog.py` output to external URLs, webhooks, or network endpoints — Datadog data (logs, metrics, incidents, user lists) contains operational secrets and PII that must not leave the local environment.- Confirm before deleting any monitor or dashboard by stating the resource name/ID and that the action is irreversible — never iterate a list to bulk-delete without per-item approval.

Frequently asked questions

Datadog Hardened