CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel

OpenTelemetry guidance for VS Code agent experiences. Use when changing Agent Host telemetry, local Copilot Chat telemetry, provider-native spans or metrics, OTel settings and managed policy, trace persistence/export, or monitoring documentation.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 dense, high-quality procedural skill: concrete file paths, function names, setting IDs, and runnable validation commands throughout, with explicit sequencing via checklists and an explicit policy of delegating exhaustive signal tables to authoritative external documents. The only notable gaps are minor redundancy between inline rules and the Anti-patterns section, and the absence of an explicit test-failure feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and procedural throughout — ownership maps as directory trees, numbered checklists, explicit rules ('Never add a new VS Code setting merely to mirror a new runtime-owned managed setting') — with zero explanation of concepts Claude already knows (no OTel primer, no library introductions). It falls short of anchor 5 only because the Anti-patterns section reiterates points already made inline ('Treating deprecated extension-host Copilot CLI code as the current architecture', 'Assuming runtime main matches the package bundled by VS Code', 'Claiming all providers support the same OTLP protocols'), which could be trimmed.

4 / 5

Actionability

Fully executable and specific throughout: exact setting prefixes ('chat.agentHost.otel.*', 'github.copilot.chat.otel.*'), exact functions and files to touch ('buildAgentHostOTelEnv() in common/agentService.ts', 'resolveOTelConfig() in extensions/copilot/src/platform/otel/common/otelConfig.ts'), concrete attribute conventions ('github.copilot.*', 'service.namespace=vscode.agent-host'), and copy-paste-ready test commands ('./scripts/test.sh --grep "AgentHostOTel\|agent host.*OTel"', 'npx tsc --noEmit --project tsconfig.json') covering both surfaces.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: the four-step version-discipline procedure, seven-step Agent Host configuration checklist, six-step signal checklist, and a validation section with runnable commands plus a documentation-only verification list ('every relative link resolves; setting and command IDs exist in source...'). It sits at anchor 4 rather than 5 because there is no explicit fix-and-retry feedback loop (e.g., what to do when the integration test fails), though the doc-vs-source discrepancy rule ('verify with tests and call out the discrepancy') partially compensates and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

Exemplary disclosure discipline for a bundleless skill: the body is explicitly procedural ('Keep this skill procedural. Do not duplicate complete settings, environment-variable, attribute, event, or metric tables here') and delegates exhaustive detail one level deep to clearly signaled authoritative documents with links ([OTEL.md](../../../src/vs/platform/agentHost/OTEL.md), agent_monitoring.md, the runtime's monitor.md at an immutable revision). Sections are well-organized with a routing table, ownership maps, and checklists making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

73%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 well-scoped, niche description with an explicit and unusually specific 'Use when' trigger clause covering six concrete areas. The main weakness is the thin capability statement: 'guidance' is generic, so the description leans on its when-clause to convey what the skill actually does.

Suggestions

Replace the generic verb 'guidance' with concrete actions, e.g., 'Change, audit, and document OpenTelemetry instrumentation for VS Code agent experiences...' to lift the capability statement to the same concreteness as the trigger clause.

Add one or two natural trigger synonyms such as 'tracing', 'instrumentation', or 'OTLP export' that contributors commonly use when referring to telemetry work.

Consider stating the outcome or scope of the guidance (e.g., routing modes, settings, provider-native signals) so the 'what' answers what kind of guidance is provided, not just that it exists.

DimensionReasoningScore

Specificity

The description names the domain ('OpenTelemetry guidance for VS Code agent experiences') and the when-clause enumerates concrete surfaces ('Agent Host telemetry, local Copilot Chat telemetry, provider-native spans or metrics, OTel settings and managed policy, trace persistence/export'), but the capability verb is the generic 'guidance' — it never states concrete actions like auditing, changing, or adding telemetry. This matches anchor 3 (names domain with some concreteness, not comprehensive action coverage) rather than anchor 4, which expects several specific actions listed.

3 / 5

Completeness

Both parts are present: 'OpenTelemetry guidance for VS Code agent experiences' states what it is, and an explicit 'Use when changing...' clause with six concrete trigger areas states when to use it. It falls just short of anchor 5 because the 'what' is a single generic noun ('guidance') rather than concrete capability statements — the actual actions are only implied by the when-clause.

4 / 5

Trigger Term Quality

Strong natural keyword coverage within its niche: 'OpenTelemetry', 'OTel' (both the abbreviation and full name), 'Agent Host telemetry', 'Copilot Chat', 'spans', 'metrics', 'managed policy', 'trace persistence/export', 'monitoring documentation' — terms a VS Code contributor would naturally say. Not anchor 5 because common variations like 'tracing', 'instrumentation', 'OTLP', or 'exporters' are absent.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — OpenTelemetry specifically for VS Code agent surfaces (Agent Host, Copilot Chat) — with distinct triggers like 'chat.agentHost.otel'-adjacent terminology that no general skill would claim. Minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/otel/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.