agentleFS
Sign inStart free
jalbarrangjalbarrang/skills/datadog/SKILL.md

datadog

Skill2 starsChanged 3 months agoMITView on GitHub

Search Datadog logs and RUM events via the Datadog HTTP API. Use when searching Datadog logs, inspecting RUM sessions/errors, debugging production issues, querying status:error or @http.status_code, or looking up front-end session/view/action events.

  • Reads credentials

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use kubernetes, docker and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mjunaidcaSkill

    kubernetes

    Production-grade Kubernetes manifests and debugging for containerized applications. This skill should be used when users ask to deploy to Kubernetes, create K8s manifests, containerize for K8s, set up Deployments/Services/Jobs/StatefulSets/CronJobs, create namespaces with resource quotas, set up multi-team isolation, configure ResourceQuota/ LimitRange, secure with RBAC (ServiceAccount, Role, RoleBinding), configure init containers (model download, db wait, migrations), set up sidecars (logging, metrics), or debug pods (CrashLoopBackOff, logs, exec, describe, events). Auto-detects from Dockerfile/code, generates hardened manifests with educational comments. CKAD-aligned.

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

  • MicrosoftSkill

    jira

    Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.

    Also in 3 projects that use this

  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Search production logs and RUM events.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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

Search production logs and RUM events. Scripts print a compact digest to stdout and write full JSON events to a temp file — read the printed path when you need complete messages or attributes.

Setup

  1. Export API credentials (or put them in a project .env; shell env wins):
export DD_API_KEY=...
export DD_APP_KEY=...
  1. Optional project config at .agents/datadog.json (or ~/.agents/datadog.json):
{
  "site": "us5.datadoghq.com",
  "service": "my-api",
  "env": "prod",
  "defaultTimeRange": "1h",
  "defaultTags": [],
  "rumApplicationId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "rumService": "my-frontend"
}

site defaults to datadoghq.com. Secrets stay in env vars — never in the JSON file.

Debugging: set DD_DRY_RUN=1 to print the would-be request URL + JSON body without calling Datadog.

Scripts

Resolve <skill> to this skill's directory. Invoke with Node ≥ 20.

Search logs

node <skill>/scripts/logs.mjs --query "status:error" [--from 1h] [--to now] [--limit 25]

Applies config service / env / defaultTags when the query does not already set them. Default time range is defaultTimeRange from config (or 1h). See reference/query-syntax.md and reference/time-formats.md.

Search RUM

node <skill>/scripts/rum.mjs --query "@type:error" [--from 1h] [--to now] [--limit 25]

Defaults to @type:session when the query omits @type. Applies rumApplicationId, rumService (or service), env, and defaultTags the same way. Optional --application-id, --service, --env, --sort newest|oldest.

Output contract

Digest on stdout (timestamp / service / status or type / excerpt). Full JSON events in a temp file under os.tmpdir() — path printed at the end. Prefer read on that path over re-querying.

When to load references

FileWhen
reference/query-syntax.mdLog/RUM query examples and auto-scoping rules
reference/time-formats.mdRelative vs ISO time inputs

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.

Check your setup, free