otel-dotnet

OpenTelemetry in .NET — DI/builder SDK setup (OpenTelemetry.Extensions.Hosting, AddOpenTelemetry, UseOtlpExporter, OpenTelemetrySdk.Create), native .NET instrumentation APIs (ActivitySource, System.Diagnostics.Metrics Meter) plus logging abstractions (ILogger), zero-code CLR-profiler agent, contrib instrumentation packages, performance tuning, and breaking-change audits. Use when adding, reviewing, or configuring OpenTelemetry in a .NET or ASP.NET Core service. Triggers on "setup otel in dotnet", "dotnet telemetry", ".net tracing", "ASP.NET Core opentelemetry", "AddOpenTelemetry", "UseOtlpExporter", "OpenTelemetrySdk.Create", "ActivitySource", "System.Diagnostics.Metrics Meter", "ILogger opentelemetry", "OpenTelemetry.Extensions.Hosting", "opentelemetry-dotnet-instrumentation", or any C# OTel question.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured reference hub: concise, with concrete executable fetch commands for version facts and a clear task-to-reference routing table. All referenced bundle files exist and stay one level deep, so progressive disclosure is clean.

Dimension	Reasoning	Score
Conciseness	The ~35-line body is lean throughout, assumes Claude knows what OpenTelemetry and .NET are, and avoids padded explanation, matching the 'every token earns its place' anchor.	3 / 3
Actionability	The 'Sources of Truth' table provides copy-paste-ready commands (gh api ... -q '.tag_name', WebFetch https://www.nuget.org/...) and the references table gives concrete task-to-file routing, satisfying the fully-executable anchor for a hub skill.	3 / 3
Workflow Clarity	As a single-action router ('Load a reference below based on the task'), the 'Use when' column makes the routing decision unambiguous; no destructive or batch operations exist in the body that would require validation checkpoints.	3 / 3
Progressive Disclosure	A clear overview points to five well-signaled references that are one level deep, each verified to exist as a real file in references/, with no nested 'see X -> see Y' chains, matching the score-3 anchor.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: it enumerates concrete .NET OpenTelemetry capabilities, supplies explicit 'Use when' guidance, and packs in natural trigger terms plus distinctive API-name triggers. Only minor risk is the broad catch-all phrase, which does not materially undermine distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('DI/builder SDK setup', 'zero-code CLR-profiler agent', 'performance tuning', 'breaking-change audits') rather than vague language, matching the score-3 anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated capability set) and when via 'Use when adding, reviewing, or configuring OpenTelemetry in a .NET or ASP.NET Core service' plus the trigger list, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	A dedicated 'Triggers on' list includes natural user phrases ('setup otel in dotnet', 'dotnet telemetry', '.net tracing', 'ASP.NET Core opentelemetry') alongside API identifiers, giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	A sharply .NET-specific niche anchored on .NET-only API names (AddOpenTelemetry, OpenTelemetrySdk.Create) makes it unlikely to fire for unrelated skills, despite a slightly broad 'any C# OTel question' catch-all.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-dotnet/SKILL.md
Commit: c5d2edc

Reviewed: about 1 hour ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.