Otel expert

Skill bg-szy/TOP-SKILLS/skills/marketplace/otel-expert

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill otel-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

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