From opentelemetry
Provides OpenTelemetry conventions for span naming, semantic attributes, status setting, in-memory trace testing, and instrumentation boundaries. Use when setting up tracing or writing trace tests.
npx claudepluginhub bendrucker/claude --plugin opentelemetryThis skill uses the workspace's default tool permissions.
Use short, low-cardinality names from semantic conventions:
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.
Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.
Use short, low-cardinality names from semantic conventions:
GET /users/{id} (method + route template, never full URL path)SELECT users (operation + table)grpc.health.v1.Health/Checkorders process (destination + operation)Use semantic convention attribute names — never invent your own:
http.request.method, url.full, http.response.status_code, server.addressdb.system, db.statement, db.namespaceerror.type, service.nameImport from the versioned semconv package (e.g., go.opentelemetry.io/otel/semconv/v1.x).
Only set status on errors: span.SetStatus(codes.Error, err.Error()). Never set Ok — unset is the success state. Call RecordError alongside SetStatus (it only adds a span event, doesn't change status).
For HTTP: 4xx is Error on client spans, Unset on server spans. 5xx is always Error.
Use in-memory exporters with SimpleSpanProcessor (not batch — batch introduces timing). Assert on exported spans' names, attributes, and status. No mocking needed.
Instrument network calls, I/O, and queue operations — not every function. Use span events (AddEvent) instead of separate log statements for events within a traced operation.