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

96%

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

92%Weight 40%Scale 1-5

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

A well-structured navigation skill: concise overview, a verified reference table with clear use-conditions, and executable source-of-truth commands. The only blemish is mild redundancy between the Sources of Truth note and the Cross-References section.

Suggestions

Remove the duplicate otel-declarative-config / '.NET not yet implemented' mention from 'Cross-References' since it already appears in 'Sources of Truth', or fold the sibling-skill pointers into the Sources of Truth table.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'Cross-References' section repeats the otel-declarative-config / '.NET not yet implemented' note already stated in 'Sources of Truth'. Not a 5 because of that minor redundancy; not a 3 because the rest is efficient and unpadded.	4 / 5
Actionability	Provides concrete copy-paste-ready commands ('gh api repos/open-telemetry/opentelemetry-dotnet/releases/latest -q '.tag_name'', 'WebFetch https://www.nuget.org/packages/<PackageId>') and a task→file routing table. Not a 4 because the commands are fully executable and cover the common fact-fetching cases.	5 / 5
Workflow Clarity	This is a simple single-purpose navigation skill whose single action — 'Load a reference below based on the task' — is made unambiguous by the 'Use when' column, with no destructive or batch operations requiring validation. Not a 4 because the routing is fully explicit.	5 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references (all five referenced files verified present: setup.md, api.md, instrumentation-libraries.md, performance.md, breaking-changes.md), bulk detail split into those files. Not a 4 because navigation is clean and references are exactly one level deep.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 dense, well-constructed description that covers what the skill does, when to use it, and the natural/technical triggers, all in third person. Verbosity is information-dense rather than padded.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions with comprehensive coverage — 'DI/builder SDK setup', 'native .NET instrumentation APIs', 'logging abstractions (ILogger)', 'zero-code CLR-profiler agent', 'contrib instrumentation packages', 'performance tuning', and 'breaking-change audits' — each backed by concrete API names. Not a 4 because coverage is comprehensive rather than having minor gaps.	5 / 5
Completeness	Explicitly answers 'what' (the enumerated capability areas) and 'when' ('Use when adding, reviewing, or configuring OpenTelemetry in a .NET or ASP.NET Core service') with concrete trigger phrases. Not a 4 because both halves are explicit and concrete rather than one being merely implied.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural phrases users say ('setup otel in dotnet', 'dotnet telemetry', '.net tracing', 'ASP.NET Core opentelemetry', 'any C# OTel question') plus the API identifiers developers reference. Not a 4 because both natural synonyms and technical identifiers are present.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to OpenTelemetry in .NET/ASP.NET Core with .NET-specific triggers, giving a clear niche with minimal overlap with sibling OTel skills. Not a 4 because the triggers are language-specific and unlikely to fire for the wrong skill.	5 / 5
	Total	20 / 20 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: 8e6ed41

Reviewed: 16 hours 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.