agentleFS
DataDogDataDog/pup/skills/dd-idp/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 11 mentionsNov 2026: 33 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the DataDog/pup repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about DataDog/pup

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

44 more on GitHub

On Hacker News · 1

  • Other versions1 project uses a version of this.

    Word for word · 1

    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.

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
  1. Distinctive:

    Use Pup's read-only Unified Entity Graph (UEG) to discover software, ownership, work, and operational context.

    line 13
  2. Distinctive:

    Use a recipe when one fits.

    line 17
  3. Very specific:

    Default to pup idp kinds and pup idp entities query for inventory, ownership, status, or connected context across services, teams, systems, …

    line 41
  4. Very specific:

    Use pup idp assist when the user values a fast, curated single-service summary, metadata gaps, and suggested next actions over graph …

    line 42
  5. Very specific:

    Treat find as a simple paginated literal service-name lookup.

    line 43
  6. Very specific:

    Use product commands such as pup incidents, pup slos, pup monitors, pup logs, pup traces, or pup security when the user needs deeper or …

    line 44
  7. Very specific:

    Use idp entities facets for observed field values and idp entities aggregate for grouped or filtered counts.

    line 45
  8. Very specific:

    Use pup service-catalog for the legacy typed service registry and pup software-catalog for Catalog entity/kind reads and writes.

    line 46
  9. Distinctive:

    If the relevant kind is unclear, start with the curated kind index.

    line 50
  10. Very specific:

    Add --include-low-level when looking for infrastructure kinds such as pods or containers.

    line 59
  11. Very specific:

    Keep the kind/ref outside alternatives: kind:service AND (owner:payments OR team:payments).

    line 89
  12. Very specific:

    Never write kind:"service".

    line 90
  13. Very specific:

    Use bare terms such as kind:service AND catalog with --free-text-match partial.

    line 92
  14. Very specific:

    Use lookbacks such as 1h, 24h, or 7d for --timeseries-interval.

    line 93
  15. Very specific:

    Treat expanded relations as bounded samples.

    line 94
  16. Very specific:

    Treat null or absent counts/booleans as unknown, never as zero or false.

    line 95
  17. Distinctive:

    Read UEG DSL when constructing or paginating a query, choosing flags, or following relations.

    line 100
  18. Distinctive:

    Read UEG footguns when a query fails, unexpectedly returns zero, or touches timestamps, negation, high-cardinality relations, APIs, GitHub, …

    line 101
  19. Distinctive:

    Read IDP recipes for runnable queries answering the questions above and other integration workflows.

    line 102

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

QuestionOften useful toRecipe
Which service handles this endpoint, and who owns it?On-call engineerEndpoint to service
Where is this service's code, and whom should I contact?Engineer joining a teamService context
Who is on call for this service now?Incident leadOn-call contact
Which services depend on this service, database, queue, or provider?SRE or service ownerCaller impact
What does our team own, and what needs attention?Engineering leadPortfolio and health
Which services increased in cost, and where are savings suggested?Engineering lead or FinOps partnerTeam cost
Which services need ownership or standards cleanup?Platform engineerOwnership gaps and scorecard levels
Which public endpoints lack protections, and who owns them?Security engineerAPI posture
Which services and owners need to act on this vulnerability advisory?Security engineerAdvisory to owners
Which Terraform workspaces have drift, and where is their configuration?Platform engineerTerraform 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 kinds and pup idp entities query for inventory, ownership, status, or connected context across services, teams, systems, repositories, dependencies, work, operations, or security kinds.
  • Use 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.
  • Treat 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.
  • Use product commands such as pup incidents, pup slos, pup monitors, pup logs, pup traces, or pup security when the user needs deeper or current telemetry.
  • Use 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.
  • Use 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.

Schema-first workflow

  1. 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.

  2. 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.

  3. 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.
  4. 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.
  5. 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 concrete ref:"ref:<kind>:<id>".
  • Keep the kind/ref outside alternatives: kind:service AND (owner:payments OR team:payments). A top-level OR is invalid.
  • Never write 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.
  • Use bare terms such as kind:service AND catalog with --free-text-match partial. The mode does not change field filters such as name:*catalog*.
  • Use lookbacks such as 1h, 24h, or 7d for --timeseries-interval. See the DSL reference for absolute windows and property scopes.
  • Treat expanded relations as bounded samples. Increase --relation-limit or query the related kind directly when the full set matters.
  • Treat null or 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.