debug-issue-with-datadog SKILL.md skillA
debug-issue-with-datadog from langfuse/langfuse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add langfuse/langfuse/debug-issue-with-datadog@git:20261119.d535d56Pins git:20261119.d535d56 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- langfuse/langfuse
- Path
.agents/skills/debug-issue-with-datadog/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261119.d535d56, committed Nov 19, 2026
- First version recorded
- Apr 27, 2026
- Size
- 6,339 bytes
- Repository stars
- 37,634
- License
- a license file GitHub does not identify
Establish root cause by combining Datadog telemetry with the Langfuse repo. Use when investigating or triaging a user report, Linear or GitHub issue, incident, or pasted production error.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Debug Issue with Datadog Use this skill whenever the task is **investigative** rather than implementational: a user, customer, or oncall has surfaced a problem and you need to figure out *what is actually happening in production* and *where in the code it lives*. The deliverable is an analysis, not a patch — though the analysis should make the right patch obvious. ## When to Apply - A Linear issue (typically with an `LFE-XXXX` ID) describes a production failure, error spike, or customer report. - A GitHub issue or pasted incident/error report needs triage. - A monitor alerted and you need to understand *why* before deciding what to fix. - Existing tickets under the "Make monitoring useful again" project (parent `LFE-8837`) and similar — these expect the structured analysis output below. If the task is "implement this fix" rather than "figure out what's broken", this is the wrong skill — go to `backend-dev-guidelines` or the relevant package guide. ## Workflow Read the inputs first, then plan the Datadog sweep, then read the code, then write the analysis. Do not skip ahead to suggested patches before the data supports them. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_bolfqsdybxnwojwe/527a79b6613f19722667aec0a1c8695746c56b4c1107be0c1935eb5a82658676.json
Then /plugin install debug-issue-with-datadog@markdownregistry-bolfqsdybxnwojwe in Claude Code. It installs git:20261119.d535d56, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add langfuse/langfuse/debug-issue-with-datadog@sha256:527a79b6613f1972The line at the top of this page pins the label git:20261119.d535d56, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bolfqsdybxnwojwe)
5 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in langfuse/langfuse/debug-issue-with-datadog since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of debug-issue-with-datadog from somewhere else? Ask it: where did my debug-issue-with-datadog come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Apr 27, 2026 and Nov 19, 2026, about one every 52 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261119.d535d56 latest | 2026-11-19 | d535d56 | 6,339 B | A | view · diff |
| git:20260729.6d2988f | 2026-07-29 | 6d2988f | 6,279 B | A | view · diff |
| git:20260716.50269e7 | 2026-07-16 | 50269e7 | 6,509 B | A | view · diff |
| git:20260511.08615fe | 2026-05-11 | 08615fe | 5,766 B | A | view · diff |
| git:20260427.8e275fb | 2026-04-27 | 8e275fb | 5,446 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/debug-issue-with-datadog/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6339 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
langfuse/langfuse · 37,634 stars · license a license file GitHub does not identify · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bolfqsdybxnwojwe GET https://markdownregistry.com/api/v1/resolve?ref=langfuse/langfuse/debug-issue-with-datadog GET https://markdownregistry.com/api/v1/blob/527a79b6613f19722667aec0a1c8695746c56b4c1107be0c1935eb5a82658676
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from langfuse/langfuse
Every file in langfuse/langfuse
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.