Apm Integrations
DataDog/dd-trace-js
A skill your agent uses when adding, debugging, fixing, or modifying instrumentation and plugins for third-party libraries in dd-trace-js.
Find, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph.
$ npx skills add DataDog/pup --skill dd-idp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DataDog/pup dd-idp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dd-idp .claude/skills/dd-idp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .claude/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DataDog/pup/tree/main/skills/dd-idpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DataDog/pup --skill dd-idp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DataDog/pup dd-idp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dd-idp .agents/skills/dd-idp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .agents/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/pup --skill dd-idp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DataDog/pup dd-idp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dd-idp .cursor/skills/dd-idp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .cursor/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DataDog/pup.git --path skills/dd-idp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DataDog/pup --skill dd-idp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DataDog/pup dd-idp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dd-idp .gemini/skills/dd-idp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .gemini/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DataDog/pup dd-idpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DataDog/pup --skill dd-idp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dd-idp .github/skills/dd-idp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .github/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/pup --skill dd-idp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DataDog/pup dd-idp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/pup.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dd-idp .opencode/skills/dd-idp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dd-idp" agent skill from https://github.com/DataDog/pup/tree/main/skills/dd-idp into .opencode/skills/dd-idp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dd-idp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
dd-idpFind, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph.
Dd Idp is an agent skill from DataDog/pup, published by the product's own GitHub organization. Find, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph. Use for inventory, ownership, dependencies, and status questions across connected integrations and custom entities. Discover available kinds, fields, and relationships progressively when no recipe fits.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/footguns.md`, `references/recipes.md` and `references/ueg-dsl.md`).
It sits in DevOps & Cloud, covering Knowledge graphs. It works with Datadog. The repository describes itself as: Give your AI agent a Pup — a CLI companion with 200+ commands across 33+ Datadog products. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6a3c662. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Dd Idp loads about 2k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 834 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from DataDog/pup at commit 6a3c662, republished under its Apache-2.0 licence (© DataDog). 834 words, ~1,959 tokens.
.claude/skills/dd-idp/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Use Pup's read-only Unified Entity Graph (UEG) to discover software, ownership, work, and operational context. Its main payoff is connected context in one bounded request: a service plus its owners, systems, code, dependencies, and health signals through declared relationships.
Use a recipe when one fits. For inventory, ownership, status, or relationship questions about software, infrastructure, or engineering work, check available entity kinds even when no recipe matches. Follow the schema-first workflow, starting from the identifier the user has.
| Question | Often useful to | Recipe |
|---|---|---|
| Which service handles this endpoint, and who owns it? | On-call engineer | Endpoint to service |
| Where is this service's code, and whom should I contact? | Engineer joining a team | Service context |
| Who is on call for this service now? | Incident lead | On-call contact |
| Which services depend on this service, database, queue, or provider? | SRE or service owner | Caller impact |
| What does our team own, and what needs attention? | Engineering lead | Portfolio and health |
| Which services increased in cost, and where are savings suggested? | Engineering lead or FinOps partner | Team cost |
| Which services need ownership or standards cleanup? | Platform engineer | Ownership gaps and scorecard levels |
| Which public endpoints lack protections, and who owns them? | Security engineer | API posture |
| Which services and owners need to act on this vulnerability advisory? | Security engineer | Advisory to owners |
| Which Terraform workspaces have drift, and where is their configuration? | Platform engineer | Terraform drift |
Connect resources only through returned relationships; sharing a repository or a similar name does not establish service impact.
pup idp kinds and pup idp entities query for inventory, ownership, status, or connected context across services, teams, systems, repositories, dependencies, work, operations, or security kinds.pup idp assist when the user values a fast, curated single-service summary, metadata gaps, and suggested next actions over graph fidelity; use owner for convenient owner/on-call resolution.find as a simple paginated literal service-name lookup. Explicit kind: and ref: queries remain compatibility paths; use entities query for non-service kinds, another lookback, broader relation families, selected fields, counts, pagination, and traversal. Use deps as a convenient one-hour UEG runtime service-to-service dependency summary.pup incidents, pup slos, pup monitors, pup logs, pup traces, or pup security when the user needs deeper or current telemetry.idp entities facets for observed field values and idp entities aggregate for grouped or filtered counts. Prefer these over paging an inventory just to count it.pup service-catalog for the legacy typed service registry and pup software-catalog for Catalog entity/kind reads and writes. Do not use graph queries for mutations.If the relevant kind is unclear, start with the curated kind index. If it has no suitable kind, check the live inventory, including custom kinds, before concluding that UEG cannot help:
pup --read-only idp kinds list
pup --read-only idp kinds list --all --include-custom --jq '.kinds | map({kind, display_name})'Add --include-low-level when looking for infrastructure kinds such as pods
or containers.
Describe a candidate kind to discover attribute names and types, supported filters, and relations with their target kinds:
pup --read-only idp kinds describe '<kind>'Describe a promising relation's target kind when its fields could help answer the question. Inspect schemas progressively as the investigation needs them.
Build a small query from the discovered schema or adapt a recipe. Scope it to
a known identifier or filter, use a small page such as --limit 5, and select only the
attributes and relation family needed. Use --fields <kind>=... to select
related attributes. Inspect the returned values, then follow returned refs
when another hop is useful. Use the query reference
to construct queries beyond the examples.
Inspect warnings and result/relationship truncation. For inventories, use
an explicit --max-results budget and check page.stop_reason. Continue
with next_request.args when completeness is required; see
pagination.
Synthesize only what the returned fields and declared relations establish. Label noisy matches as inferred and missing edges as unavailable.
kind:<kind> or a concrete ref:"ref:<kind>:<id>".kind:service AND (owner:payments OR team:payments). A top-level OR is invalid.kind:"service"; the quoted kind silently returns no results upstream and Pup rejects it.--field selects attributes. --include expands relations. Discover both with kinds describe rather than guessing.kind:service AND catalog with --free-text-match partial. The mode does not change field filters such as name:*catalog*.1h, 24h, or 7d for --timeseries-interval. See the DSL reference for absolute windows and property scopes.--relation-limit or query the related kind directly when the full set matters.null or absent counts/booleans as unknown, never as zero or false.© DataDog, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in skills/dd-idp of DataDog/pup.
Open the folder on GitHubat commit 6a3c662
Dd Idp next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dd Idp this skillDataDog/pup | 1k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Apm IntegrationsDataDog/dd-trace-js | 836 | — | ~3k | Automated safety check: Pass | Custom licence | |
| Datadog Data Source GeneratorDataDog/terraform-provider-datadog | 468 | — | ~2.7k | Automated safety check: Pass | MPL-2.0 | |
| Write RbsDataDog/dd-trace-rb | 417 | — | ~805 | Automated safety check: Pass | Custom licence | |
| Apm IntegrationsDataDog/dd-trace-java | 736 | — | ~3.7k | Automated safety check: Notes | Apache-2.0 | |
| Tool ConnectorZhixiangLuo/10xProductivity | 478 | — | ~925 | Automated safety check: Pass | MIT |
DataDog/dd-trace-js
A skill your agent uses when adding, debugging, fixing, or modifying instrumentation and plugins for third-party libraries in dd-trace-js.
DataDog/terraform-provider-datadog
Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.
DataDog/dd-trace-rb
A skill your agent uses when writing, reviewing, or modifying RBS type signatures (sig//.rbs, vendor/rbs//.rbs, or inline : annotations) or running Steep – e.g.
DataDog/dd-trace-java
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
ZhixiangLuo/10xProductivity
Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial…
redis/agent-skills
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
DataDog/pup
Live Debugger - inspect runtime argument/variable values in production by placing log probes on methods.
DataDog/pup
Datadog docs lookup using docs.datadoghq.com/llms.txt and linked Markdown pages.
DataDog/pup
Datadog API CLI with 49 command groups, 300+ subcommands. An agent skill from DataDog/pup.
DataDog/pup
Load when investigating a specific flaky test. An agent skill from DataDog/pup.
DataDog/pup
APM - traces, services, dependencies, performance analysis. An agent skill from DataDog/pup.
DataDog/pup
File GitHub issues to the right repository (pup CLI or plugin)
Works with
Categories
Find, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph. Dd Idp is an agent skill from DataDog/pup, published by the product's own GitHub organization. Find, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph.
Dd Idp fits situations like: status questions across connected integrations and custom entities; tasks that involve Knowledge graphs.
Run `npx skills add DataDog/pup --skill dd-idp -a claude-code`. Or copy the skill folder (skills/dd-idp in DataDog/pup) into .claude/skills/dd-idp in your project. Claude Code loads it when a task matches its description.
Run `npx skills add DataDog/pup --skill dd-idp -a codex`. Or copy the skill folder (skills/dd-idp in DataDog/pup) into .agents/skills/dd-idp in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/pup --skill dd-idp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dd-idp, .gemini/skills/dd-idp, .github/skills/dd-idp and .opencode/skills/dd-idp in your project.
SKILL.md names no scripts, command-line tools or credentials: Dd Idp is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Dd Idp is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Dd Idp: Apm Integrations (DataDog/dd-trace-js, 836 stars), Datadog Data Source Generator (DataDog/terraform-provider-datadog, 468 stars), Write Rbs (DataDog/dd-trace-rb, 417 stars) and Apm Integrations (DataDog/dd-trace-java, 736 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
DataDog (a GitHub organization, an official publisher) maintains it in DataDog/pup, which has 1,026 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.
Source: DataDog/pup on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.