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

91%

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

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.

An exemplary procedural skill body: it assumes Claude's competence, gives exact files, functions, setting IDs, and test commands, sequences every multi-step change with explicit validation checkpoints, and deliberately defers exhaustive signal/settings tables to well-signaled authoritative documents one level deep. The only improvement space is trimming minor duplicated warnings about the deprecated extension-host CLI architecture.

DimensionReasoningScore

Conciseness

The body is almost entirely directive — ownership trees, checklists, exact settings prefixes, and validation commands — with zero explanation of concepts Claude already knows (no "what is OpenTelemetry" padding). It misses anchor 5 only through minor redundancy: the deprecated extension-host CLI warning appears both as "Do not use it as a model for new work" and again as the anti-pattern "Treating deprecated extension-host Copilot CLI code as the current architecture", and the intro table's two-pipeline split is restated in prose under "Current architecture".

4 / 5

Actionability

Guidance is copy-paste executable and file/function-specific: "./scripts/test-integration.sh --run src/vs/platform/agentHost/test/node/otel/agentHostOTelService.integrationTest.ts", "pnpm exec tsc --noEmit --project tsconfig.json", "Update ... buildAgentHostOTelEnv() in common/agentService.ts", "Update resolveOTelConfig() in extensions/copilot/src/platform/otel/common/otelConfig.ts", plus concrete attribute namespaces ("gen_ai.*", "github.copilot.*") and "Pass free-form content through truncateForOTel with the configured maximum". Commands, paths, and functions cover the common cases with no gaps, matching anchor 5 rather than anchor 4.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the runtime version discipline steps end with "Use runtime `main` only after confirming that the relevant files are unchanged from the bundled revision", both configuration checklists end with "Add focused ... tests", and a dedicated Validation section gives the smallest-check commands plus a doc-only verification list ("every relative link resolves; setting and command IDs exist in source..."). An explicit error-recovery rule — "If executable source and documentation disagree, verify with tests and call out the discrepancy rather than silently selecting one" — completes the anchor-5 fit; checkpoints are explicit, so anchor 4's "minor validation gaps" does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the skill correctly keeps exhaustive material out of SKILL.md by pointing one level deep to authoritative repo documents: the surface table links to src/vs/platform/agentHost/OTEL.md and extensions/copilot/docs/monitoring/agent_monitoring.md, defers native Copilot signals to the runtime's docs/developer-docs/monitor.md at the bundled revision, and states "Keep this skill procedural. Do not duplicate complete settings, environment-variable, attribute, event, or metric tables here." References are clearly signaled with paths and purpose, and navigation is easy — a clean match for anchor 5.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong description: it pairs a clear (if slightly generic) capability statement with an explicit, concrete "Use when" trigger clause covering both VS Code OTel pipelines and their synonyms. Trigger-term coverage and distinctiveness are excellent; the only soft spot is that the leading action verb ("guidance") is generic rather than enumerating distinct concrete actions.

DimensionReasoningScore

Specificity

"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" enumerates six concrete change areas with precise terminology. It falls short of anchor 5 because the core capability verb is generic ("OpenTelemetry guidance") rather than multiple distinct concrete actions, and exceeds anchor 3 because far more than 1-2 specific areas are named.

4 / 5

Completeness

The description explicitly answers both questions: what — "OpenTelemetry guidance for VS Code agent experiences"; when — an explicit "Use when changing..." clause listing concrete trigger areas. This matches the anchor-5 pattern of clear what plus concrete trigger phrases, and the 'when' is specific enough that it does not fit anchor 4's "could be more explicit".

5 / 5

Trigger Term Quality

Natural terms a contributor would say are well covered: "OpenTelemetry" plus its synonyms "OTel" and "telemetry", "spans", "metrics", "Agent Host", "Copilot Chat", "trace persistence/export", "monitoring documentation". Not 5 because a few natural variations are missing (e.g., "OTLP", "tracing", "exporter", "observability"); not 3 because coverage includes the full synonym set and signal-specific vocabulary rather than only some relevant keywords.

4 / 5

Distinctiveness Conflict Risk

"Agent Host telemetry", "local Copilot Chat telemetry", "provider-native spans or metrics", and "VS Code agent experiences" carve out a clear niche with distinct triggers and minimal conflict risk. It sits above anchor 4 because every trigger is scoped to OTel/telemetry surfaces; the only mildly broad item is "monitoring documentation".

5 / 5

Total

18

/

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.