Official agent skill

Bump Libdatadog

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

OfficialApache-2.0Auto-check passedDevelopment

Install Bump Libdatadog

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a claude-code

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

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog --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/bump-libdatadog .claude/skills/bump-libdatadog && 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/

Paste into Claude Code

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .claude/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-dotnet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/bump-libdatadog .agents/skills/bump-libdatadog && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .agents/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-dotnet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/bump-libdatadog .cursor/skills/bump-libdatadog && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .cursor/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/DataDog/dd-trace-dotnet.git --path .claude/skills/bump-libdatadog

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-dotnet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/bump-libdatadog .gemini/skills/bump-libdatadog && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .gemini/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .github/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DataDog/dd-trace-dotnet --skill bump-libdatadog -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-dotnet bump-libdatadog --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-dotnet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/bump-libdatadog .opencode/skills/bump-libdatadog && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bump-libdatadog" agent skill from https://github.com/DataDog/dd-trace-dotnet/tree/master/.claude/skills/bump-libdatadog into .opencode/skills/bump-libdatadog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-libdatadog", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: bump-libdatadog
GitHub stars: 573
Token cost: ~1.7k tokens
SKILL.md length: 692 words
Files: 2 (incl. scripts)
Skills in repo: 6
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

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

Works in 8 steps: Linux/macOS —… → Windows —… → Determine target version → …
The user asks to bump
SKILL.md covers Overview, Files to Modify, Step-by-Step Procedure and Files That May Need Regeneration, plus 3 more sections
Runs Shell scripts from its folder; calls bash; reaches github.com

What it does

Bump Libdatadog is an agent skill from DataDog/dd-trace-dotnet, published by the product's own GitHub organization. Update/bump the libdatadog native library version in dd-trace-dotnet. Use when the user asks to bump, update, or upgrade libdatadog, or mentions a new libdatadog release version.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/fetch-release-hashes.sh`).

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

When your agent uses it

The user asks to bump
Upgrade libdatadog
Mentions a new libdatadog release version

Example prompts

“/bump-libdatadog”

Requirements

A Bash shell

Workflow steps

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

Linux/macOS — build/cmake/FindLibdatadog.cmake
Windows — build/vcpkg_local_ports/libdatadog/
Determine target version
Get hashes from the release page
Update build/cmake/FindLibdatadog.cmake
Update build/vcpkg_local_ports/libdatadog/vcpkg.json
Update build/vcpkg_local_ports/libdatadog/portfile.cmake
Verify

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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
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

Bump Libdatadog loads about 1.7k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 692 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/bump-libdatadog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: bump-libdatadog
description: Update/bump the libdatadog native library version in dd-trace-dotnet. Use when the user asks to bump, update, or upgrade libdatadog, or mentions a new libdatadog release version.

Bump libdatadog Version

Overview

The native library is consumed as prebuilt binaries from GitHub releases of DataDog/libdatadog-dotnet — the .NET-specific distribution of libdatadog (a minimal feature preset: profiling, crashtracker, symbolizer, library-config). This is not upstream DataDog/libdatadog.

Version scheme: the pinned version is libdatadog-dotnet's own release version (e.g. v1.3.5), which is distinct from the upstream libdatadog version it is built from (tracked by LIBDATADOG_VERSION in that repo — e.g. libdatadog-dotnet v1.3.5 is built from upstream libdatadog v32.0.0). Pin the libdatadog-dotnet version here, not the upstream one.

There are two version pins to update, both from the same libdatadog-dotnet release:

Platform	File	Hash type	Version format
Linux/macOS	`build/cmake/FindLibdatadog.cmake`	SHA-256	`v<MAJOR>.<MINOR>.<PATCH>`
Windows	`build/vcpkg_local_ports/libdatadog/vcpkg.json` + `portfile.cmake`	SHA-512	`<MAJOR>.<MINOR>.<PATCH>` (no `v` prefix)

A libdatadog-dotnet release builds all 8 platform artifacts together, so the two pins should normally move to the same version in lockstep. Confirm with the user if they intend otherwise.

Files to Modify

1. Linux/macOS — `build/cmake/FindLibdatadog.cmake`

Update these values:

LIBDATADOG_VERSION — the version tag (e.g. "v32.0.0")
SHA256_LIBDATADOG_ARM64 — macOS arm64 hash
SHA256_LIBDATADOG_X86_64 — macOS x86_64 hash
SHA256_LIBDATADOG (aarch64 gnu) — Linux aarch64 glibc hash
SHA256_LIBDATADOG (aarch64 musl) — Linux aarch64 Alpine hash
SHA256_LIBDATADOG (x86_64 musl) — Linux x86_64 Alpine hash
SHA256_LIBDATADOG (x86_64 gnu) — Linux x86_64 glibc hash

Artifact filenames (from GitHub releases):

libdatadog-aarch64-apple-darwin.tar.gz
libdatadog-x86_64-apple-darwin.tar.gz
libdatadog-aarch64-unknown-linux-gnu.tar.gz
libdatadog-aarch64-alpine-linux-musl.tar.gz
libdatadog-x86_64-alpine-linux-musl.tar.gz (note: uses ${CMAKE_SYSTEM_PROCESSOR} in filename)
libdatadog-x86_64-unknown-linux-gnu.tar.gz (note: uses ${CMAKE_SYSTEM_PROCESSOR} in filename)

2. Windows — `build/vcpkg_local_ports/libdatadog/`

Two files:

vcpkg.json — update "version-string" (no v prefix)
portfile.cmake — update SHA-512 hashes for x64 and x86 Windows zips

Artifact filenames:

libdatadog-x64-windows.zip
libdatadog-x86-windows.zip

Step-by-Step Procedure

Step 1: Determine target version

Ask the user for the target version, or check the latest release:

https://github.com/DataDog/libdatadog-dotnet/releases

Step 2: Get hashes from the release page

SHA-256 and SHA-512 checksums are published directly in the GitHub release notes. Either:

Visit https://github.com/DataDog/libdatadog-dotnet/releases/tag/v<VERSION> and copy from the checksums sections, or
Run the helper script which fetches them via the GitHub API:

bash

bash .claude/skills/bump-libdatadog/scripts/fetch-release-hashes.sh <VERSION>

Where <VERSION> is without the v prefix (e.g. 1.3.5).

The release notes contain:

SHA256 checksums section → for FindLibdatadog.cmake (6 Linux/macOS artifacts)
SHA512 checksums section → for portfile.cmake (2 Windows artifacts)

Step 3: Update `build/cmake/FindLibdatadog.cmake`

Update LIBDATADOG_VERSION to "v<VERSION>"
Replace each SHA256_LIBDATADOG* value with the new SHA-256 hash from the script output

Step 4: Update `build/vcpkg_local_ports/libdatadog/vcpkg.json`

Update "version-string" to the new version (no v prefix).

Step 5: Update `build/vcpkg_local_ports/libdatadog/portfile.cmake`

Replace the SHA-512 hashes for x64 and x86 Windows builds.

Step 6: Verify

Confirm all 8 hashes were updated (6 for CMake SHA-256, 2 for vcpkg SHA-512)
Confirm version strings match in both files

Run the Nuke build targets to validate hashes:

bash

# Linux — validates CMake SHA-256 hashes during configure
./tracer/build.sh CompileProfilerNativeSrc

# Windows — validates vcpkg SHA-512 hashes during install
.\tracer\build.cmd CompileProfilerNativeSrc

Show full SKILL.md (278 more words)Show less

Files That May Need Regeneration

These don't contain version strings but may need refreshing after a bump if the exported symbol set or glibc requirements change:

tracer/build/_build/NativeValidation/native-libdatadog-symbols-alpine-x64.verified.txt
tracer/build/_build/NativeValidation/native-libdatadog-symbols-alpine-arm64.verified.txt

CI will fail if the symbol list changes — re-run the Alpine symbol validation step and accept the new snapshot.

Because libdatadog-dotnet ships a reduced feature set (no data-pipeline, log, telemetry, ddsketch, or ffe), its exported symbols are a strict subset of upstream libdatadog — so these snapshots reflect that smaller set. The glibc cap in Build.Profiler.Steps.cs (libdatadog_profiling ≤ 2.15 on x64, ≤ 2.17 on arm64) still applies and is unchanged by the source switch — libdatadog-dotnet x64 builds are capped at GLIBC 2.15, same as upstream.

Optional Updates (doc-comment SHAs)

Several files under tracer/src/Datadog.Trace/LibDatadog/ have XML doc comments linking to a specific upstream libdatadog git SHA (e.g. 60583218a8de6768f67d04fcd5bc6443f67f516b). These are informational only and can be updated for traceability (use the upstream SHA the libdatadog-dotnet release was built from):

VecU8.cs, CharSlice.cs, Error.cs
ServiceDiscovery/ResultTag.cs, ServiceDiscovery/TracerMemfdHandleResult.cs

profiler/Directory.Build.targets — Windows link dependencies for libdatadog
tracer/build/_build/Build.Steps.cs — copies libdatadog binary to monitoring home
tracer/build/_build/Build.Profiler.Steps.cs — profiler build steps; glibc version expectations for Alpine
.gitlab/one-pipeline.locked.yml — CI pipeline (auto-generated, don't edit manually)
vcpkg.json (root) — declares dependency on libdatadog (no version pin here)
vcpkg-configuration.json — overlay ports config

Important Notes

The CMake file uses SHA-256 hashes; the vcpkg portfile uses SHA-512 hashes. Both are published in the libdatadog-dotnet GitHub release notes (under ## Checksums).
The CMake version has a v prefix (v1.3.5); vcpkg does not (1.3.5).
If a release doesn't have all platform artifacts, the bump may need to wait or be partial.
After bumping, CI will validate the hashes on all platforms. Hash mismatches cause clear build failures.

Files

SKILL.md and 1 other file (scripts) in .claude/skills/bump-libdatadog of DataDog/dd-trace-dotnet.

SKILL.md
scripts/fetch-release-hashes.sh

Open the folder on GitHubat commit 09536cc

Compare with similar skills

Bump Libdatadog 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.

Bump Libdatadog compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bump Libdatadog this skillDataDog/dd-trace-dotnet	573	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
JS Cpp Protocolnotepadqq/notepadqq	2.3k	—	~3.2k	Automated safety check: Pass	GPL-3.0	yesterday
Dotnet Debuggingnovotnyllc/dotnet-artisan	233	—	~2.1k	Automated safety check: Pass	MIT	1 mo ago
.NET Crash Dump Collectiondotnet/skills	5.6k	2 repos	~1.1k	Automated safety check: Pass	MIT	today
Sokol Netelix22/Sokol.NET	154	—	~2.8k	Automated safety check: Pass	MIT	yesterday
Run Maui Apptig/winprint	101	—	~1.2k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

JS Cpp Protocol
notepadqq/notepadqq
Reference for the communication protocol between the JavaScript editor (CodeMirror or Monaco) and the C++/Qt UI layer via QWebChannel.
2.3k GitHub stars~3.2k tokensUpdated yesterday
DevelopmentAuto-check passed
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
.NET Crash Dump Collection
dotnet/skills
Official
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
5.6k GitHub starsUsed in 2 repos~1.1k tokens
DevOps & CloudAuto-check passed
Sokol Net
elix22/Sokol.NET
Sokol.NET framework development — use for ANY work in this repo: creating or debugging examples, building/running for desktop/Android/iOS/Web, writing or compiling shaders, adding a new C/C++…
154 GitHub stars~2.8k tokensUpdated yesterday
Game DevelopmentAuto-check passed
Run Maui App
tig/winprint
Build, launch, screenshot, and drive the WinPrint.Maui Windows app (winprint.exe) — including UIA automation of the File button and native Open dialog, and pixel capture that works for WinUI3 content.
101 GitHub stars~1.2k tokensUpdated 1 mo ago
MobileAuto-check passed
Maui AI Debugging
Redth/Maui.Gtk
End-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps as an AI agent.
101 GitHub stars~4.1k tokensUpdated 5 mo ago
MobileAuto-check passed

More from DataDog/dd-trace-dotnet

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 Error
DataDog/dd-trace-dotnet
Official
Error Stack Trace Analysis for dd-trace-dotnet. An agent skill from DataDog/dd-trace-dotnet.
573 GitHub stars~634 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

Questions about Bump Libdatadog

What does Bump Libdatadog do?

Update/bump the libdatadog native library version in dd-trace-dotnet. Bump Libdatadog is an agent skill from DataDog/dd-trace-dotnet, published by the product's own GitHub organization. Update/bump the libdatadog native library version in dd-trace-dotnet.

When should I use Bump Libdatadog?

Bump Libdatadog fits situations like: the user asks to bump; upgrade libdatadog; mentions a new libdatadog release version.

How do I install Bump Libdatadog in Claude Code?

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

How do I install Bump Libdatadog in Codex?

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

Can I use Bump Libdatadog 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 bump-libdatadog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-libdatadog, .gemini/skills/bump-libdatadog, .github/skills/bump-libdatadog and .opencode/skills/bump-libdatadog in your project.

What does Bump Libdatadog need to run?

Going by SKILL.md and its folder, Bump Libdatadog needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Bump Libdatadog access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Bump Libdatadog 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Bump Libdatadog use?

Bump Libdatadog 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 Bump Libdatadog use?

About 1.7k tokens (SKILL.md is roughly 7k 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 Bump Libdatadog?

Skills that share tags, products or a category with Bump Libdatadog: JS Cpp Protocol (notepadqq/notepadqq, 2.3k stars), Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars), .NET Crash Dump Collection (dotnet/skills, 5.6k stars) and Sokol Net (elix22/Sokol.NET, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Libdatadog?

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.

Install Bump Libdatadog

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bump libdatadog Version

Overview

Files to Modify

1. Linux/macOS — build/cmake/FindLibdatadog.cmake

2. Windows — build/vcpkg_local_ports/libdatadog/

Step-by-Step Procedure

Step 1: Determine target version

Step 2: Get hashes from the release page

Step 3: Update build/cmake/FindLibdatadog.cmake

Step 4: Update build/vcpkg_local_ports/libdatadog/vcpkg.json

Step 5: Update build/vcpkg_local_ports/libdatadog/portfile.cmake

Step 6: Verify

Files That May Need Regeneration

Optional Updates (doc-comment SHAs)

Related Files (no changes needed, but useful context)

Important Notes

Files

Compare with similar skills

Similar skills

More from DataDog/dd-trace-dotnet

Related

Questions about Bump Libdatadog

1. Linux/macOS — `build/cmake/FindLibdatadog.cmake`

2. Windows — `build/vcpkg_local_ports/libdatadog/`

Step 3: Update `build/cmake/FindLibdatadog.cmake`

Step 4: Update `build/vcpkg_local_ports/libdatadog/vcpkg.json`

Step 5: Update `build/vcpkg_local_ports/libdatadog/portfile.cmake`