otel-tracing

Enforce OpenTelemetry span creation, context propagation, and semantic conventions.

19|Updated Jan 30, 2026

Search Tags:#observability #distributed systems #tracing #instrumentation #opentelemetry #spans #context propagation

Ready to run

npx skills add https://github.com/xobotyi/cc-foundry --skill otel-tracing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel-tracing
Source: https://github.com/xobotyi/cc-foundry/tree/main/plugins/backend/skills/otel-tracing
Command: npx skills add https://github.com/xobotyi/cc-foundry --skill otel-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you correctly instrument your distributed systems using OpenTelemetry, ensuring that traces accurately capture the flow of requests and identify performance bottlenecks or errors.

Core Features & Use Cases

Correct Span Creation: Guides on naming spans, setting SpanKind, and ensuring spans are always ended.
Context Propagation: Ensures trace context is correctly propagated across service boundaries using W3C Trace Context.
Error Handling: Details on recording exceptions and setting span status to Error.
Use Case: When developing a new microservice, use this Skill to ensure all outgoing HTTP requests and incoming API calls are correctly traced, allowing you to see the full request lifecycle in your observability backend.

Quick Start

Apply OpenTelemetry tracing conventions to the provided code snippet for instrumenting an HTTP client.

Frequently Asked Questions about otel-tracing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I propagate trace context across microservices using OpenTelemetry?▼

Trace context is propagated across microservices using the W3C Trace Context standard to ensure distributed requests are correctly correlated. This Skill enforces proper context propagation rules across service boundaries so you can visualize the complete request lifecycle.

How do I record errors and exceptions in OpenTelemetry spans?▼

To record errors in OpenTelemetry spans, you must record the exception details and set the span status to Error. This Skill enforces correct error handling discipline to ensure operational issues are accurately captured in your observability backend.

What is the correct way to name OpenTelemetry spans and set SpanKind?▼

Correct span creation requires following semantic conventions for naming spans and accurately setting the SpanKind attribute. This Skill enforces span naming discipline to ensure traces capture meaningful data and identify performance bottlenecks effectively.

How do I instrument an HTTP client for distributed tracing?▼

Instrumenting an HTTP client requires applying OpenTelemetry tracing conventions to capture outgoing requests and ensure spans are always ended. This Skill guides the instrumentation process to accurately track the full request flow across distributed systems.

Why does my distributed tracing fail to correlate requests across services?▼

Distributed tracing fails to correlate requests when W3C Trace Context propagation rules are not followed across service boundaries. This Skill enforces strict context propagation discipline to prevent broken trace chains and ensure accurate observability.