메뉴
Access Datadog metrics in the us5 site with environment-provided credentials and the helper script. Use when Codex needs to discover active metric names, query timeseries data, inspect metric tags, or answer monitoring questions from Datadog metrics.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Understand and explain an unfamiliar repository by inspecting its structure, entrypoints, runtime flows, and key modules. Use when the user asks for onboarding to a new codebase, wants an architecture walkthrough, asks where to start reading, needs a feature traced end-to-end, or wants a concise explanation of how folders, services, APIs, jobs, data models, or tests fit together.
Prepare and open a GitHub pull request with the GitHub CLI. Use when the user asks to open a PR, create a pull request from the current branch, draft a PR title and body, compare against a base branch, or submit a PR with `gh pr create`.
Create a focused git commit from the current working tree using conventional commits. Use when the user asks to commit changes, write a commit message, choose a commit type like feat or fix, stage the right files, or turn a finished edit into a clean commit without scooping up unrelated work.
SOC 직업 분류 기준
| name | datadog-metrics |
| description | Access Datadog metrics in the us5 site with environment-provided credentials and the helper script. Use when Codex needs to discover active metric names, query timeseries data, inspect metric tags, or answer monitoring questions from Datadog metrics. |
Use this skill for Datadog metric work against us5.datadoghq.com. The helper script reads credentials from environment variables, so the common path is to export them once and run the script instead of hand-writing curl commands.
Run scripts/datadog_metrics.py from the repo root or by absolute path.
Set credentials first:
export DATADOG_SITE=us5.datadoghq.com
export DATADOG_API_KEY=...
export DATADOG_APP_KEY=...
Common commands:
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py list-active --from now-24h --prefix validator_api.
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py query 'avg:validator_api.current_slot{env:prod}' --from now-30m
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py tags validator_api.current_slot
If the user gives a rough description instead of an exact metric name, start with list-active.
--prefix to narrow broad namespaces.--limit to keep output small.--from now-24h or another explicit window so the result is easy to justify.Example:
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py list-active --from now-24h --prefix transaction_monitor.
Use query once you know the metric expression.
avg:metric.name{tag:value}.--from now-15m --to now.--show-points N when the user needs the most recent raw samples.--output json when another tool or script will consume the result.Supported time formats:
now, now-15m, now-2h, now-7d2026-03-27T09:00:00ZExample:
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py query \
'avg:validator_api.current_slot{env:prod}' \
--from now-1h \
--show-points 5
Use tags when the user needs to know which tags are available for slicing a metric.
--configured-only to show only configured tags when the full set is noisy.Example:
python3 codex/skills/datadog-metrics/scripts/datadog_metrics.py tags validator_api.current_slot --configured-only
DATADOG_SITE, DATADOG_API_KEY, and DATADOG_APP_KEY.DD_SITE, DD_API_KEY, or DD_APP_KEY for one-off overrides, or pass CLI flags directly.