datadog-agentic-plugins
A curated library of agentic plugins and skills for Claude that guide prospects and customers through setting up, instrumenting, and validating a Datadog proof of concept across any tech stack.
Each plugin represents a technology domain — an infrastructure platform, a programming language, a database engine, or a message queue. Each skill within a plugin is a focused, version-aware procedure that Claude can execute: provisioning a cluster, installing the Datadog Agent, instrumenting a Spring Boot app, enabling Database Monitoring, or validating that telemetry is flowing.
Prospects pick the plugins that match their stack. Claude reads the relevant skills, adapts to their specific versions, and walks them through setup step by step — from zero to traces, metrics, and logs in Datadog. Disclaimer: this marketplace is not endorsed by Datadog - the plugins are unofficial.
Table of Contents
Who This Is For
Prospects and customers use this repository during a Datadog PoC. You select the plugins that match your infrastructure, languages, databases, and queues. Claude loads the relevant skills and guides you through setup, instrumentation, and validation — adapted to your exact versions and configuration.
Datadog Solutions Engineers contribute to this repository. You author and maintain the plugins, skills, reference variants, validation scripts, and sample applications. Each contribution makes the PoC experience faster and more reliable for the next prospect. See the Contributing section for how to add or improve plugins and skills.
How to use this marketplace and plugins with Claude Code
Add the plugin:
claude plugin marketplace add https://github.com/jek-bao-choo/datadog-agentic-plugins
Start Claude then add the plugin
/plugin marketplace add https://github.com/jek-bao-choo/datadog-agentic-plugins
/plugin install quickstart@datadog-agentic-plugins
/reload-plugins
/quickstart:menu
Architecture Overview
The repository is a Claude Code marketplace registered via .claude-plugin/marketplace.json at the repo root. Each plugin is a directory with its own .claude-plugin/plugin.json manifest (required by Claude Code) and a PLUGIN.md overview (a convention for this marketplace).
datadog-agentic-plugins/
.claude-plugin/
marketplace.json # Marketplace registry — lists all available plugins
{plugin-name}/
.claude-plugin/
plugin.json # Required — Claude Code plugin manifest (JSON)
PLUGIN.md # Convention — plugin overview, category, dependencies, versions
skills/ # Required — at least one skill
skill-name/
SKILL.md # Entry point — version matrix, routing logic, core instructions
references/ # Version-variant instruction docs Claude reads into context
scripts/ # Validation and setup automation Claude executes
assets/ # Deployable sample apps, schemas, config files the prospect runs
commands/ # Optional — slash commands (.md files)
hooks/ # Optional — event-driven automation (hooks.json)
agents/ # Optional — subagent definitions (.md files)
.mcp.json # Optional — MCP server integrations
A plugin represents a technology domain. It groups related skills and declares dependencies on other plugins. The .claude-plugin/plugin.json manifest is required for Claude Code to discover and load the plugin. The PLUGIN.md file is a supplementary convention specific to this marketplace — it provides category, dependency, and version information that Claude reads and interprets.
jeremylongshore
gemini-cli-extensions
DataDog
duyet
Jeffallan