CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

Excellent router-style SKILL.md: lean, well-structured, with an accurate reference table (all referenced files exist, one level deep) and concrete commands for fetching current version facts instead of hardcoding stale ones. Its only limitation is inherent to the entry-point design — all direct task content lives in the references rather than the body.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence: no explanation of what OpenTelemetry is, just a routing table ("Load a reference below based on the task; each reference is self-contained"), concrete fetch commands, and cross-references. Every section earns its place, matching the 5 anchor; the only near-verbose spot ("why there is no released declarative YAML config in .NET") is a genuinely useful fact, not padding.

5 / 5

Actionability

Guidance is mostly executable: the Sources of Truth table gives copy-paste commands (`gh api repos/open-telemetry/opentelemetry-dotnet/releases/latest -q '.tag_name'`, exact `WebFetch` URLs) and the References table gives clear per-task routing criteria. It falls short of the 5 anchor because the body itself contains no direct task instructions or code snippet — all execution guidance is deferred to the reference files — while the 4 anchor ("mostly executable guidance ... with minor gaps") fits exactly.

4 / 5

Workflow Clarity

This is a simple single-purpose entry-point skill (under 50 lines), and its single action is unambiguous: "Load a reference below based on the task", with a per-file 'Use when' column making the choice deterministic. The Sources of Truth table even adds a verification path for version-sensitive facts. Per the simple-skill exception this scores 5; there are no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references: all five referenced files (setup.md, api.md, instrumentation-libraries.md, performance.md, breaking-changes.md) exist in references/, each has a 'Use when' description, and inspection of the bundle confirms the reference files link only to external URLs rather than nesting further local references. Matches the 5 anchor (easy navigation, content appropriately split).

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 high-quality description: it names concrete capabilities with real API identifiers, states an explicit 'Use when' clause, and enumerates natural trigger phrases with synonyms. It is detailed without being vague and fits its niche unambiguously.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas with specific API names — "DI/builder SDK setup (OpenTelemetry.Extensions.Hosting, AddOpenTelemetry, UseOtlpExporter, OpenTelemetrySdk.Create)", "native .NET instrumentation APIs (ActivitySource, System.Diagnostics.Metrics Meter)", "zero-code CLR-profiler agent", "performance tuning, and breaking-change audits". This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) and exceeds the 4 anchor, which only expects 'several' actions with minor gaps; there are no vague or padded phrases.

5 / 5

Completeness

Both questions are explicitly answered: 'what' via the concrete capability list, and 'when' via "Use when adding, reviewing, or configuring OpenTelemetry in a .NET or ASP.NET Core service" followed by an explicit "Triggers on ..." enumeration. This matches the 5 anchor (clearly and explicitly answers both what AND when with concrete trigger phrases); a 4 would require the 'when' to be less explicit than the dedicated trigger clause present here.

5 / 5

Trigger Term Quality

The explicit trigger list covers natural phrasings users would actually say — "setup otel in dotnet", "dotnet telemetry", ".net tracing", "ASP.NET Core opentelemetry", "any C# OTel question" — plus synonyms (otel/.NET/C#) and specific API terms ("AddOpenTelemetry", "UseOtlpExporter", "ActivitySource"). Coverage is comprehensive with synonyms, matching the 5 anchor; the 4 anchor ("a few natural terms missing") does not fit since both colloquial and technical trigger phrasings are present.

5 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — OpenTelemetry specifically in ".NET or ASP.NET Core" — with distinct triggers ("AddOpenTelemetry", "opentelemetry-dotnet-instrumentation", "setup otel in dotnet") that other skills would not claim. It matches the 5 anchor (clear niche with distinct triggers, minimal conflict risk); the catch-all "any C# OTel question" is still scoped to C#, so overlap risk stays minimal rather than 'minor but noticeable' as at 4.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.