agentleFS
datadog-labsdatadog-labs/agent-skills/dd-docs/SKILL.md

dd-docs

Skill185 starsChanged 38 days agoMITView on GitHub

Look up Datadog documentation, limits, and feature availability. Prefer search_datadog_documentation when that MCP tool is available, then one Markdown page from docs.datadoghq.com/llms.txt. For API reference, use pup docs api.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the smallest source that answers the question, then stop.

    line 14
  2. Very specific:

    Call read_datadog_documentation with one source URL or document id only when a passage is not enough.

    line 24
  3. Distinctive:

    If the tool is not in your tool list, skip this section.

    line 26

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

Use the smallest source that answers the question, then stop. Cite the page URL you used.

  1. search_datadog_documentation is available → Search.
  2. The question is an API endpoint or request schema, and search did not answer it → API.
  3. Otherwise → Page.

Search

search_datadog_documentation (MCP toolset documentation, no extra permission) returns at most 10 source passages with links. It does not write an answer. It supports English, French, Japanese, Korean, and Spanish.

Call read_datadog_documentation with one source URL or document id only when a passage is not enough. It returns long pages in parts; stop at the part that answers.

If the tool is not in your tool list, skip this section. Enabling the toolset is a separate setup task.

API

Pup reads the live API reference and needs no auth. Commands, smallest first:

pup docs api <topic> --operations
pup docs api <topic>

The operations list is the small result. Fetch pup docs api <topic> <operation> only when you need that operation's request schema: the page includes every sample. Skip pup docs api with no topic.

Page

https://docs.datadoghq.com/llms.txt is the section index. Open the one section index it links to, then fetch one page by appending .md:

https://docs.datadoghq.com/monitors/llms.txt
https://docs.datadoghq.com/monitors.md

Documentation is served from docs.datadoghq.com. Site-specific values, such as API endpoints, are selected on that page.

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.