Official agent skill

Analyze Error

by DataDog in DataDog/dd-trace-dotnet

Error Stack Trace Analysis for dd-trace-dotnet. An agent skill from DataDog/dd-trace-dotnet.

OfficialApache-2.0Auto-check passedDevelopment

Install Analyze Error

skills CLI
$ npx skills add DataDog/dd-trace-dotnet --skill analyze-error -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DataDog/dd-trace-dotnet analyze-error --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DataDog/dd-trace-dotnet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/analyze-error .claude/skills/analyze-error && rm -rf skills-src

Use ~/.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/

Facts

Skill name
analyze-error
GitHub stars
573
Token cost
~634 tokens
SKILL.md length
353 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Error Stack Trace Analysis for dd-trace-dotnet. An agent skill from DataDog/dd-trace-dotnet.

  • Works in 5 steps: Overview → Summary → Root Cause → …
  • Tasks that involve Debugging
  • SKILL.md covers Workflow and Output Format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyze Error is an agent skill from DataDog/dd-trace-dotnet, published by the product's own GitHub organization. Error Stack Trace Analysis for dd-trace-dotnet

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. It works with .NET and Datadog. The repository describes itself as: .NET Client Library for Datadog APM. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Debugging

Example prompts

  • “/analyze-error”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Overview
  2. Summary
  3. Root Cause
  4. Suggested Fix
  5. Reproduction Steps

What it can do on your machine

Read from SKILL.md and the folder at commit 09536cc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze Error loads about 634 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 353 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~15
When it runs · the whole SKILL.md, loaded when a task matches
~634

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from DataDog/dd-trace-dotnet at commit 09536cc, republished under its Apache-2.0 licence (© DataDog). 353 words, ~634 tokens.

Download SKILL.mdSave it as .claude/skills/analyze-error/SKILL.md (or your agent's skills folder).
name
analyze-error
description
Error Stack Trace Analysis for dd-trace-dotnet
argument-hint
<paste-error-stack-trace> <ctrl+enter any other context>
disable-model-invocation
true

Exception Analysis for dd-trace-dotnet

Analyze a redacted exception that was encountered within an application running dd-trace-dotnet. The exception was caught by dd-trace-dotnet, redacted, and then sent to Datadog's log intake. The goal is to: understand the error, determine if it is caused by dd-trace-dotnet, determine how to reproduce, determine how to prevent it (not catch it).

Workflow

User provided the basic error message along with the redacted stack trace. First line will be the Error Message - this is a constant message template that dd-trace-dotnet will log and send to Datadog Following lines will be the stack trace.

The user may have entered additional context info afterwards such as descriptions, PR links, versions the error was seen on.

Considerations

If it appears that duck typing is involved, prior to doing deep analysis go over the source code within dd-trace-dotnet\tracer\src\Datadog.Trace\DuckTyping\ as it is vital to have a clear understanding of this for proper error reconstruction.

External Libraries

When necessary refer to the official source of known third party libraries that are within the stack to provide better error reconstruction.

Show full SKILL.md (176 more words)Show less
Constraints
  • REDACTED frames are not known, but it is permissible to assume what they likely are.
  • Never recommend using a try/catch.
  • Log messages are constant message templates.
  • Stack traces may be outdated as in the current version of the code has changed and the error may have been resolved.
  • If the version isn't the latest version that does not imply it is resolved on latest
  • Only recommend changes within dd-trace-dotnet.
  • All exceptions / errors given have been gracefully caught.

Output Format

Use Markdown Do not use tables

1. Overview

Stack Trace, Component / CODEOWNER team, Actionability

2. Summary

2 to 3 sentences that can be used to explain what is happening.

3. Root Cause

Detailed analysis outlining the code flow that leads to the error. Format as follows:

  • Bold header with a short descriptive label
  • Reference simple type/method names, limit usages of URLs in this section
  • Put actual code references in code blocks
4. Suggested Fix

Before / after code comparison, format this as a git diff

5. Reproduction Steps

Provide an overview of how to reproduce this error.

© DataDog, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/analyze-error of DataDog/dd-trace-dotnet.

Open the folder on GitHubat commit 09536cc

Compare with similar skills

Analyze Error 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.

Analyze Error compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze Error this skillDataDog/dd-trace-dotnet573—~634Automated safety check: PassApache-2.0
Dotnet Debuggingnovotnyllc/dotnet-artisan233—~2.1kAutomated safety check: PassMIT
Okojo Node Ink Debugakeit0/okojo160—~798Automated safety check: PassMIT
MSBuildLocator .NET Core Loadermicrosoft/MSBuildLocator263—~1.1kAutomated safety check: PassCustom licence
Nes Rom Debugjonathanpeppers/dotnes780—~1.5kAutomated safety check: PassMIT
Raven Debug Compilermarinasundstrom/raven108—~1.6kAutomated safety check: PassMIT

Similar skills

  • Dotnet Debugging

    novotnyllc/dotnet-artisan

    Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…

    233 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox.

    160 GitHub stars~798 tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • MSBuildLocator .NET Core Loader

    microsoft/MSBuildLocator

    Official

    Reference for how MSBuildLocator loads MSBuild assemblies and finds the .NET SDK on .NET Core hosts, for anyone editing or debugging that loader code.

    263 GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Nes Rom Debug

    jonathanpeppers/dotnes

    Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler.

    780 GitHub stars~1.5k tokensUpdated 14 days ago
    DevelopmentAuto-check passed
  • Raven Debug Compiler

    marinasundstrom/raven

    Debug workflow for Raven compiler analysis and emission issues using rvn frontend tooling and the rvnc compiler driver.

    108 GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Development Workflow

    runceel/ReactiveProperty

    ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.

    944 GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from DataDog/dd-trace-dotnet

  • Bump Libdatadog

    DataDog/dd-trace-dotnet

    Official

    Update/bump the libdatadog native library version in dd-trace-dotnet.

    573 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Analyze Azdo Build

    DataDog/dd-trace-dotnet

    Official

    Analyze Azure DevOps CI build failures in dd-trace-dotnet pipeline.

    573 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Azure Functions

    DataDog/dd-trace-dotnet

    Official

    Dev/test workflow for tracer engineers working on the Datadog .NET tracer — build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze…

    573 GitHub stars~4.7k tokensUpdated today
    Auto-check passed
  • Analyze Crash

    DataDog/dd-trace-dotnet

    Official

    Stack Trace Crash Analysis for dd-trace-dotnet. An agent skill from DataDog/dd-trace-dotnet.

    573 GitHub stars~2.6k tokensUpdated today
    Auto-check: warnings
  • Review PR

    DataDog/dd-trace-dotnet

    Official

    Perform a review on a GitHub PR, leaving comments on the PR. An agent skill from DataDog/dd-trace-dotnet.

    573 GitHub stars~788 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Analyze Error

What does Analyze Error do?

Error Stack Trace Analysis for dd-trace-dotnet. An agent skill from DataDog/dd-trace-dotnet. Analyze Error is an agent skill from DataDog/dd-trace-dotnet, published by the product's own GitHub organization.

When should I use Analyze Error?

Analyze Error fits situations like: tasks that involve Debugging.

How do I install Analyze Error in Claude Code?

Run `npx skills add DataDog/dd-trace-dotnet --skill analyze-error -a claude-code`. Or copy the skill folder (.claude/skills/analyze-error in DataDog/dd-trace-dotnet) into .claude/skills/analyze-error in your project. Claude Code loads it when a task matches its description.

How do I install Analyze Error in Codex?

Run `npx skills add DataDog/dd-trace-dotnet --skill analyze-error -a codex`. Or copy the skill folder (.claude/skills/analyze-error in DataDog/dd-trace-dotnet) into .agents/skills/analyze-error in your project. Codex loads it when a task matches its description.

Can I use Analyze Error in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/dd-trace-dotnet --skill analyze-error -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-error, .gemini/skills/analyze-error, .github/skills/analyze-error and .opencode/skills/analyze-error in your project.

What does Analyze Error need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyze Error is instructions for the agent only.

Does Analyze Error access the network?

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.

Is Analyze Error safe to install?

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.

What licence does Analyze Error use?

Analyze Error is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze Error use?

About 634 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze Error?

Skills that share tags, products or a category with Analyze Error: Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars), Okojo Node Ink Debug (akeit0/okojo, 160 stars), MSBuildLocator .NET Core Loader (microsoft/MSBuildLocator, 263 stars) and Nes Rom Debug (jonathanpeppers/dotnes, 780 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze Error?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/dd-trace-dotnet, which has 573 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: DataDog/dd-trace-dotnet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.