otel

OpenTelemetry instrumentation for the Copilot Chat extension — covers the four agent execution paths, the IOTelService abstraction, span/metric/event conventions, and the relationship between code and the user/developer monitoring docs. Use when adding/changing OTel spans, metrics, or events; instrumenting a new agent surface; touching the Copilot CLI bridge or Claude span emission; or updating `extensions/copilot/docs/monitoring/agent_monitoring*.md`.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

The body is highly actionable with clear sequenced workflows and validation checkpoints, but it is a long monolithic document with no bundle-based progressive disclosure to offload large reference tables. Tightening explanatory prose and splitting canonical maps into reference files would lift the weaker dimensions.

Suggestions

Move the canonical file map and span/metric/event convention tables into a bundled reference file (e.g. references/conventions.md) and link to it from SKILL.md to improve progressive disclosure.

Trim explanatory prose blocks like the 'Why asymmetric?' callout and the dual-emit narrative to the essential rule, improving conciseness toward the lean anchor.

If the skill grows further, extract the procedure checklists (section 7) into a separate references/procedures.md referenced one level deep from the overview.

Dimension	Reasoning	Score
Conciseness	Largely lean and information-dense (tables, code, file maps) with no generic OTel preamble, but several prose blocks ('Why asymmetric?', dual-emit rationale) could be tightened; it is mostly efficient rather than maximally so.	2 / 3
Actionability	Provides executable TypeScript patterns (standard span pattern, trace propagation, content-capture gating), concrete file paths, named constants/enums, and runnable validation commands (npx tsc --noEmit, npm test -- --grep), matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	Multi-step procedures are numbered and sequenced ('When adding a new span/attribute', 'When changing the Copilot CLI bridge') with an explicit validation section and checkpoints before PR submission, matching the explicit-validation anchor.	3 / 3
Progressive Disclosure	No skill bundle exists (references/scripts/assets absent); the body is a single monolithic SKILL.md with large reference-style tables (canonical map, conventions) kept inline, and references point to external repo source files rather than skill-internal progressive disclosure, so structure is present but not optimally split.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, and complete, naming concrete capabilities and explicit use-conditions tied to a well-scoped niche. It is among the strongest reference examples and unlikely to trigger for the wrong skill.

Dimension	Reasoning	Score
Specificity	Names multiple concrete coverage areas — 'the four agent execution paths, the IOTelService abstraction, span/metric/event conventions, and the relationship between code and the user/developer monitoring docs' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what (instrumentation coverage areas) and when ('Use when adding/changing OTel spans, metrics, or events; instrumenting a new agent surface; ...'), matching the explicit-trigger anchor rather than the implied-when level.	3 / 3
Trigger Term Quality	Explicit, natural trigger phrasing ('adding/changing OTel spans, metrics, or events; instrumenting a new agent surface; touching the Copilot CLI bridge or Claude span emission; or updating ...agent_monitoring*.md') maps directly to what a developer would say, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	A clear niche — OTel instrumentation for the Copilot Chat extension's specific agent paths — with distinct triggers tied to named files and components, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 13 suspicious	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .github/skills/otel/SKILL.md
Commit: b87c504

Reviewed: 2 days 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.