Cloud Native Distributed Tracing
Use when the user asks about traceparent and W3C trace context, baggage, tail vs head sampling, tracing Kafka messages, span links, or Jaeger/Tempo trace correlation across services. Produces an end-to-end tracing design: propagation, sampling and collector topology. Not for OTel SDK and Collector rollout (use devops-opentelemetry) or metrics alerting (use prometheus-grafana).
Install
npx skills add j4flmao/agent-skills --skill cloud-native-distributed-tracinggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/cloud-native/distributed-tracing ~/.claude/skills/cloud-native-distributed-tracingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Distributed Tracing Architecture
## Purpose
Make every request traceable across services, queues, and async jobs without unbounded cost. The hard parts are context propagation across non-HTTP boundaries and choosing a sampling design that keeps errors and slow traces while discarding routine ones.
## Agent Protocol
### Trigger
"distributed tracing", "trace context", "traceparent", "baggage", "tail sampling", "head sampling", "trace kafka", "jaeger", "trace correlation", "span links".
### Input Context
- Languages/frameworks, messaging systems (Kafka, SQS, RabbitMQ), service mesh presence.
- Trace volume (spans/s) and backend (Jaeger, Tempo, vendor APM).
- What must be kept (errors, latency outliers, specific tenants).
### Output Artifact
Propagation plan, sampling policy, Collector config. No file unless requested.
### Response Format
```
Propagators: {tracecontext,baggage[,b3]}
Sampling: head={ratio} | tail={policies}
Collector topology: {agent -> load-balancing exporter -> tail-sampling gateway -> backend}
Async boundaries: {how context crosses each queue}
```
### Completion Criteria
- [ ] Every boundary (HTTP, gRPC, each queue) propagates context.
- [ ] Sampling keeps 100% of errors if tail sampling is used.
- [ ] Logs carry `trace_id`/`span_id` for correlation.
## W3C Trace Context
`traceparent: 00-<trace-id 32 hex>-<parent-id 16 hex>-<trace-flags 2 hex>`
- `00` = version; trace-flags bit `01` = sampled.Details
- Skill name
cloud-native-distributed-tracing- Repository
- j4flmao/agent-skills
- Path
skills/cloud-native/distributed-tracing/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Cloud Native Distributed Tracing skill do?
Use when the user asks about traceparent and W3C trace context, baggage, tail vs head sampling, tracing Kafka messages, span links, or Jaeger/Tempo trace correlation across services. Produces an end-to-end tracing design: propagation, sampling and collector topology. Not for OTel SDK and Collector rollout (use devops-opentelemetry) or metrics alerting (use prometheus-grafana).
How do I install the Cloud Native Distributed Tracing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill cloud-native-distributed-tracing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cloud Native Distributed Tracing popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Data Data Quality
45j4flmao/agent-skills
Use when the user asks to add data quality checks to the pipeline, data validation, Great Expectations (GX Core), dbt tests, Soda checks, data profiling or quality dimensions and SLAs. Produces check suites, thresholds and where they run in the pipeline. Not for test strategy and regression diffs (use data-testing) or monitoring (use data-data-observability).
AI Ab Testing System
39lionelsimai/claude-skills-collection
Build AI A/B test analysis systems. TRIGGERS - Use when user needs help with ai-ab-testing-system related tasks.
Data Testing
45j4flmao/agent-skills
Use when the user asks about dbt unit tests, data regression testing, data-diff / Datafold, Soda or GX tests in CI, or testing data pipelines before deploy. Produces a layered data test strategy with unit, contract and diff tests. Not for runtime quality monitors (use data-data-observability) or CI wiring (use data-pipeline-cicd).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.