Error Stack Trace Analysis for dd-trace-dotnet
npx skills add https://github.com/DataDog/dd-trace-dotnet --skill analyze-error
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).
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.
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.
When necessary refer to the official source of known third party libraries that are within the stack to provide better error reconstruction.
Use Markdown
Do not use tables
Stack Trace, Component / CODEOWNER team, Actionability
2 to 3 sentences that can be used to explain what is happening.
Detailed analysis outlining the code flow that leads to the error. Format as follows:
Before / after code comparison, format this as a git diff
Provide an overview of how to reproduce this error.
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take datadog/analyze-error from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.