Skip to content

Instantly share code, notes, and snippets.

View saikoumudi's full-sized avatar

Sai Koumudi Kaluvakolanu saikoumudi

View GitHub Profile
@saikoumudi
saikoumudi / hooksconfiguration.md
Last active March 23, 2026 17:34
Hooks Configuration

Client-Specific hooks.json Formats

Why

We need visibility into which skills and tools are being used across Copilot CLI, VS Code, and Claude Code to understand adoption and prioritize development. Agent hooks let us do this — they are commands (shell scripts, PowerShell scripts, or any executable) that run automatically before or after an AI agent uses a tool, without modifying the agent itself.

The PostToolUse hook fires after every tool call, receiving the tool name, arguments, and session info via stdin as JSON — making it ideal for telemetry and observability. However, different AI coding clients use different formats for their hooks configuration. This document outlines those differences.

Hook Formats

@saikoumudi
saikoumudi / azure-skills-telemetry.md
Last active March 23, 2026 17:26
azure-skills telemetry

Azure MCP Server - Azure-Skills Plugin Telemetry Feature

Overview

We need visibility into which skills and tools are being used across Copilot CLI, VS Code, and Claude Code to understand adoption and prioritize development. This feature adds telemetry tracking for the azure-skills plugin execution. It enables collection of plugin usage metrics while maintaining privacy through PII removal and allowlisting.

Purpose

  • Track skill invocations, Azure MCP tool usage, and reference files accessed by the skills
  • Maintain user privacy by removing PII from file paths
  • Security-first approach with allowlist-based validation for both file references and skill names