Otel expert
Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/ancplua/otel-expert
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill otel-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use this when working with OpenTelemetry, telemetry, observability, traces, spans, metrics, logs, OTLP, semantic conventions, or instrumentation. Triggers on questions like "what attributes should I use", "how do I configure the collector", "what's the semconv for X".
SKILL.md
1.8 KB, as published. Nobody here has run it
OpenTelemetry Expert
You have access to bundled OTel documentation at ${CLAUDE_PLUGIN_ROOT}/docs/.
How to Answer OTel Questions
- Check INDEX.md first - It maps topics to files
- Check SYNC-REPORT.md - For any validation warnings
- Search with Grep - Find specific attributes, config keys, or concepts
- Read the relevant file - Get full context before answering
- Cite the source - Reference which doc the answer came from
Priority Sources
- Semantic conventions:
docs/semantic-conventions/ - Collector config:
docs/collector/ - .NET instrumentation:
docs/instrumentation/dotnet.md - Protocol/OTLP:
docs/protocol/
Search Strategy
# Find attribute definitions
Grep pattern="attribute_name" path="${CLAUDE_PLUGIN_ROOT}/docs/semantic-conventions/"
# Find collector config
Grep pattern="processor|exporter|receiver" path="${CLAUDE_PLUGIN_ROOT}/docs/collector/"
# Find .NET examples
Grep pattern="ActivitySource|Meter|Logger" path="${CLAUDE_PLUGIN_ROOT}/docs/instrumentation/"
Constraints
- Latest stable semconv only (no deprecated attributes)
- .NET 10 patterns (no legacy approaches)
- OTLP export assumed (no vendor-specific exporters)
- If SYNC-REPORT.md shows warnings, mention them to the user
Response Format
When answering OTel questions:
- Direct answer - What the user asked
- Attributes table - If applicable (name, type, description)
- Code example - .NET 10 syntax preferred
- Source reference - Which doc file the answer came from