Appinsights Instrumentation

This one hooks up Azure App Insights telemetry to ASP.NET Core or Node.js webapps running in Azure. It'll check what you're running and prefer auto-instrumentation for ASP.NET Core apps in App Service when possible, otherwise it walks through manual setup. That means either adding App Insights to your existing Bicep templates or using Azure CLI to spin up the resource, then modifying your application code with the right SDK calls. The context gathering is solid, it actually asks about your hosting setup before doing anything, which matters because the instrumentation approach changes depending on whether you're in App Service, Container Apps, or elsewhere. Good for when you need observability but don't want to dig through Microsoft's documentation maze.

skills.sh installs: 9.5K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill appinsights-instrumentation --agent claude-code

Installs into .claude/skills of the current project.

Files

AppInsights instrumentation

This skill enables sending telemetry data of a webapp to Azure App Insights for better observability of the app's health.

When to use this skill

Use this skill when the user wants to enable telemetry for their webapp.

Prerequisites

The app in the workspace must be one of these kinds

An ASP.NET Core app hosted in Azure
A Node.js app hosted in Azure

Guidelines

Collect context information

Find out the (programming language, application framework, hosting) tuple of the application the user is trying to add telemetry support in. This determines how the application can be instrumented. Read the source code to make an educated guess. Confirm with the user on anything you don't know. You must always ask the user where the application is hosted (e.g. on a personal computer, in an Azure App Service as code, in an Azure App Service as container, in an Azure Container App, etc.).