dd-idp
Skill1k starsChanged 6 months agoApache-2.0View on GitHub
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.
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- datadog-labs/pupword for word, first seen Oct 8, 2026
Who's talking about DataDog/pup
- A Hacker News story“Pup – Datadog CLI”Hacker News · Feb 10, 2026 · 4 points
- DataDog/terraform-provider-datadog“[datadog_provider] Add use_pup to authenticate with a pup login”GitHub · Nov 12, 2026 · 2 reactions
- DataDog/terraform-provider-datadog“[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command”GitHub · Oct 20, 2026 · 1 reactions
- datadog-labs/homebrew-pack“feat(policy): add trust policy for pup release workflow”GitHub · Feb 10, 2026 · 1 reactions
- Groupe-Hevea/tools-aquaproj“chore(deps): update dependency datadog-labs/pup to v2.4.5”GitHub · Nov 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub and Hacker News (50 times).
On GitHub · 49
- Nov 12, 2026[datadog_provider] Add use_pup to authenticate with a pup login — DataDog/terraform-provider-datadog2 reactions · 2 comments
- Oct 20, 2026[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command — DataDog/terraform-provider-datadog1 reaction · 3 comments
- Feb 10, 2026feat(policy): add trust policy for pup release workflow — datadog-labs/homebrew-pack1 reaction · 2 comments
- Nov 15, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.4 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
44 more on GitHub
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.7 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.6 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — mikutas/dotfiles0 reactions
- Nov 12, 2026chore(deps): update dependency datadog/pup to v2.4.7 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 12, 2026chore(deps): update dependency github:datadog/pup to v2.4.7 — JP-Ellis/dotfiles0 reactions
- Nov 11, 2026chore(deps): update dependency datadog/pup to v2.4.5 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 11, 2026Update dependency github:DataDog/pup to v2.4.2 — BarryThePenguin/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog-labs/pup to v2.4.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 10, 2026chore(deps): update all non-major dependencies — tak848/dotfiles0 reactions · 2 comments
- Nov 10, 2026chore(deps): update dependency github:datadog/pup to v2.4.4 — JP-Ellis/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog/pup to v2.4.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 8, 2026chore(deps): update dependency datadog-labs/pup to v2.4.2 — mikutas/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency github:datadog/pup to v2.4.2 — JP-Ellis/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency datadog/pup to v2.4.2 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — mikutas/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.10 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.8 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.7 — BarryThePenguin/dotfiles0 reactions
- Nov 5, 2026Update dependency github:DataDog/pup to v2.3.6 — BarryThePenguin/dotfiles0 reactions
- Nov 4, 2026Update dependency github:DataDog/pup to v2.3.5 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.1 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.4 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency github:datadog/pup to v2.4.1 — JP-Ellis/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.0 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.3 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v2 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v1.27.1 — BarryThePenguin/dotfiles0 reactions
- Nov 1, 2026chore(deps): update dependency datadog-labs/pup to v2.3.8 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 31, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency github:datadog/pup to v2.3.10 — JP-Ellis/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.6 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog/pup to v2.3.10 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency datadog/pup to v2.3.6 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency github:datadog/pup to v2.3.8 — JP-Ellis/dotfiles0 reactions
- Oct 26, 2026chore(deps): update dependency datadog/pup to v2.3.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 26, 2026chore(deps): update dependency github:datadog/pup to v2.3.5 — JP-Ellis/dotfiles0 reactions
- Sep 21, 2026[Plugin]: pup — using-system/otelyssey0 reactions · 6 comments
- Aug 23, 2026Add dsf WASM apps, named-sandbox connect, and TensorLake tool_runner door — rita-aga/temper0 reactions
- Jul 15, 2026Is a CLI in the roadmap? — incident-io/sdk-go0 reactions · 4 comments
- Jun 23, 2026Datadog, 'Pup' 오픈소스 공개 — 33개 Datadog 제품 200여 개 명령어를 AI 에이전트가 직접 호출 가능한 CLI로 제공 — roomedia/ax-trend0 reactions
On Hacker News · 1
- Feb 10, 2026Pup – Datadog CLI4 points
Other versions1 project uses a version of this.
Word for word · 1
- datadog-labs/pup★ 1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- pupSkill
- dd-apmSkill
- dd-code-generationSkill
- dd-debuggerSkill
- dd-docsSkill
- dd-file-issueSkill
- dd-logsSkill
- dd-monitorsSkill
- dd-pupSkill
- dd-symdbSkill
- dd-triage-flaky-testSkill
- dd-unblock-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 6 are distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use Pup's read-only Unified Entity Graph (UEG) to discover software, ownership, work, and operational context.
- Distinctive: line 17
Use a recipe when one fits.
- Very specific: line 41
Default to pup idp kinds and pup idp entities query for inventory, ownership, status, or connected context across services, teams, systems, …
- Very specific: line 42
Use pup idp assist when the user values a fast, curated single-service summary, metadata gaps, and suggested next actions over graph …
- Very specific: line 43
Treat find as a simple paginated literal service-name lookup.
- Very specific: line 44
Use product commands such as pup incidents, pup slos, pup monitors, pup logs, pup traces, or pup security when the user needs deeper or …
- Very specific: line 45
Use idp entities facets for observed field values and idp entities aggregate for grouped or filtered counts.
- Very specific: line 46
Use pup service-catalog for the legacy typed service registry and pup software-catalog for Catalog entity/kind reads and writes.
- Distinctive: line 50
If the relevant kind is unclear, start with the curated kind index.
- Very specific: line 59
Add --include-low-level when looking for infrastructure kinds such as pods or containers.
- Very specific: line 89
Keep the kind/ref outside alternatives: kind:service AND (owner:payments OR team:payments).
- Very specific: line 90
Never write kind:"service".
- Very specific: line 92
Use bare terms such as kind:service AND catalog with --free-text-match partial.
- Very specific: line 93
Use lookbacks such as 1h, 24h, or 7d for --timeseries-interval.
- Very specific: line 94
Treat expanded relations as bounded samples.
- Very specific: line 95
Treat null or absent counts/booleans as unknown, never as zero or false.
- Distinctive: line 100
Read UEG DSL when constructing or paginating a query, choosing flags, or following relations.
- Distinctive: line 101
Read UEG footguns when a query fails, unexpectedly returns zero, or touches timestamps, negation, high-cardinality relations, APIs, GitHub, …
- Distinctive: line 102
Read IDP recipes for runnable queries answering the questions above and other integration workflows.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Datadog IDP Entity Graph
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.
Start with the user's question
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.
Choose the right surface
- Default to
pup idp kindsandpup idp entities queryfor inventory, ownership, status, or connected context across services, teams, systems, repositories, dependencies, work, operations, or security kinds. - Use
pup idp assistwhen the user values a fast, curated single-service summary, metadata gaps, and suggested next actions over graph fidelity; useownerfor convenient owner/on-call resolution. - Treat
findas a simple paginated literal service-name lookup. Explicitkind:andref:queries remain compatibility paths; useentities queryfor non-service kinds, another lookback, broader relation families, selected fields, counts, pagination, and traversal. Usedepsas a convenient one-hour UEG runtime service-to-service dependency summary. - Use product commands such as
pup incidents,pup slos,pup monitors,pup logs,pup traces, orpup securitywhen the user needs deeper or current telemetry. - Use
idp entities facetsfor observed field values andidp entities aggregatefor grouped or filtered counts. Prefer these over paging an inventory just to count it. - Use
pup service-catalogfor the legacy typed service registry andpup software-catalogfor Catalog entity/kind reads and writes. Do not use graph queries for mutations.
Schema-first workflow
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-levelwhen 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-resultsbudget and checkpage.stop_reason. Continue withnext_request.argswhen 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.
Correctness rules
- Scope every query with one unquoted
kind:<kind>or a concreteref:"ref:<kind>:<id>". - Keep the kind/ref outside alternatives:
kind:service AND (owner:payments OR team:payments). A top-levelORis invalid. - Never write
kind:"service"; the quoted kind silently returns no results upstream and Pup rejects it. --fieldselects attributes.--includeexpands relations. Discover both withkinds describerather than guessing.- Use bare terms such as
kind:service AND catalogwith--free-text-match partial. The mode does not change field filters such asname:*catalog*. - Use lookbacks such as
1h,24h, or7dfor--timeseries-interval. See the DSL reference for absolute windows and property scopes. - Treat expanded relations as bounded samples. Increase
--relation-limitor query the related kind directly when the full set matters. - Treat
nullor absent counts/booleans as unknown, never as zero or false. - Preserve source boundaries: UEG establishes graph facts; product APIs establish detailed operational facts.
References
- Read UEG DSL when constructing or paginating a query, choosing flags, or following relations.
- Read UEG footguns when a query fails, unexpectedly returns zero, or touches timestamps, negation, high-cardinality relations, APIs, GitHub, Jira, scorecards, or security findings.
- Read IDP recipes for runnable queries answering the questions above and other integration workflows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

