Auto-instrument Kubernetes apps with Odigos
Use Odigos to add OpenTelemetry tracing to Kubernetes or VM workloads without code changes, then route the traces to the observability backend an operator already uses.
npx skills add agentskillexchange/skills --skill auto-instrument-kubernetes-apps-with-odigos
Use Odigos when an agent or SRE operator needs trace evidence from a running service but should not edit application code to add SDK instrumentation. The workflow is to install Odigos, select the workloads to instrument, configure the OpenTelemetry destination, and collect traces, logs, and metrics for incident review or production-readiness checks. Invoke this instead of using an observability product normally when the missing step is zero-code instrumentation across existing services, especially in Kubernetes environments where the agent needs fresh telemetry before debugging or writing a remediation plan. The scope boundary is instrumentation rollout and evidence collection; it is not a general observability dashboard, tracing backend, or monitoring-platform listing.
What this skill actually does
Inputs and prerequisites: Odigos CLI, Kubernetes or supported VM environment, OpenTelemetry-compatible destination.
Setup notes: Install the Odigos CLI from the upstream installation docs, run odigos install in the target environment, choose the applications to instrument, and configure the OpenTelemetry destination for traces and related telemetry.
Source and verification boundary: use https://docs.odigos.io/quickstart/introduction as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.