New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Setting Up Distributed Tracing

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Execute this skill automates the setup of distributed tracing for microservices.

MITAuto-check passedDevOps & Cloud

Install Setting Up Distributed Tracing

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-distributed-tracing -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace setting-up-distributed-tracing --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/setting-up-distributed-tracing .claude/skills/setting-up-distributed-tracing && 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
setting-up-distributed-tracing
GitHub stars
2.8k
Token cost
~896 tokens
SKILL.md length
374 words
Files
5 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Execute this skill automates the setup of distributed tracing for microservices.

  • Works in 3 steps: Backend Selection: Determines the… → Instrumentation Strategy: Designs an… → Configuration Generation: Generates the…
  • Appropriate context detected
  • SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Setting Up Distributed Tracing is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute this skill automates the setup of distributed tracing for microservices. it helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. use this skill when the user re... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Observability and Microservices. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Appropriate context detected
  • With relevant phrases based on skill purpose

Example prompts

  • “/setting-up-distributed-tracing”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(cmd:*)

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Backend Selection: Determines the preferred tracing backend (e.g., Jaeger, Zipkin, Datadog).
  2. Instrumentation Strategy: Designs an instrumentation strategy for each service, focusing on key operations and dependencies.
  3. Configuration Generation: Generates the necessary configuration files and code snippets to enable distributed tracing.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(cmd:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    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.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Setting Up Distributed Tracing loads about 896 tokens when it runs, and up to ~913 if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 374 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~896
With references · SKILL.md plus every file in references/, read only if the agent opens them
~913

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 374 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/setting-up-distributed-tracing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
setting-up-distributed-tracing
description
Execute this skill automates the setup of distributed tracing for microservices. it helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. use this skill when the user re... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(cmd:*)
compatibility
Designed for Claude Code
version
1.22.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
performance, microservices, tracing

Distributed Tracing Setup

Set up distributed tracing for microservices using OpenTelemetry, Jaeger, or Zipkin with context propagation, span creation, and trace collection configuration.

Overview

This skill streamlines the process of setting up distributed tracing in a microservices environment. It guides you through the key steps of instrumenting your services, configuring trace context propagation, and selecting a backend for trace collection and analysis, enabling comprehensive monitoring and debugging.

How It Works

  1. Backend Selection: Determines the preferred tracing backend (e.g., Jaeger, Zipkin, Datadog).
  2. Instrumentation Strategy: Designs an instrumentation strategy for each service, focusing on key operations and dependencies.
  3. Configuration Generation: Generates the necessary configuration files and code snippets to enable distributed tracing.

When to Use This Skill

This skill activates when you need to:

  • Implement distributed tracing in a microservices application.
  • Gain end-to-end visibility into request flows across multiple services.
  • Troubleshoot performance bottlenecks and latency issues.

Examples

Example 1: Adding Tracing to a New Microservice

User request: "setup tracing for the new payment service"

The skill will:

  1. Prompt for the preferred tracing backend (e.g., Jaeger).
  2. Generate code snippets for OpenTelemetry instrumentation in the payment service.
Example 2: Troubleshooting Performance Issues

User request: "implement distributed tracing to debug slow checkout process"

The skill will:

  1. Guide the user through instrumenting relevant services in the checkout flow.
  2. Provide configuration examples for context propagation.
Show full SKILL.md (149 more words)Show less

Best Practices

  • Backend Choice: Select a tracing backend that aligns with your existing infrastructure and monitoring tools.
  • Sampling Strategy: Implement a sampling strategy to manage trace volume and cost, especially in high-traffic environments.
  • Context Propagation: Ensure proper context propagation across all services to maintain trace continuity.

Integration

This skill can be used in conjunction with other plugins to automate the deployment and configuration of tracing infrastructure. For example, it can integrate with infrastructure-as-code tools to provision Jaeger or Zipkin clusters.

Prerequisites

  • Appropriate file access permissions
  • Required dependencies installed

Instructions

  1. Invoke this skill when the trigger conditions are met
  2. Provide necessary context and parameters
  3. Review the generated output
  4. Apply modifications as needed

Output

The skill produces structured output relevant to the task.

Error Handling

  • Invalid input: Prompts for correction
  • Missing dependencies: Lists required components
  • Permission errors: Suggests remediation steps

Resources

  • Project documentation
  • Related skills and commands

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

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/.curated/setting-up-distributed-tracing of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md
  • scripts/setup_jaeger.py

Open the folder on GitHubat commit cfae287

Compare with similar skills

Setting Up Distributed Tracing 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.

Setting Up Distributed Tracing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Setting Up Distributed Tracing this skilljeremylongshore/tons-of-skills-marketplace2.8k—~896Automated safety check: PassMIT
Distributed Tracingwshobson/agents40k12 repos~527Automated safety check: PassMIT
Add Metricmicrobus-io/fabric172—~1.5kAutomated safety check: PassApache-2.0
Aspire Service DefaultsAaronontheweb/dotnet-skills1.2k1 repos~2.6kAutomated safety check: PassMIT
Dt Obs ServicesDynatrace/dynatrace-for-ai163—~3.3kAutomated safety check: PassApache-2.0
Service Mesh Expertaiskillstore/marketplace4337 repos~686Automated safety check: PassNone

Similar skills

  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 12 repos~527 tokens
    DevOps & CloudAuto-check passed

  • Add Metric

    microbus-io/fabric

    TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.

    172 GitHub stars~1.5k tokensUpdated 13 days ago
    DevOps & CloudAuto-check passed

  • Aspire Service Defaults

    Aaronontheweb/dotnet-skills

    Sets up a shared ServiceDefaults project for .NET Aspire apps that centralizes OpenTelemetry, health checks, HTTP resilience and service discovery for every service.

    1.2k GitHub starsUsed in 1 repo~2.6k tokens
    DevOps & CloudAuto-check passed

  • Dt Obs Services

    Dynatrace/dynatrace-for-ai

    Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go.

    163 GitHub stars~3.3k tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed

  • Service Mesh Expert

    aiskillstore/marketplace

    Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns.

    433 GitHub starsUsed in 7 repos~686 tokens
    DevOps & CloudAuto-check passed

  • Backend Design

    itseffi/agentic-os

    Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

    114 GitHub stars~474 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Setting Up Distributed Tracing

What does Setting Up Distributed Tracing do?

Execute this skill automates the setup of distributed tracing for microservices. Setting Up Distributed Tracing is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute this skill automates the setup of distributed tracing for microservices.

When should I use Setting Up Distributed Tracing?

Setting Up Distributed Tracing fits situations like: appropriate context detected; with relevant phrases based on skill purpose.

How do I install Setting Up Distributed Tracing in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-distributed-tracing -a claude-code`. Or copy the skill folder (skills/.curated/setting-up-distributed-tracing in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/setting-up-distributed-tracing in your project. Claude Code loads it when a task matches its description.

How do I install Setting Up Distributed Tracing in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-distributed-tracing -a codex`. Or copy the skill folder (skills/.curated/setting-up-distributed-tracing in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/setting-up-distributed-tracing in your project. Codex loads it when a task matches its description.

Can I use Setting Up Distributed Tracing 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 jeremylongshore/tons-of-skills-marketplace --skill setting-up-distributed-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-up-distributed-tracing, .gemini/skills/setting-up-distributed-tracing, .github/skills/setting-up-distributed-tracing and .opencode/skills/setting-up-distributed-tracing in your project.

What does Setting Up Distributed Tracing need to run?

Going by SKILL.md and its folder, Setting Up Distributed Tracing needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Setting Up Distributed Tracing 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 Setting Up Distributed Tracing 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 Setting Up Distributed Tracing use?

Setting Up Distributed Tracing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setting Up Distributed Tracing use?

About 896 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17 tokens, read only when the agent opens those files.

What are the alternatives to Setting Up Distributed Tracing?

Skills that share tags, products or a category with Setting Up Distributed Tracing: Distributed Tracing (wshobson/agents, 40k stars), Add Metric (microbus-io/fabric, 172 stars), Aspire Service Defaults (Aaronontheweb/dotnet-skills, 1.2k stars) and Dt Obs Services (Dynatrace/dynatrace-for-ai, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setting Up Distributed Tracing?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.