
Dd Docs
Let your coding agent fetch accurate Datadog product docs, limits, and Markdown pages via docs.datadoghq.com/llms.txt instead of hallucinating observability APIs.
Overview
dd-docs is an agent skill most often used in Operate (also Build, Grow) that locates Datadog documentation and limits via docs.datadoghq.com/llms.txt and linked Markdown pages.
Install
npx skills add https://github.com/datadog-labs/agent-skills --skill dd-docsWhat is this skill?
- Uses Datadog’s llms.txt index for LLM-friendly doc discovery
- grep-style topic search across monitors, APM, logs, and related pages
- Fetches raw Markdown by appending .md to most docs.datadoghq.com URLs
- Surfaces official limits and product boundaries from linked documentation
- Versioned Datadog Labs agent-skills package (metadata 1.0.0)
- Official index at https://docs.datadoghq.com/llms.txt
- Skill metadata version 1.0.0
Adoption & trust: 752 installs on skills.sh; 127 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent invents Datadog configuration steps or quota details because it cannot reliably find the current official docs.
Who is it for?
Indie SaaS operators and builders integrating Datadog who want agents to ground answers in docs.datadoghq.com sources.
Skip if: Teams not using Datadog or anyone needing live metric queries and dashboard edits without reading docs first.
When should I use this skill?
Invoke when you need to locate Datadog documentation, product overviews, or limits using docs.datadoghq.com/llms.txt and linked Markdown pages.
What do I get? / Deliverables
The agent returns links and Markdown excerpts from Datadog’s llms.txt index and doc URLs so monitors, APM, and logs setup follow published guidance.
- Relevant Datadog doc URLs and summaries
- Markdown excerpts from specific product pages
- Cited limits or configuration notes from official docs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Datadog is primarily an operate-time observability stack, so the canonical shelf is Operate even when you configure it earlier in the journey. Monitoring matches APM, logs, metrics, and monitors documentation—the main topics indexed in llms.txt.
Where it fits
Pull tracing.md while adding APM instrumentation to a Node API.
Verify monitor and SLO doc limits before go-live checklists.
grep llms.txt for alert configuration when paging rules misfire.
Cross-check logs documentation when defining product analytics pipelines.
How it compares
A docs-lookup skill over HTTP, not a Datadog MCP server or Terraform deploy bundle.
Common Questions / FAQ
Who is dd-docs for?
Solo builders and small teams using Claude Code, Cursor, or Codex who need Datadog product and limits documentation pulled from the official llms.txt index.
When should I use dd-docs?
In Build while designing tracing and logging integrations, in Operate when configuring monitors and triaging observability gaps, and in Grow when aligning analytics events with Datadog log pipelines.
Is dd-docs safe to install?
The skill only guides fetching public documentation URLs; review the Security Audits panel on this Prism page and avoid piping agent-suggested curl into environments that mishandle secrets.
SKILL.md
READMESKILL.md - Dd Docs
# Datadog Docs Use this skill to locate Datadog documentation and limits. ## LLM-Friendly Documentation Datadog provides an LLM-optimized documentation index at: ``` https://docs.datadoghq.com/llms.txt ``` This file contains: - Overview of all Datadog products organized by use case - Full list of documentation pages with URLs and descriptions - Direct links to Markdown sources (append `.md` to URLs) ### How to Use llms.txt 1. **Fetch the index** to understand available documentation: ```bash curl -s https://docs.datadoghq.com/llms.txt | head -100 ``` 2. **Search for specific topics**: Examples: ```bash curl -s https://docs.datadoghq.com/llms.txt | grep -i "monitors" curl -s https://docs.datadoghq.com/llms.txt | grep -i "apm" curl -s https://docs.datadoghq.com/llms.txt | grep -i "logs" ``` 3. **Fetch specific doc pages** (add .md to most Datadog Docs URLs for raw content): ```bash curl -s https://docs.datadoghq.com/monitors.md curl -s https://docs.datadoghq.com/tracing.md ``` ### Key Documentation Sections | Topic | URL | |-------|-----| | APM/Tracing | https://docs.datadoghq.com/tracing/ | | Logs | https://docs.datadoghq.com/logs/ | | Metrics | https://docs.datadoghq.com/metrics/ | | Monitors | https://docs.datadoghq.com/monitors/ | | Dashboards | https://docs.datadoghq.com/dashboards/ | | Security | https://docs.datadoghq.com/security/ | | Synthetics | https://docs.datadoghq.com/synthetics/ | | RUM | https://docs.datadoghq.com/real_user_monitoring/ | | Incidents | https://docs.datadoghq.com/service_management/incident_management/ | | API Reference | https://docs.datadoghq.com/api/ | ## Scope Guardrails - Use llms.txt for documentation lookups - Defer to official docs for feature availability and limits ## Failure Handling - If docs.datadoghq.com is unreachable, check network connectivity - For region-specific docs, use appropriate site (datadoghq.eu, etc.)