otel_instrument

Route OpenTelemetry requests to the appropriate specialized sub-skill.

20|6|Updated Jan 16, 2026

Search Tags:#routing #delegation #observability #instrumentation #opentelemetry #otel #semantic-conventions

Ready to run

npx skills add https://github.com/adrielp/ai-engineering-harness --skill otel-instrument

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel_instrument
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/otel_instrument
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill otel-instrument

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenTelemetry orchestrator — auto-activates on observability, telemetry, tracing, metrics, logging, OTel SDK, Collector, semantic conventions, or OTTL requests. Routes to the correct sub-skill instead of attempting a generic solution.

Core Features & Use Cases

Intent-driven routing to the appropriate otel_* sub-skill (e.g., otel_instrumentation, otel_collector, otel_ottl, otel_semantic_conventions).
Minimal context gathering and routing decisions based on user input to preserve efficiency.
Safe fallbacks and clear delegation when multiple matches could apply.

Quick Start

Describe your OpenTelemetry task in plain language and otel_instrument will route it to the correct sub-skill.

Frequently Asked Questions about otel_instrument

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

FAQPage Schema

How do I route OpenTelemetry tasks to the correct instrumentation or collector workflow?▼

You can route OpenTelemetry work by describing your telemetry task in plain language. The system analyzes your intent and delegates the request to the appropriate sub-skill, covering instrumentation, collectors, semantic conventions, or OTTL transformations.

What is semantic convention routing for OpenTelemetry observability?▼

Semantic convention routing directs OpenTelemetry observability requests to a specialized sub-skill. It identifies whether your task involves tracing, metrics, logging, or semantic standards, and safely delegates the work instead of attempting a generic solution.

Can I use this to configure both OpenTelemetry SDK instrumentation and Collector pipelines?▼

Yes, you can use it for both OpenTelemetry SDK instrumentation and Collector pipelines. It identifies your specific observability requirements and routes the configuration work to the appropriate dedicated sub-skill for safe delegation.

How do I apply OTTL transformations across my application services?▼

To apply OTTL transformations across application services, the orchestrator identifies your processing intent and routes the request to a specialized OTTL sub-skill. This ensures your telemetry data transformations are handled by targeted logic rather than generic configurations.

What happens when an OpenTelemetry request matches multiple sub-skills?▼

When an OpenTelemetry request matches multiple sub-skills, the system applies first-match routing with safe fallbacks. It prioritizes the most relevant intent identified in your request and provides clear delegation to prevent conflicting telemetry configurations.