datadog-labsagent-skills320 installs on skills.sh

Agent Observability Replay Trace

Use when a developer wants to iterate on ONE specific Agent Observability / LLM Obs trace whose...

Works in any agentClaude CodeCodexCursorClaude appChatGPT+ any other agent
datadog-labs/agent-skills
Security state: reviewed

3 static scans, 0 counted findings.

Edge checks it again each time your agent loads it.

SKILL.md4 files · 46.4 KB

From the datadog-labs public repository. Edge did not write or edit this skill.

What it does

  • Use when a developer wants to iterate on ONE specific Agent Observability / LLM Obs trace whose output they didn't like : re-running that trace against their LOCAL code, seeing a concise diff of the old vs new output, and looping (change code → replay → diff) until satisfied.
  • Invoked as /agent-observability-replay-trace <trace-id> [changes to test].
  • Signals: "replay this trace"; "iterate on a trace"; "this trace's output is wrong, fix it and re-run"; "re-run trace <id> with <change>"; pasting a trace id from the Agent Observability UI with a description of what to fix.
  • It fetches the trace via the datadog-llmo MCP or the pup CLI, edits code, re-runs the app to emit a NEW trace, and diffs the two : no local server, no browser.
  • For agents traced with ddtrace / LLM Obs (Python first-class), with JSON-serializable entry input.
  • Do NOT use for: scored Experiments or the browser "Replay" button (that's agent-observability-replay-experiment), building an experiment from a dataset/CSV, writing evaluators, root-causing failed traces, or RUM/HTTP session replay.

How it works

  1. 1
    Copy

    Try for free gives you one prompt.

  2. 2
    Paste

    Paste it into Claude Code, Codex or Cursor.

  3. 3
    Ask

    Ask for the outcome. Your agent loads Agent Observability Replay Trace.

What you can inspect

3 static scans, 0 counted findings.

Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.

State definitions

Skill details

Security scansReviewed

3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.

Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .

Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: 2.

Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .

Edge static checks
Pass · 0 counted findings · 2026-09-27
Cisco skill-scanner
Pass · 0 counted findings · 2026-09-27
Semgrep Edge rules
Pass · 0 counted findings · 2026-09-27
Creator, source & licencedatadog-labs

From the datadog-labs public repository. Edge did not write or edit this skill.

Revision
7f8b08f4fa57211ac1b2b42d9771c9e0c4d79124
Package hash
sha256:8d13b3f5ef8da46930f204966abcd46c9cf23e1c1b6b3362706a96e7951dcd1d
Licence
MIT
Description
Use when a developer wants to iterate on ONE specific Agent Observability / LLM Obs trace whose output they didn't like : re-running that trace against their LOCAL code, seeing a concise diff of the old vs new output, and looping (change code → replay → diff) until satisfied. Invoked as /agent-observability-replay-trace <trace-id> [changes to test]. Signals: "replay this trace"; "iterate on a trace"; "this trace's output is wrong, fix it and re-run"; "re-run trace <id> with <change>"; pasting a trace id from the Agent Observability UI with a description of what to fix. It fetches the trace via the datadog-llmo MCP or the pup CLI, edits code, re-runs the app to emit a NEW trace, and diffs the two : no local server, no browser. For agents traced with ddtrace / LLM Obs (Python first-class), with JSON-serializable entry input. Do NOT use for: scored Experiments or the browser "Replay" button (that's agent-observability-replay-experiment), building an experiment from a dataset/CSV, writing evaluators, root-causing failed traces, or RUM/HTTP session replay.
Quoted from the skill’s own description
Read skill files4 files

4 files, 46.4 KB at revision 7f8b08f4fa57.

Questions about Agent Observability Replay Trace

What does Agent Observability Replay Trace do?

Use when a developer wants to iterate on ONE specific Agent Observability / LLM Obs trace whose... Published by datadog-labs (datadog-labs/agent-skills).

Is Agent Observability Replay Trace safe to use?

Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.

How do I use Agent Observability Replay Trace in Claude Code, Codex or Cursor?

Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.