Apm Integrations
DataDog/dd-trace-java
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
A skill your agent uses when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check…
$ npx skills add jjmartres/opencode --skill datadog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jjmartres/opencode datadog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/opencode/skills/datadog .claude/skills/datadog && rm -rf skills-srcUse ~/.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/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .claude/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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 install https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadogType 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.
$ npx skills add jjmartres/opencode --skill datadog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jjmartres/opencode datadog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/opencode/skills/datadog .agents/skills/datadog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .agents/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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.
$ npx skills add jjmartres/opencode --skill datadog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jjmartres/opencode datadog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/opencode/skills/datadog .cursor/skills/datadog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .cursor/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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 https://github.com/jjmartres/opencode.git --path opencode/skills/datadog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jjmartres/opencode --skill datadog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jjmartres/opencode datadog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/opencode/skills/datadog .gemini/skills/datadog && rm -rf skills-srcUse ~/.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/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .gemini/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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.
$ gh skill install jjmartres/opencode datadogInstalls 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).
$ npx skills add jjmartres/opencode --skill datadog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .github/skills && cp -r skills-src/opencode/skills/datadog .github/skills/datadog && rm -rf skills-srcUse ~/.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/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .github/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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.
$ npx skills add jjmartres/opencode --skill datadog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jjmartres/opencode datadog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jjmartres/opencode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/opencode/skills/datadog .opencode/skills/datadog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "datadog" agent skill from https://github.com/jjmartres/opencode/tree/main/opencode/skills/datadog into .opencode/skills/datadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "datadog", 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.
datadogA skill your agent uses when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check…
Datadog is an agent skill from jjmartres/opencode. Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `reference/installation.md`).
It sits in DevOps & Cloud, covering Observability. It works with Datadog. The repository describes itself as: A powerful, custom opencode configuration, complete with a suite of agents, commands, rules, skills, and a pre-configured MCP server. It's designed to be a flexible starting… The licence is MIT.
Read from SKILL.md and the folder at commit 28dc323. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Datadog loads about 1.7k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 294 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from jjmartres/opencode at commit 28dc323, republished under its MIT licence (© jjmartres). 294 words, ~1,668 tokens.
.claude/skills/datadog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.This skill will help you to interact with Datadog, through the unofficial datadog-cli to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
datadog logs search --query "<query>" [--from <time>] [--to <time>] [--limit <n>] [--sort <order>]Examples:
datadog logs search --query "status:error" --from 1h
datadog logs search --query "service:api status:error @http.status_code:500" --from 1hStream logs as they arrive. Press Ctrl+C to stop.
datadog logs tail --query "<query>" [--interval <seconds>]Examples:
datadog logs tail --query "status:error"
datadog logs tail --query "service:api" --interval 5Find all logs for a distributed trace across services.
datadog logs trace --id "<trace-id>" [--from <time>] [--to <time>]Example:
datadog logs trace --id "abc123def456" --from 24hGet logs before and after a specific timestamp to understand what happened.
datadog logs context --timestamp "<iso-timestamp>" [--before <time>] [--after <time>] [--service <svc>]Examples:
datadog logs context --timestamp "2024-01-15T10:30:00Z" --before 5m --after 2m
datadog logs context --timestamp "2024-01-15T10:30:00Z" --service api --before 10mQuick breakdown of errors by service, type, and message.
datadog errors [--from <time>] [--to <time>] [--service <svc>]Examples:
datadog errors --from 1h
datadog errors --service payment-api --from 24hCompare log counts between current period and previous period.
datadog logs compare --query "<query>" --period <time>Examples:
datadog logs compare --query "status:error" --period 1h
datadog logs compare --query "service:api status:error" --period 6hGroup similar log messages to find patterns (replaces UUIDs, numbers, etc.).
datadog logs patterns --query "<query>" [--from <time>] [--limit <n>]Examples:
datadog logs patterns --query "status:error" --from 1h
datadog logs patterns --query "service:api" --from 6h --limit 1000List all services with recent log activity.
datadog services [--from <time>] [--to <time>]Example:
datadog services --from 24hdatadog logs agg --query "<query>" --facet <facet> [--from <time>]Common facets: status, service, host, @http.status_code, @error.kind
Examples:
datadog logs agg --query "*" --facet status --from 1h
datadog logs agg --query "status:error" --facet service --from 24hRun multiple queries in parallel.
datadog logs multi --queries "name1:query1,name2:query2" [--from <time>]Example:
datadog logs multi --queries "errors:status:error,warnings:status:warn" --from 1hdatadog metrics query --query "<metrics-query>" [--from <time>] [--to <time>]Query format: <aggregation>:<metric>{<tags>}
Examples:
datadog metrics query --query "avg:system.cpu.user{*}" --from 1h
datadog metrics query --query "avg:system.cpu.user{service:api}" --from 1h
datadog metrics query --query "sum:trace.http.request.errors{service:api}.as_count()" --from 1h| Flag | Description |
|---|---|
--pretty | Human-readable output with colors |
--output <file> | Export results to JSON file |
--site <site> | Datadog site (e.g., datadoghq.eu) |
30m, 1h, 6h, 24h, 7d2024-01-15T10:30:00Z# 1. Quick error overview
datadog errors --from 1h
# 2. Is this new? Compare to previous period
datadog logs compare --query "status:error" --period 1h
# 3. What patterns are we seeing?
datadog logs patterns --query "status:error" --from 1h
# 4. Narrow down by service
datadog logs search --query "status:error service:payment-api" --from 1h
# 5. Get context around a specific timestamp
datadog logs context --timestamp "2024-01-15T10:30:00Z" --service api --before 5m --after 2m
# 6. Follow the distributed trace
datadog logs trace --id "TRACE_ID"# Stream errors as they happen
datadog logs tail --query "status:error"
# Watch specific service
datadog logs tail --query "service:api status:error"# List services
datadog services --from 24h
# Check error distribution
datadog logs agg --query "service:api" --facet status --from 1h
# Check CPU/memory
datadog metrics query --query "avg:system.cpu.user{service:api}" --from 1h# Save search results
datadog logs search --query "status:error" --from 1h --output errors.json
# Save error summary
datadog errors --from 24h --output error-report.json| Operator | Example | Description |
|---|---|---|
AND | service:api status:error | Both conditions |
OR | status:error OR status:warn | Either condition |
- | -status:info | Exclude |
* | service:api-* | Wildcard |
>= <= | @http.status_code:>=400 | Numeric comparison |
[TO] | @duration:[1000 TO 5000] | Range |
service - Service namestatus - Log level (error, warn, info, debug)host - Hostname@http.status_code - HTTP status code@error.kind - Error type@trace_id / @dd.trace_id - Trace ID© jjmartres, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in opencode/skills/datadog of jjmartres/opencode.
Open the folder on GitHubat commit 28dc323
Datadog 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Datadog this skilljjmartres/opencode | 133 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Apm IntegrationsDataDog/dd-trace-java | 736 | — | ~3.7k | Automated safety check: Notes | Apache-2.0 | |
| Redis Observabilityredis/agent-skills | 165 | 2 repos | ~911 | Automated safety check: Pass | MIT | |
| Frontmcp Observabilityagentfront/frontmcp | 146 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Monitoring Observabilityahmedasmar/devops-claude-skills | 203 | — | ~3.9k | Automated safety check: Pass | None | |
| Observability Architecturemajiayu000/litellm-rs | 117 | — | ~1.3k | Automated safety check: Pass | MIT |
DataDog/dd-trace-java
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
redis/agent-skills
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
majiayu000/litellm-rs
LiteLLM-RS Observability Architecture. An agent skill from majiayu000/litellm-rs.
EliasOulkadi/shokunin
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…
jjmartres/opencode
Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.
jjmartres/opencode
Builds Marp slide decks in one of seven ready-made themes, using bundled templates plus syntax, image and style references to keep slides short and readable.
jjmartres/opencode
Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.
jjmartres/opencode
Applies Google Style documentation to Python docstrings, Go comments and Terraform descriptions, for writing new docs or reviewing existing ones.
jjmartres/opencode
Guides use of Worktrunk (wt), a CLI that makes git worktrees as easy as branches so several AI agents can work in parallel on isolated branches.
jjmartres/opencode
A skill your agent uses when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text.
Works with
Categories
A skill your agent uses when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check…. Datadog is an agent skill from jjmartres/opencode. Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
Datadog fits situations like: you need to search Datadog logs; tail logs in real-time; trace distributed requests; investigate errors.
Run `npx skills add jjmartres/opencode --skill datadog -a claude-code`. Or copy the skill folder (opencode/skills/datadog in jjmartres/opencode) into .claude/skills/datadog in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jjmartres/opencode --skill datadog -a codex`. Or copy the skill folder (opencode/skills/datadog in jjmartres/opencode) into .agents/skills/datadog in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jjmartres/opencode --skill datadog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/datadog, .gemini/skills/datadog, .github/skills/datadog and .opencode/skills/datadog in your project.
SKILL.md names no scripts, command-line tools or credentials: Datadog is instructions for the agent only.
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.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Datadog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Datadog: Apm Integrations (DataDog/dd-trace-java, 736 stars), Redis Observability (redis/agent-skills, 165 stars), Frontmcp Observability (agentfront/frontmcp, 146 stars) and Monitoring Observability (ahmedasmar/devops-claude-skills, 203 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jjmartres (a GitHub user) maintains it in jjmartres/opencode, which has 133 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 20, 2026.
Source: jjmartres/opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.