Official agent skill

Locate Config Setting

Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using dda inv schema.locate

OfficialApache-2.0Auto-check: notesDevOps & Cloud

Install Locate Config Setting

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/locate-config-setting .claude/skills/locate-config-setting && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .claude/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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

$skill-installer install https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting

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

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/locate-config-setting .agents/skills/locate-config-setting && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .agents/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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.

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/locate-config-setting .cursor/skills/locate-config-setting && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .cursor/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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

$ gemini skills install https://github.com/DataDog/datadog-agent.git --path .agents/skills/locate-config-setting

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/locate-config-setting .gemini/skills/locate-config-setting && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .gemini/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting

Installs 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).

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/locate-config-setting .github/skills/locate-config-setting && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .github/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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.

skills CLI

$ npx skills add DataDog/datadog-agent --skill locate-config-setting -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent locate-config-setting --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/locate-config-setting .opencode/skills/locate-config-setting && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "locate-config-setting" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/locate-config-setting into .opencode/skills/locate-config-setting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locate-config-setting", 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.

Facts

Skill name: locate-config-setting
GitHub stars: 3.8k
Token cost: ~1.1k tokens
SKILL.md length: 475 words
Files: 1
Skills in repo: 35
Repo updated: Oct 9, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using dda inv schema.locate

DevOps & Cloud work in your project
SKILL.md covers Command, What it prints, Location semantics (important) and Behavior notes, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Locate Config Setting is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization. Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using dda inv schema.locate

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Datadog. The repository describes itself as: Main repository for Datadog Agent. The licence is Apache-2.0.

When your agent uses it

DevOps & Cloud work in your project

Example prompts

“/locate-config-setting”

Requirements

Pre-approved tools (allowed-tools): Bash, Read

What it can do on your machine

Read from SKILL.md and the folder at commit a706f1a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Locate Config Setting loads about 1.1k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 475 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~39
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read
```

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.

SKILL.md

The full file from DataDog/datadog-agent at commit a706f1a, republished under its Apache-2.0 licence (© DataDog). 475 words, ~1,131 tokens.

Download SKILL.mdSave it as .claude/skills/locate-config-setting/SKILL.md (or your agent's skills folder).

name: locate-config-setting
description: Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using `dda inv schema.locate`
allowed-tools: Bash, Read
argument-hint: [setting.path]
model: sonnet

Locate a Datadog Agent configuration setting or section in the schema source and print its definition plus the exact file and line where it lives.

Use this whenever you need to answer "where/how is config key X defined?" — its type, default, env vars, description, or which schema file to edit. It is much faster and more reliable than grepping the ~20k lines of schema YAML by hand, because the schema is split across files (core_schema.yaml plus per-section sub-files referenced via $ref), so a naive grep often points at the wrong file.

Command

bash

dda inv -- schema.locate <setting.path>

<setting.path> is the dotted logical path exactly as a user writes it in datadog.yaml / system-probe.yaml — e.g. api_key, proxy.https, apm_config.enabled. (Use -- so invoke treats the path as a positional arg.)

It can also be a pattern: any argument containing a character outside [A-Za-z0-9_.] (e.g. *, $, [) is matched against every full dotted path in the schema instead of looked up exactly. The pattern is treated as a regular expression (re.search); if it isn't valid regex it falls back to shell-style glob (fnmatch). So '*enabled' lists every setting whose path ends with enabled. Pattern matches are printed as a compact, sorted [<schema>] <path> -> <file>:<line> list (one line per match) rather than full node blocks; pass --json for the full {schema, path, file, line, node} array.

Flags

Flag	Effect
`--target core` / `--target system-probe`	Restrict to one schema (default: search both).
`--json`	Emit a JSON array of `{schema, path, file, line, node}` instead of human text. Use this when you want to parse the result programmatically.

Show full SKILL.md (223 more words)Show less

What it prints

Setting (leaf): the full schema node — node_type, type, default, env_vars, visibility, description, tags.
Section: the section's own metadata, with properties collapsed to the sorted list of immediate child key names (so a big section like apm_config doesn't dump thousands of lines). Drill into a child to see its full node.
A clickable location header per match: [<schema>] <file>:<line>.
If a key exists in both schemas (e.g. log_level), it prints one block per schema, labeled [core] and [system-probe].

Location semantics (important)

A top-level split section (e.g. apm_config, logs_config) is reported at its $ref: line in pkg/config/schema/yaml/core_schema.yaml — that's where it's wired in.
A setting inside a split section (e.g. apm_config.enabled) is reported in the sub-file (pkg/config/schema/yaml/apm_config.yaml:<line>) — that's where its real definition is, and the file you'd edit.
A setting/section that lives inline in the top file (e.g. api_key, proxy.https) is reported directly in core_schema.yaml.

Behavior notes

Reads the YAML source under pkg/config/schema/yaml/ — no build step or agent binary needed; works straight from a checkout. Line numbers are real.
Only traverses named settings and sections (properties). Array items and patternProperties internals are out of scope.
Not found → prints an error and exits non-zero (no fuzzy suggestions).

Examples

bash

# Top-level setting → core_schema.yaml + full node
dda inv -- schema.locate api_key

# Setting inside a split section → resolves into the sub-file
dda inv -- schema.locate apm_config.enabled

# Bare split section → $ref site in core_schema.yaml, child names only
dda inv -- schema.locate apm_config

# Restrict to one schema and get machine-readable output
dda inv -- schema.locate process_config.enabled --target core --json

# Pattern (glob): every setting whose full path ends with 'enabled'
dda inv -- schema.locate '*enabled'

# Pattern (regex): every path containing 'proxy' (a bare word like 'proxy' is an
# exact lookup, so add metacharacters to force a pattern/contains-match)
dda inv -- schema.locate '.*proxy'

The task lives in tasks/schema/locate.py (registered in tasks/schema/__init__.py).
Schema source: pkg/config/schema/yaml/.
To add a new config field (not just locate one), use the create-config-field skill.

Files

Just SKILL.md in .agents/skills/locate-config-setting of DataDog/datadog-agent.

Open the folder on GitHubat commit a706f1a

Compare with similar skills

Locate Config Setting 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.

Locate Config Setting compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Locate Config Setting this skillDataDog/datadog-agent	3.8k	—	~1.1k	Automated safety check: Notes	Apache-2.0	today
Apm IntegrationsDataDog/dd-trace-js	837	—	~3k	Automated safety check: Pass	Custom licence	today
Dd IdpDataDog/pup	1k	—	~2k	Automated safety check: Pass	Apache-2.0	today
Datadog Data Source GeneratorDataDog/terraform-provider-datadog	468	—	~2.7k	Automated safety check: Pass	MPL-2.0	today
Apm IntegrationsDataDog/dd-trace-java	736	—	~3.7k	Automated safety check: Notes	Apache-2.0	today
Azure FunctionsDataDog/dd-trace-dotnet	573	—	~4.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Apm Integrations
DataDog/dd-trace-js
Official
A skill your agent uses when adding, debugging, fixing, or modifying instrumentation and plugins for third-party libraries in dd-trace-js.
837 GitHub stars~3k tokensUpdated today
DevOps & CloudAuto-check passed
Dd Idp
DataDog/pup
Official
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.
1k GitHub stars~2k tokensUpdated today
DevOps & CloudAuto-check passed
Datadog Data Source Generator
DataDog/terraform-provider-datadog
Official
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.
468 GitHub stars~2.7k tokensUpdated today
DevOps & CloudAuto-check passed
Apm Integrations
DataDog/dd-trace-java
Official
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
736 GitHub stars~3.7k tokensUpdated today
DevOps & CloudAuto-check: notes
Azure Functions
DataDog/dd-trace-dotnet
Official
Dev/test workflow for tracer engineers working on the Datadog .NET tracer — build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze…
573 GitHub stars~4.7k tokensUpdated today
DevOps & CloudAuto-check passed
Tool Connector
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…
478 GitHub stars~925 tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed

More from DataDog/datadog-agent

All 35 skills in this repo

Triage CI Failure
DataDog/datadog-agent
Official
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
3.8k GitHub stars~2.3k tokensUpdated today
Auto-check passed
Elicit
DataDog/datadog-agent
Official
Run a structured discovery session to build an Allium specification through conversation.
3.8k GitHub starsUsed in 1 repo~3.7k tokens
Auto-check passed
Follow PR
DataDog/datadog-agent
Official
Monitor the current PR's GitLab pipeline to completion, then report success, auto-fix, or investigate a failure.
3.8k GitHub stars~3.2k tokensUpdated today
Auto-check passed
Create Epic Recap
DataDog/datadog-agent
Official
A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…
3.8k GitHub stars~5k tokensUpdated today
Auto-check: notes
Explain Lading Config
DataDog/datadog-agent
Official
Explains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.
3.8k GitHub stars~1.2k tokensUpdated today
Auto-check passed
Distill
DataDog/datadog-agent
Official
Extract an Allium specification from an existing codebase. An agent skill from DataDog/datadog-agent.
3.8k GitHub starsUsed in 1 repo~7k tokens
Auto-check passed

Works with

Datadog

Questions about Locate Config Setting

What does Locate Config Setting do?

Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using dda inv schema.locate. Locate Config Setting is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization.

When should I use Locate Config Setting?

Locate Config Setting fits situations like: devOps & Cloud work in your project.

How do I install Locate Config Setting in Claude Code?

Run `npx skills add DataDog/datadog-agent --skill locate-config-setting -a claude-code`. Or copy the skill folder (.agents/skills/locate-config-setting in DataDog/datadog-agent) into .claude/skills/locate-config-setting in your project. Claude Code loads it when a task matches its description.

How do I install Locate Config Setting in Codex?

Run `npx skills add DataDog/datadog-agent --skill locate-config-setting -a codex`. Or copy the skill folder (.agents/skills/locate-config-setting in DataDog/datadog-agent) into .agents/skills/locate-config-setting in your project. Codex loads it when a task matches its description.

Can I use Locate Config Setting in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/datadog-agent --skill locate-config-setting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/locate-config-setting, .gemini/skills/locate-config-setting, .github/skills/locate-config-setting and .opencode/skills/locate-config-setting in your project.

What does Locate Config Setting need to run?

SKILL.md names no scripts, command-line tools or credentials: Locate Config Setting is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read.

Does Locate Config Setting access the network?

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.

Is Locate Config Setting safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Locate Config Setting use?

Locate Config Setting 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.

How many tokens does Locate Config Setting use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Locate Config Setting?

Skills that share tags, products or a category with Locate Config Setting: Apm Integrations (DataDog/dd-trace-js, 837 stars), Dd Idp (DataDog/pup, 1k stars), Datadog Data Source Generator (DataDog/terraform-provider-datadog, 468 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.

Who maintains Locate Config Setting?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/datadog-agent, which has 3,759 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

Source: DataDog/datadog-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Locate Config Setting

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Command

Flags

What it prints

Location semantics (important)

Behavior notes

Examples

Related

Files

Compare with similar skills

Similar skills

More from DataDog/datadog-agent

Related

Questions about Locate Config Setting