datadog-notebooks

Creates Markdown-based DaDragon notebook runbooks for incident management.

Updated Mar 16, 2026

Search Tags:#templates #markdown #observability #notebooks #datadog #runbooks #incident-response

Ready to run

npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill datadog-notebooks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: datadog-notebooks
Source: https://github.com/javiertelioz/my-personal-marketplace/tree/main/plugins/datadog-notebooks/skills/datadog-notebooks
Command: npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill datadog-notebooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and author Datadog notebook runbooks in Markdown to capture incident investigation steps, signals, and governance, enabling responders to translate knowledge into repeatable, actionable workflows.

Core Features & Use Cases

designs runbooks for recurring incident patterns such as high error rate, latency spikes, provider timeouts, and queue lag
asks for the minimum context needed to make the runbook operational
scans the codebase when available to infer service boundaries, dependencies, and likely failure domains
produces the actual notebook Markdown
uses reusable placeholders when real telemetry names are not confirmed
keeps the output aligned with Datadog notebook authoring patterns

Quick Start

Draft a Datadog notebook runbook in Markdown using the recommended frontmatter and sections.

Frequently Asked Questions about datadog-notebooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create Datadog notebook runbooks in Markdown for incident response?▼

Datadog notebook runbooks are Markdown documents that standardize incident triage by outlining signals, mitigation steps, and escalation criteria. They translate investigation knowledge into repeatable, actionable workflows using frontmatter-driven templates for responders across services.

What is the best way to structure a Datadog notebook runbook for recurring incident patterns?▼

The best way to structure a Datadog notebook runbook is using frontmatter-driven templates with standardized sections. This format captures governance guidance, mitigation steps, and escalation criteria for recurring incidents like latency spikes, high error rates, and queue lag.

Do I need confirmed telemetry names to draft a Datadog notebook runbook?▼

You do not need confirmed telemetry names to draft a Datadog notebook runbook. The drafting process uses reusable placeholders when real telemetry names are not confirmed, keeping the output aligned with Datadog notebook authoring patterns while remaining operational.

Can I generate incident response runbooks by scanning my codebase for service boundaries?▼

You can generate incident response runbooks by scanning your codebase when available. The process infers service boundaries, dependencies, and likely failure domains, asking for the minimum context needed to make the runbook operational for responders.

What recurring incident patterns can I document using Datadog notebook runbooks?▼

You can document recurring incident patterns such as high error rates, latency spikes, provider timeouts, and queue lag. Datadog notebook runbooks standardize the triage process by outlining specific signals, mitigation steps, and escalation criteria for these failure domains.