Zipkin Distributed Tracing Wrapper

Problem

When tracing is added to scripts, CI, or tooling, Zipkin can become another external dependency to handle manually: initialization, context, and error handling may scatter across business code. Wrap Zipkin is positioned not as a tracing backend replacement, but as a skill-oriented Wrapper that packages zipkin - Distributed tracing system into a reusable tooling surface, reducing boilerplate when wiring tracing into automated flows. It also makes tracing-related code easier to separate from core business logic when debugging external dependencies.

Core behavior and boundaries

• Wrapped target: It wraps Zipkin, a distributed tracing system, and is suited to tool, github, and automation scenarios as a callable component.
• How it fits: The skill exposes itself as a Wrapper, so callers should treat it as an abstraction over Zipkin capabilities; actual behavior depends on the target Zipkin configuration.
• Boundary: It does not replace a Zipkin server, nor does it promise storage, querying, or visualization. Endpoint, auth, sampling, and context propagation remain dependent on deployment and integration.
• Caution: The available description is brief, so confirm the actual exposed interface, parameters, and error returns before integration, rather than assuming the wrapper is a full tracing platform.