Index of every page on this site: llms.txt
Avatar for Datadog Labs

Datadog Labs

Datadog Labs repositories are experimental. They are NOT covered by the Datadog MSA or terms of service, and are not supported by Datadog.

75 skills 185 United States of America Synced

Mostly·datadog, apm, instrumentation

datadog-labs/agent-skills

Public repository for Datadog Agent Skills

75 skills 185
npx skilld add datadog-labs/agent-skills --all
  • 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 changes. Only use if no Datadog Agent is deployed on the cluster yet.

  • Run an iterative code-improvement hill-climb against real Datadog LLM-Obs data, locally, with Claude Code as the agent. Establishes a baseline eval, makes one focused change, re-scores with the same harness, keeps the change if it improves the score in the goal's direction (labeling within-noise gains tentative), and repeats. Use when the user says "run an auto experiment", "hill-climb this code", "iteratively improve X and measure the delta", "optimize this prompt/file against my traces", "auto-optimize against LLM-Obs", or wants the local equivalent of the auto_experiments worker. Works from an ml_app, a dataset_id, an annotation_queue_id (a queue of human-labelled interactions), a list of trace_ids, or (by exception) a local dataset file. The corpus and its val/test splits live in Datadog LLM-Obs Datasets, created once per run with a timestamp in their names.

  • Fit a Datadog LLM-Obs evaluator to human labels. Takes an annotation queue, works out where in the trace the labelled property actually lives, drafts an LLM-judge that predicts the human label, scores that judge against the already-labelled rows with a metric agreed with the user, then hill-climbs it — inspect the errors, make one focused change, re-score, keep it only if it beats the best — for a bounded number of iterations, and finally publishes the winner to Datadog as a DISABLED evaluator (not a Datadog draft — a real evaluator with `enabled: false`). Use when the user says "build an eval from my annotations", "build an evaluator from the annotation queue", "turn my annotations into an evaluator", "learn an evaluator from my labels", "fit a judge to the annotation queue", "auto-label", "auto labelling", "automate this annotation queue", "scale up my human labels", or wants the rest of a queue graded the way the humans graded the first rows. Needs an annotation queue with at least two classes present in the human labels (e.g. one true and one false for a boolean).

  • Bootstrap evaluators from production traces — by default propose online LLM-judge evaluators and, after you confirm, create them in Datadog as disabled drafts (never auto-enabled); on request emit Python SDK code or a framework-agnostic JSON spec instead. Use when user says "bootstrap evaluators", "generate evaluators", "create evals from traces", "eval bootstrap", "write evaluators", "build eval suite", "publish evaluators", or wants to generate BaseEvaluator/LLMJudge code or online judge configs from production LLM trace data. Works with ml_app and optional RCA report or failure hypothesis.

  • End-to-end Agent Observability pipeline for an instrumented ml_app — classify production traces, root-cause failures, bootstrap evaluators, then (optionally) sample + publish a dataset, generate + run an experiment, and analyze results. Six narrated phases with a standardized banner and a "continue" checkpoint between each. Pure orchestration over the agent-observability sub-skills (`agent-observability-session-classify`, `agent-observability-trace-rca`, `agent-observability-eval-bootstrap`, `agent-observability-experiment-bootstrap`, `agent-observability-experiment-analyzer`). Use when user says "run the eval pipeline", "go from traces to evals", "bootstrap evals end to end", "classify then RCA then bootstrap", "build an eval set from scratch", "onboard me to datasets and experiments", "walk me through experiments", "I have an ml_app, now what", "Agent Observability onboarding", "guided experiment setup", "from traces to experiments", or wants a deterministic, narrated tour from production data through evaluators, datasets, and experiments. Stop early with `--stop-after <phase>` to short-circuit at evaluators or dataset, or resume mid-flow with `--start-at <phase>`.

  • Analyze LLM experiment results. Handles single or comparative experiments, exploratory or Q&A modes. Use when user says "analyze experiment", "compare experiments", "analyze against baseline", or provides one or two experiment IDs for analysis.

  • Bootstrap a reproducible LLM Observability experiment through the Python ddtrace SDK or the Node dd-trace SDK. Use for experiment, dataset, evaluator, benchmark, regression, or LLM-as-a-judge scaffolding. The legacy Python invocation remains supported.

  • Load this skill when the user wants to run an online experiment (live-traffic A/B test) on an LLM application instrumented with Agent Observability: compare two versions of a prompt, model, or behavior using a Datadog feature flag, score metrics from evaluations, and cost and token metrics. Covers creating the flag, wiring the app, creating the experiment, attaching metrics, setting the traffic split, and starting it, including taking the change tested in an offline experiment onto live traffic. Triggers: online experiment, A/B test an LLM app, test a prompt change on live traffic, experiment with feature flag and evaluation score, start an online experiment from an offline experiment.

  • Use when a developer wants to iterate on ONE specific Agent Observability / LLM Obs trace whose output they didn't like — re-running that trace against their LOCAL code, seeing a concise diff of the old vs new output, and looping (change code → replay → diff) until satisfied. Invoked as /agent-observability-replay-trace <trace-id> [changes to test]. Signals: "replay this trace"; "iterate on a trace"; "this trace's output is wrong, fix it and re-run"; "re-run trace <id> with <change>"; pasting a trace id from the Agent Observability UI with a description of what to fix. It fetches the trace via the datadog-llmo MCP or the pup CLI, edits code, re-runs the app to emit a NEW trace, and diffs the two — no local server, no browser. For agents traced with ddtrace / LLM Obs (Python first-class), with JSON-serializable entry input. Do NOT use for: scored Experiments or the browser "Replay" button (that's agent-observability-replay-experiment), building an experiment from a dataset/CSV, writing evaluators, root-causing failed traces, or RUM/HTTP session replay.

  • Classify whether user intent was satisfied in a Datadog Agent Observability trace or session. Three modes: (1) session_id — classify a single CMD+I assistant session with RUM; (2) trace_id — classify a single Agent Observability trace without RUM; (3) ml_app — sample and classify multiple sessions or traces from a given LLM app. Output is compact by default (verdict + one-sentence reason). Use when evaluating satisfaction, classifying sessions/traces, labeling data, or generating signal for agent-observability-eval-pipeline or agent-observability-trace-rca.

  • Root cause analysis on production LLM traces. Diagnoses why an LLM application is failing — works from eval judge verdicts, runtime errors, or structural anomalies depending on what signals are present. Walks the span tree from symptom to root cause. Use when user says "what's wrong with my app", "why is my eval failing", "analyze errors", "root cause analysis", "diagnose failures", or wants to understand production failure patterns.

  • Audit what the Bits AI assistant (MCP server) has done in your Datadog org — tool calls by user, resources accessed, and anomaly flags for AI governance.

  • Generate auditor-ready compliance evidence from Datadog Audit Trail for SOC 2 and PCI DSS. Maps framework controls to specific query patterns and produces formatted output.

  • Investigate a Datadog product usage or cost spike by correlating Usage Metering data (when/what spiked) with Audit Trail config changes (who changed what in the preceding window).

  • Guides developers building Datadog Apps with TypeScript, React, and the @datadog/apps scaffolder and CLI. Use when a user wants to scaffold, run, debug, upgrade, build, upload, or publish a Datadog App, set up CI/CD, use OAuth or API/application key auth, trigger or poll Workflow Automation from a backend function, choose DDSQL or Action Catalog for backend data access, query app datastores with DDSQL, or migrate an existing app from another tool such as Backstage (a software template, scaffolder template, `template.yaml`, or custom plugin) into a Datadog App, including backend function troubleshooting.

  • Ensure the user has an authenticated Datadog account with a valid DD_API_KEY on the right region before any Datadog setup or instrumentation. Detects existing DD_API_KEY / DD_APP_KEY / DD_SITE, validates them against the Datadog API, and fixes the common wrong-region 403. If no usable key exists, signs the user in (OAuth) or creates a new account, then obtains and validates a key. Use this whenever a user needs a Datadog account or API key, hits a 403 / wrong-region error, or is about to run any Datadog *-setup or instrumentation skill.

  • Install the Datadog Agent on a Docker host - standalone Docker (Linux or Windows) or Docker Compose - with infrastructure metrics, container logs, APM trace intake, and DogStatsD on by default, plus optional live processes, tags, hostname, proxy, and container filtering, keeping the API key in a restricted env file rather than on the command line. Use when the user has Docker containers on a single server, wants to install Datadog on their Docker host, or wants to set up Datadog with Docker Compose. Does not install the Agent on Kubernetes or directly on a Linux, macOS, or Windows host (use dd-agent-install-kubernetes, dd-agent-install-linux, dd-agent-install-macos, or dd-agent-install-windows). Requires a Datadog account with a valid API key and application key; run `dd-account-setup` first if they are missing.

  • Install the Datadog Agent on a Kubernetes cluster - Amazon EKS (standard or Fargate profiles), Azure AKS, Google GKE (standard or Autopilot), OpenShift, Oracle OKE, VMware Tanzu (TKG), Rancher (RKE2/K3s), or self-managed - through the Datadog Operator (kubectl/Helm), the Datadog Helm chart, or Terraform, with metrics, logs, and APM trace intake on by default, Single Step Instrumentation off unless the user asks, and optional products; for an SSI-first install use `dd-apm/k8s-ssi` `agent-install`. Use when the user is running a Kubernetes cluster on GKE, EKS, AKS, OpenShift, OKE, or TKG, asks to install or set up the Datadog Agent on Kubernetes, wants to install the Agent with Terraform, or wants to monitor their Kubernetes pods. Does not connect a cloud provider integration or install the Agent on standalone hosts or plain Docker. Requires a Datadog account with a valid API key and application key; run `dd-account-setup` first if they are missing.

  • Install the Datadog Agent on Linux hosts - a single machine or a fleet - with support for cloud rollouts (AWS Systems Manager, GCP VM Manager, Azure Run Command), remote configuration management, proxy, FIPS, custom tags, and advanced configuration, with infrastructure metrics, logs, and the APM trace receiver on by default and host Single Step Instrumentation only when the user asks (for an SSI-first request, use `dd-apm/linux-ssi` `agent-install`). Use when the user wants to monitor their Linux servers, install the Datadog Agent on an Ubuntu or other Linux host, or roll the Agent out to an EC2 or other cloud VM fleet without SSHing in. Does not install the Agent on Windows, macOS, Docker, or Kubernetes (use dd-agent-install-windows, dd-agent-install-macos, dd-agent-install-docker, or dd-agent-install-kubernetes) and does not connect a cloud provider integration. Requires a Datadog account with a valid API key and application key; run `dd-account-setup` first if they are missing.

  • Install the Datadog Agent on a macOS machine with the macOS installer, with infrastructure metrics, logs, and APM trace intake on by default, plus optional live processes, APM instrumentation, custom tags, and service management. Use when the user wants to install the Datadog Agent on their Mac, set up Datadog on macOS, or monitor a macOS developer or CI machine with Datadog. Does not install the Agent on Linux, Windows, Docker, or Kubernetes (use dd-agent-install-linux, dd-agent-install-windows, dd-agent-install-docker, or dd-agent-install-kubernetes) and does not target managed cloud fleets. Requires a Datadog account with a valid API key and application key; run `dd-account-setup` first if they are missing.

  • Install the Datadog Agent on Windows Server hosts - a single machine or a fleet - with support for cloud rollouts (AWS Systems Manager, GCP VM Manager, Azure Run Command), MSI properties, FIPS, custom tags, and advanced configuration, with infrastructure metrics, logs, and APM trace intake on by default. Use when the user wants to install the Datadog Agent on a Windows server, deploy Datadog to their Windows VMs, or set up the Datadog Agent on Windows Server 2022 or another Windows Server version. Does not install the Agent on Linux, macOS, Docker, or Kubernetes (use dd-agent-install-linux, dd-agent-install-macos, dd-agent-install-docker, or dd-agent-install-kubernetes) and does not connect a cloud provider integration. Requires a Datadog account with a valid API key and application key; if they are missing, run `dd-account-setup` first on commercial sites, or supply them directly on government sites.

  • Route Datadog Android SDK upgrades to the migration instructions for the project's current and target major versions.

  • Connects Anthropic to Datadog so the user can see Claude usage and cost data — organization-wide usage on the Platform plan, per-user usage on the Enterprise plan, and costs in Cloud Cost Management when enabled. Guides creating the key the plan needs, entered in a separate secure prompt where the agent never sees it, and verifies that usage data is actually arriving. Use when the user wants Anthropic or Claude API usage and cost data in Datadog, or asks to connect, configure, or repair the Datadog Anthropic Usage and Costs integration. Not for tracing Anthropic SDK calls in an application; use dd-instrument-llmo for LLM Observability.

  • APM - install, onboard, instrument, enable, set up, configure, traces, services, dependencies, performance analysis, Data Streams Monitoring (DSM), queue lag, pipeline latency. Use for any request involving Datadog APM setup, instrumentation (SSI, ddtrace, agent install), or analysis.

  • Audit Trail investigations - who changed what, key compromise, cost spike root cause, compliance evidence (SOC 2/PCI), and AI activity auditing.

  • Set up Datadog Cloud Cost Management for AWS by configuring a Cost and Usage Report - either CUR 2.0 (recommended) or a Legacy CUR - and provisioning the S3 bucket, bucket policy, IAM read policy, role attachment, and Datadog registration with Terraform. Use when the user wants to track their AWS cloud costs, set up cost and usage reports, set up Cloud Cost Management (CCM) for AWS, set up CCM with CUR 2.0, or connect an AWS Data Export to Datadog. Does not connect a new AWS account to Datadog and does not set up cost management for other clouds. Requires an existing role-based Datadog AWS integration; run `dd-aws-integration` first if it is missing.

  • 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 registers the account through datadog_integration_aws_account so AWS metrics, the resource catalog, and CSPM findings start flowing. Use when the user has AWS resources they want to monitor, wants to connect an AWS account to Datadog, asks to set up or repair the AWS integration, or needs the Datadog IAM role and external ID provisioned. Does not set up log forwarding.

  • Set up AWS log forwarding to Datadog with Terraform - deploys the Datadog Forwarder Lambda in the user's AWS account, seeds the Datadog API key into a Secrets Manager secret out-of-band so it never lands in Terraform state, and registers the forwarder ARN on the existing AWS integration so Datadog automatically subscribes CloudWatch log groups and S3 buckets. Use when the user wants to forward AWS logs to Datadog, send CloudWatch logs to Datadog, or set up the Datadog Forwarder Lambda. Does not create the AWS integration itself or set up metrics collection. Requires the Datadog AWS integration (datadog_integration_aws_account); run `dd-aws-integration` first if it is missing.

  • Set up Datadog Storage Management for AWS S3 by configuring S3 Inventory on the buckets the user picks and provisioning the destination buckets, destination bucket policy, Datadog read policy, and Storage Management sync with the DataDog/storage-management-datadog/aws Terraform module, including multi-Region and SSE-KMS destinations and optional S3 access logs. Use when the user wants to set up Storage Management for their S3 buckets, monitor their S3 storage in Datadog, or enable S3 storage management. Does not connect a new AWS account to Datadog and does not deploy the Datadog Forwarder Lambda (that is `dd-aws-log-forwarding`). Commercial AWS partition only; there is no supported setup for AWS GovCloud or China. Requires an existing role-based Datadog AWS integration; run `dd-aws-integration` first if it is missing.

  • Set up Datadog Cloud Cost Management for Azure with Terraform - provisions (or reuses) a Storage Account and Container, creates the actual-cost and amortized-cost Cost Management exports, grants the existing Datadog app registration read access through role assignments, and registers the exports with Datadog through datadog_azure_uc_config in a two-phase apply around the manual file-partitioning step. Use when the user wants to track their Azure cloud costs, asks to set up Azure cost exports for Datadog, or asks to set up Cloud Cost Management for Azure. Does not create the Azure integration or its app registration / service principal. Requires an existing Datadog Azure integration; run `dd-azure-integration` first if it is missing.

  • Set up the Datadog Azure integration with Terraform - creates an Entra ID app registration and service principal, assigns Monitoring Reader across the chosen subscriptions and management groups, grants the Microsoft Graph permissions Datadog needs for resource discovery, and registers the tenant so Azure metrics and resource collection start flowing. Use when the user wants to monitor Azure VMs, App Service, SQL Database, or AKS, wants to connect an Azure subscription or management group or tenant to Datadog, or asks to set up or repair the Azure integration. Does not set up log forwarding.

  • Set up automated Azure log forwarding to Datadog by running Datadog's official Log Forwarding Orchestrator (LFO) install script through the Azure CLI - deploys the managed control plane that auto-discovers resources across the monitored subscriptions and provisions and scales the log forwarders itself, with no per-resource diagnostic settings. Use when the user wants to forward Azure logs to Datadog, send Azure resource logs to Datadog, or set up Azure log forwarding. Does not generate Terraform and does not create the Azure integration or set up metrics collection. Requires the Datadog Azure integration; run `dd-azure-integration` first if it is missing.

  • Datadog Browser SDK — RUM, Logs, Session Replay, profiling, product analytics, and error tracking setup, configuration, and migration. Use when upgrading Browser SDK versions, setting up RUM or Logs, or troubleshooting browser-side Datadog instrumentation.

  • Set up the Datadog Confluent Cloud integration - create a Cloud resource management API key in Confluent Cloud (with the Confluent CLI or the console), register the account with Datadog, discover and register its Kafka clusters, connectors, ksqlDB and Schema Registry resources, and optionally add Schema Registry tags and Cloud Cost Management. Use when the user wants to monitor Confluent Cloud Kafka clusters, set up the Datadog Confluent Cloud integration, connect Confluent Cloud to Datadog, see Confluent metrics in Datadog, or monitor Kafka clusters on Confluent. Does not set up self-managed Kafka or the Datadog Agent. Requires a Datadog API key and application key; run `dd-account-setup` first if they are missing.

  • Set up Datadog Database Monitoring (DBM) for a standalone PostgreSQL instance on AWS RDS (not Aurora) - enable pg_stat_statements on the instance's parameter group, then deploy a managed Agent with CloudFormation, provision one with Terraform, or configure an existing Agent, plus the read-only datadog monitoring user. Use when the user wants to set up Database Monitoring for an RDS Postgres database, monitor query performance on a Postgres RDS instance, enable DBM for Postgres on RDS, or use Terraform to set up DBM for an RDS Postgres database. Not for Aurora PostgreSQL (including Serverless v2), RDS Multi-AZ DB clusters, or read replicas - do not use it to plan their setup; explain why and point the user at the DBM docs instead. Requires the Datadog AWS integration for the AWS account that holds the instance; run `dd-aws-integration` first if it is missing.

  • Look up Datadog documentation, limits, and feature availability. Prefer search_datadog_documentation when that MCP tool is available, then one Markdown page from docs.datadoghq.com/llms.txt. For API reference, use pup docs api.

  • Set up Datadog Cloud Cost Management for GCP - enables the BigQuery and BigQuery Data Transfer APIs, walks the user through the Cloud Billing detailed-usage export to BigQuery, then uses Terraform to provision the GCS bucket and the predefined IAM role bindings Datadog documents for the Datadog service account, and registers the cost config through datadog_gcp_uc_config. Use when the user wants to track their GCP cloud costs, asks to set up a GCP billing export for Datadog, or asks to set up Cloud Cost Management for GCP. Does not create the GCP integration or the Datadog service account itself. Requires an existing Datadog GCP integration; run `dd-gcp-integration` first if it is missing.

  • Set up the Datadog Google Cloud integration with Terraform - creates a service account in the host project, lets Datadog's delegate principal impersonate it via roles/iam.serviceAccountTokenCreator (no service-account keys), enables the required APIs, grants the monitoring roles across the chosen projects and folders, and registers the account through datadog_integration_gcp_sts. Use when the user wants to monitor GCP resources such as Compute Engine, Cloud SQL, GKE, Cloud Run, or Pub/Sub, wants to connect a GCP project or folder or organization to Datadog, or asks to set up or repair the GCP integration. Does not set up log forwarding.

  • Set up GCP log forwarding to Datadog with Terraform - creates a Dataflow pipeline running Google's Cloud_PubSub_to_Datadog template, fed by log sinks on the chosen projects and/or folders through a Pub/Sub topic and subscription, with a dead-letter queue, a GCS staging bucket, and Secret Manager holding a dedicated Datadog API key. Use when the user wants to forward GCP logs to Datadog, set up GCP log forwarding, or send Cloud Logging to Datadog. Does not create the GCP integration itself or set up metrics collection. Requires the Datadog GCP integration; run `dd-gcp-integration` first if it is missing.

  • Connects GitHub Copilot to Datadog so the user can see Copilot usage and license metrics for the GitHub organizations they own. Checks whether a Copilot account is already connected first; confirms which GitHub account will be connected and which organizations it collects, and verifies those organizations allow usage-metrics collection before connecting. Can also remove a connected account for cleanup. Use when the user wants Copilot usage metrics in Datadog, or asks to connect or configure the Datadog GitHub Copilot integration. Not for Copilot billing or cost data in Cloud Cost Management (use dd-github-costs-onboarding), or for code in stack traces and pull request comments (use dd-github-onboarding).

  • Bring a GitHub enterprise's or organization's bill — Actions, Packages, Copilot, storage, and other metered products — into Datadog Cloud Cost Management through the Datadog GitHub Costs integration. Shows which enterprises and organizations the user can connect, guides creating the GitHub token the integration needs (entered where the agent never sees it), and warns before connecting an enterprise together with one of its organizations, which would count those costs twice. Use when the user wants GitHub billing or cost data (Actions, Packages, Copilot, storage) in Datadog Cloud Cost Management, or asks to connect or configure the Datadog GitHub Costs integration. Not for Copilot usage or seat metrics (use dd-github-copilot-onboarding) or for code links and PR comments through the GitHub App (use dd-github-onboarding).

  • Connect GitHub to Datadog through the Datadog GitHub App so Datadog can show source code in stack traces and comment on pull requests. Checks whether a GitHub account is already connected first; the user installs the app on the GitHub organization or account they choose, and the skill verifies what the connection unlocked. Optionally also adds a `service.datadog.yaml` to a repository so its services appear in Datadog's Software Catalog. Use when the user wants to connect or configure the Datadog GitHub integration, code snippets in stack traces, or Datadog feedback on pull requests. Not for GitHub Copilot usage metrics (use dd-github-copilot-onboarding) or GitHub billing and costs in Cloud Cost Management (use dd-github-costs-onboarding).

  • Sets up Datadog Browser Error Tracking for a web app that runs the Datadog RUM Browser SDK. Turns error processing on for the app's RUM application, forwards framework-caught errors (React, Next.js, Vue, Angular, SvelteKit) to Datadog, and checks that events arrive. Use when asked to add, set up, enable or verify Error Tracking or frontend exception tracking in a browser app. Not for adding RUM itself, which dd-instrument-rum does first, or for uploading source maps, which dd-browser-sdk does.

  • Instrument the current project with Datadog LLM Observability for Python or Node.js/Next.js backends that call LLMs or run AI agents. Detects the runtime and LLM framework, provisions credentials, adds SDK init (ddtrace/dd-trace) with the correct kwargs, persists the dependency into the deploy manifest, and audits session-ID plumbing for gaps — fixing them when found. Use when the user says "instrument this project with LLM Observability", "add LLM Observability", "monitor my AI app in Datadog", "add LLM spans", "add agent session tracking", or "verify/repair my LLM Observability setup".

  • Switches on Datadog Product Analytics (funnels, retention, pathways, user journeys) for a browser app that runs the Datadog RUM Browser SDK. Turns the product on for the app's RUM application, ties sessions to signed-in users with setUser, and checks that events arrive. Use when asked to add, set up, enable or verify Product Analytics or user-behavior analytics in a web frontend. Not for adding RUM itself, which dd-instrument-rum does first, or for mobile apps.

  • Instrument browser-based web applications with Datadog Browser RUM. Detect the application framework, router, package manager, bundler, entrypoint, credentials, and existing RUM setup; add or safely complete classic Browser RUM instrumentation for React, Next.js App or Pages Router, Angular, Vue, Nuxt, Svelte, vanilla JavaScript, SPAs, and iframe-hosted apps; avoid duplicate initialization; and verify the application still builds. Use when asked to add, set up, instrument, repair, or verify Datadog RUM, Browser Monitoring, Session Replay, or framework-specific Browser RUM plugins.

  • Sets up Datadog Test Optimization (CI test visibility, per-test traces, flaky test detection) in a repo's CI pipeline for Node.js, Python, Java/JVM, Go, Ruby, .NET, Swift, or JUnit XML. Configures CI auto-instrumentation or manual test tracers, forwards container variables, and checks that test events arrive. Use when asked to add, set up, enable or verify Test Optimization or CI test visibility. Not for triaging flaky tests or unblocking a failing PR; use triage-flaky-test or unblock-pr.

  • Log management - search, archives, metrics, and cost control.

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

  • Connect a Nebius Cloud tenant to Datadog so its log streams — Kubernetes, PostgreSQL, Compute, applications, MLflow, and more — are collected through the Datadog Nebius Cloud integration. Creates the Nebius service account and keys the integration needs, and registers and verifies the integration. Use when the user wants to collect Nebius Cloud logs, connect a Nebius tenant to Datadog, or set up or repair the Datadog Nebius Cloud integration.

  • Set up Datadog Cloud Cost Management for Oracle Cloud Infrastructure (OCI) by enabling cost collection on an integrated parent tenancy - an API toggle on the existing tenancy integration, with no Terraform, storage buckets, exports or extra IAM policies. Use when the user wants to track their OCI cloud costs or asks to set up Cloud Cost Management for OCI. Does not create the OCI tenancy integration itself and does not provision any infrastructure. Requires an existing Datadog OCI integration; run `dd-oci-integration` first if it is missing.

  • Set up the Datadog Oracle Cloud Infrastructure (OCI) integration with Terraform - verifies ~/.oci/config, then applies Datadog's official oracle-cloud-integration module to create the Datadog service user, group, IAM policies, and API key in the tenancy and register it with Datadog, optionally including log collection. Use when the user has Oracle Cloud resources, wants to monitor an OCI tenancy, wants to connect OCI to Datadog, or asks to set up or repair the OCI integration.

  • Connects OpenAI to Datadog so the user can see organization-wide OpenAI API usage metrics and OpenAI costs in Cloud Cost Management (on by default). Guides creating the OpenAI admin key the integration needs (organization owners only), entered in a separate secure prompt where the agent never sees it, and verifies that usage data is actually arriving. Use when the user wants OpenAI API usage and cost data in Datadog, or asks to connect, configure, or repair the Datadog OpenAI integration. Not for tracing OpenAI calls from application code, which LLM Observability covers.

  • Entry point for Datadog onboarding. Takes a developer's plain-language goal, ensures a valid Datadog account with dd-account-setup, asks dd-product-recommender which products fit, detects the project's platform and cloud, then composes an ordered plan across the existing skills (agent install, product enable, verify, and optional cloud integration) and dispatches to each by source URL — honestly flagging products with no skill yet. Use when the user says "set up Datadog", "onboard my app / this repo to Datadog", "instrument my project", or states a monitoring goal without naming a specific product or skill.

  • Connects PagerDuty to Datadog so Datadog monitors can trigger and resolve incidents on the user's PagerDuty services. Checks which PagerDuty services are already connected first and asks whether to continue; the user picks the services to connect on PagerDuty's own install screen, the skill confirms they landed, and it can send a test page that opens and resolves a real incident. Use when the user wants PagerDuty alerts/notifications from Datadog, or asks to connect or configure the Datadog PagerDuty integration.

  • Recommends the right Datadog products for a codebase and/or a stated goal — grounded in a tech-stack→product map and a use-case→product map built from Datadog product capabilities and common technology patterns. Recommendation only; no setup instructions. Use when a user asks which Datadog products fit their app, what to monitor, or which products serve a goal like security, cost, or LLM observability.

  • Set up Datadog Continuous Profiler for a service in the local repository. Detect the language, runtime, and how the service is deployed, check the Datadog Agent and SDK prerequisites, add the profiler dependency and enablement settings (Java, Python, Go, Ruby, Node.js, .NET, PHP), and verify profiles arrive. Use when asked to enable, set up, install, configure, or turn on Datadog profiling or the Continuous Profiler, or when profiles are missing after setup.

  • Datadog CLI (pup) for Datadog app URLs and API operations, including notebooks, dashboards, metrics, logs, monitors, traces, and SLOs. Use pup instead of browser automation for those links.

  • Connects a commercial Slack workspace to Datadog and adds a channel to it, so the user can receive Datadog alerts and notifications in Slack and talk to Datadog by mentioning @Datadog. Checks whether a Slack workspace is already connected first, and can add a channel to an existing connection without reconnecting the workspace. Slack for Government (govcloud) workspaces are pointed to the Datadog UI instead, since this flow covers commercial workspaces only. Use when the user wants Slack alerts/notifications from Datadog, wants to message @Datadog in Slack, or asks to connect or configure the Datadog Slack integration. Not for creating monitors or routing specific alerts to the channel.

  • Enable Data Streams Monitoring (DSM) on services already instrumented with APM, for end-to-end latency, throughput, and consumer lag across Kafka, RabbitMQ, SQS, SNS, Kinesis, Pub/Sub, IBM MQ, Azure Service Bus, and BullMQ pipelines. Use when the user asks for data streams, queue lag, pipeline latency, or Kafka monitoring, or when an APM install finds an event-driven, async microservice, or Lambda-based system.

  • Enable Single Step Instrumentation (SSI) on Kubernetes — automatically instruments applications for APM without code changes. Only use if the Datadog Agent is already running on the cluster — if not, use agent-install first.

  • Investigate a potentially compromised Datadog API key — timeline of actions, geo/IP breakdown, endpoints called, anomaly flags, and remediation steps.

  • Generate a live Single Step Instrumentation (SSI) onboarding confirmation report — verifies APM instrumentation is working end-to-end with deep links into the Datadog UI. Only use after agent-install and enable-ssi have both completed successfully.

  • Generate a BYOD ownership preferences reference table for a customer. Walks through preference types, generates CSV, and provides upload instructions (UI, API, cloud storage, or Terraform). Use when asked about BYOD setup, preferences reference table, k9_ownership_preferences, or ownership customization.

  • Answer "who did what" security questions from Audit Trail — deletions, config changes, login activity, permission changes, actions from a specific user or IP.

  • Create and manage APM service remapping rules — rewrite service names at ingestion time to collapse noisy inferred entities, clean up auto-generated names, handle org renames, or normalize naming conventions. Use for any request involving service renaming, service mapping, inferred service cleanup, peer.service normalization, or collapsing fragmented service names.

  • Configure build-time JavaScript sourcemap upload to Datadog using the Datadog build plugin (@datadog/esbuild-plugin, @datadog/rollup-plugin, @datadog/rspack-plugin, @datadog/vite-plugin, @datadog/webpack-plugin), so RUM and Error Tracking show un-minified stack traces with git metadata attached. Use when errors in Datadog show minified stack traces, when asked to "upload sourcemaps", "set up sourcemaps", "unminify errors", or "configure the Datadog build plugin", or when a project has a bundler config and @datadog/browser-rum but no sourcemap upload.

  • Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.

  • Diagnose and fix Single Step Instrumentation (SSI) issues on Kubernetes — SSI automatically instruments applications for APM without code changes. Only use if the agent and SSI are already configured but traces are missing or instrumentation is not working.

  • Load when investigating a failing PR CI pipeline or checking PR health. Attributes each CI failure as flaky, infra, or regression, proposes a targeted action, and reports code coverage and quality/security status.

  • Upgrade an Android application from Datadog's v2 mobile RUM SDK to the latest stable v3 SDK, including Core, RUM, Logs, Trace, OkHttp, and Session Replay breaking changes.

  • Upgrade Datadog Browser SDK from v4 to v5. Use when encountering removed options like proxyUrl, sampleRate, replaySampleRate, premiumSampleRate, allowedTracingOrigins, or deprecated APIs like addRumGlobalContext, removeUser, or when a project references datadoghq-browser-agent.com CDN with /v4/ paths.

  • Upgrade Datadog Browser SDK from v5 to v6. Use when encountering removed options like useCrossSiteSessionCookie, sendLogsAfterSessionExpiration, or when dropping IE11 support, or when a project references datadoghq-browser-agent.com CDN with /v5/ paths.

  • Upgrade Datadog Browser SDK from v6 to v7. Use when encountering removed options like betaEncodeCookieOptions, allowFallbackToLocalStorage, trackBfcacheViews, usePciIntake, changed APIs like forwardErrorsToLogs, startDurationVital, stopDurationVital, or when a project references datadoghq-browser-agent.com CDN with /v6/ paths.

  • Verify Single Step Instrumentation (SSI) is working end-to-end on Kubernetes — SSI automatically instruments applications for APM without code changes. Only use after enable-ssi has run.

Skills published by Datadog Labs. Checked GitHub just now