Help us improve
Share bugs, ideas, or general feedback.
From vanguard-frontier-agentic
Reviews OpenTelemetry wiring in ASP.NET Core services: SDK registration, trace propagation, structured logging, metrics, sampling, PII leaks, and health check distinction.
npx claudepluginhub raishin/vanguard-frontier-agentic --plugin vanguard-frontier-agenticHow this skill is triggered — by the user, by Claude, or both
Slash command
/vanguard-frontier-agentic:dotnet-observability-otel-reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill reviews how an ASP.NET Core service wires its own OpenTelemetry — the SDK registration, the instrumentation it enables, the logs it emits, the metrics it records, and the sampling it applies. Telemetry only helps an operator if traces propagate across service calls, logs carry a trace identifier, exceptions keep their structure, and the application does not write secrets or customer ...
Configures structured logging with Serilog, OpenTelemetry tracing/metrics, health checks, and correlation IDs for .NET 10 applications.
Adding observability. OpenTelemetry traces/metrics/logs, health checks, custom metrics.
Guides OpenTelemetry instrumentation setup across multiple languages (Node.js, Go, Python, Java, .NET, Ruby, PHP, browser, Next.js). Covers spans, metrics, logs, resource attributes, sampling, and sensitive data handling.
Share bugs, ideas, or general feedback.
This skill reviews how an ASP.NET Core service wires its own OpenTelemetry — the SDK registration, the instrumentation it enables, the logs it emits, the metrics it records, and the sampling it applies. Telemetry only helps an operator if traces propagate across service calls, logs carry a trace identifier, exceptions keep their structure, and the application does not write secrets or customer data into spans. The review catches PII in span attributes and log messages, missing trace context propagation on outbound calls, uncorrelated logs, exceptions logged as interpolated strings, missing request-rate/latency/error metrics, unbounded production sampling, and a health endpoint doing a readiness job. It is a static review of source and sanitized configuration; it never runs the app or contacts a telemetry backend.
EXPLICIT NON-GOAL: Collector topology, exporters and backends, and dashboard infrastructure are out of scope and belong to the opentelemetry provider board — route those there. This skill reviews only what the .NET application itself configures and emits.
Program.cs, OpenTelemetry registration, logging configuration, instrumentation code) or sanitized appsettings.HttpClient or messaging) as broken distributed tracing.confirmed (config provided), inference (config partial), assumption (config absent), or unknown.Load these only when needed:
Return, at minimum:
HttpClient, messaging instrumentation)