What problem does it solve? Adding or changing OpenTelemetry telemetry in the Copilot Chat extension requires knowing four different agent execution paths, strict attribute naming conventions, and two monitoring docs that must stay in sync with the code. This Skill encodes those rules so instrumentation changes are consistent and complete. ## Core Features & Use Cases - Architecture map: Documents the four agent execution paths (foreground, Copilot CLI in-process, Copilot CLI terminal, Claude Code) and which OTel strategy each uses, plus a canonical file map of the otel platform layer. - Conventions and checklists: Enforces span/metric/event naming via genAiAttributes.ts constants, dual-emit rules for legacy copilot_chat.* attributes, content-capture gating, and step-by-step procedures for adding spans, metrics, events, or new agent surfaces. - Use Case: When adding a new execute_tool span attribute, the Skill directs you to define the constant in genAiAttributes.ts, truncate values with truncateForOTel, update EXPORTABLE_OPERATION_NAMES if needed, and document the attribute in agent_monitoring.md in the same PR. ## Quick Start Ask the AI to add a new OpenTelemetry span attribute for a tool execution in the Copilot Chat extension following the otel skill conventions.
