instrument-observability

Instrument A365 Observability

Trigger phrases — any of these will activate this skill automatically:

• "instrument observability for this agent"
• "add a365 observability to this agent"
• "add observability to this agent"
• "set up tracing for this agent"
• "make this agent visible in microsoft defender"
• "enable agent 365 telemetry"
• "wire up opentelemetry for this agent"
• "add observability to this .net agent"
• "add observability to this node.js agent"
• "add a365 observability to this python agent"

---

Overview

This skill instruments Microsoft Agent 365 observability into an existing agent codebase without disrupting the agent's core logic. It:

1. Detects the agent type (.NET AgentFramework, Node.js, or Python)
2. Installs the correct A365 observability packages (core + hosting + optional extensions)
3. Wires observability in the entry point
4. Adds BaggageBuilder context or BaggageMiddleware to message handlers
5. Implements the agentic token resolver with caching
6. Adds manual instrumentation scopes (InvokeAgentScope, InferenceScope, ExecuteToolScope — required for store publishing)
7. Updates configuration files with observability settings
8. Validates the build passes

Store publishing requirement: The Agent 365 store validation requires InvokeAgentScope, InferenceScope, and ExecuteToolScope to be implemented. This skill wires them.

All changes are additive and idempotent — rerunning the skill is safe.

---

Phase 0: Load Detection Cache and Validate

Task-list display (applies throughout this skill). This skill creates tasks inline via **TaskCreate** — "..." markers at the start of each phase, and marks them complete at phase end. The user must see this progress visibly. Each TaskCreate line corresponds to one checklist item; exactly one item in_progress at a time.

• Claude Code: TaskCreate is in allowed-tools — calling it renders a native checklist UI; subsequent TaskUpdate calls flip statuses.
• VS Code Copilot Chat / GitHub Copilot CLI: allowed-tools is ignored — before Phase 0.1, scan this SKILL.md for all **TaskCreate** — "..." lines and emit a markdown checklist in chat upfront (- [ ] Load detection cache…, - [ ] Determine agent kind…, etc.); flip items to - [x] as each phase completes.