Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →langfuse/debug-issue-with-datadog
Establish root cause by combining Datadog telemetry with the Langfuse repo.
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 6 more in the full report
8 fixed3 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
You completed an investigation anchored to Datadog monitor ID 883910 and identified the root cause as a missing DB index on trace tags. What final step should be offered regarding documentation?
| Checked | Without skill | With skill |
|---|---|---|
| The response offers a human-gated write-back to incident-alert-tickets to record the documented root cause. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
LFE-XXXX ID) describes a production
failure, error spike, or customer report.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.
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.
Intake. Pull every signal already available in the report. See
references/intake.md. For a Linear URL/ID, fetch
the issue and its comments via the Linear MCP — the description is often
updated inline as triage proceeds. For a GitHub issue, use gh issue view.
For pasted text, treat it as the description.
If intake contains an alert identity (a Datadog monitor ID or title, an
incident.io alert/INC reference, or an on-call page), first apply
incident-alert-tickets — a
documented cause section may resolve the investigation before any sweep.
Scope the sweep. From the intake, pick the affected subsystem and time
window. Use references/repo-debug-map.md
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.