How do I install the Appinsights Instrumentation skill?

Run npx skillmds@latest add tomevault-io/appinsights-instrumentation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Appinsights Instrumentation safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Appinsights Instrumentation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Appinsights Instrumentation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Appinsights Instrumentation?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Appinsights Instrumentation by tomevault-io

Name: Appinsights Instrumentation
Author: tomevault-io

File contents

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.).

Prefer auto-instrument if possible

If the app is a C# ASP.NET Core app hosted in Azure App Service, use AUTO guide to help user auto-instrument the app.

Manually instrument

Manually instrument the app by creating the AppInsights resource and update the app's code.

Create AppInsights resource

Use one of the following options that fits the environment.

Add AppInsights to existing Bicep template. See examples/appinsights.bicep for what to add. This is the best option if there are existing Bicep template files in the workspace.
Use Azure CLI. See scripts/appinsights.ps1 for what Azure CLI command to execute to create the App Insights resource.

No matter which option you choose, recommend the user to create the App Insights resource in a meaningful resource group that makes managing resources easier. A good candidate will be the same resource group that contains the resources for the hosted app in Azure.

Modify application code

If the app is an ASP.NET Core app, see ASPNETCORE guide for how to modify the C# code.
If the app is a Node.js app, see NODEJS guide for how to modify the JavaScript/TypeScript code.
If the app is a Python app, see PYTHON guide for how to modify the Python code.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: appinsights-instrumentationdescription: Instrument a webapp to send useful telemetry data to Azure App Insights Use when this capability is needed.---# AppInsights instrumentationThis skill enables sending telemetry data of a webapp to Azure App Insights for better observability of the app's health.## When to use this skillUse this skill when the user wants to enable telemetry for their webapp.## PrerequisitesThe 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 informationFind 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.). ### Prefer auto-instrument if possibleIf the app is a C# ASP.NET Core app hosted in Azure App Service, use [AUTO guide](references/AUTO.md) to help user auto-instrument the app.### Manually instrumentManually instrument the app by creating the AppInsights resource and update the app's code. #### Create AppInsights resourceUse one of the following options that fits the environment.- Add AppInsights to existing Bicep template. See [examples/appinsights.bicep](examples/appinsights.bicep) for what to add. This is the best option if there are existing Bicep template files in the workspace.- Use Azure CLI. See [scripts/appinsights.ps1](scripts/appinsights.ps1) for what Azure CLI command to execute to create the App Insights resource.No matter which option you choose, recommend the user to create the App Insights resource in a meaningful resource group that makes managing resources easier. A good candidate will be the same resource group that contains the resources for the hosted app in Azure.#### Modify application code- If the app is an ASP.NET Core app, see [ASPNETCORE guide](references/ASPNETCORE.md) for how to modify the C# code.- If the app is a Node.js app, see [NODEJS guide](references/NODEJS.md) for how to modify the JavaScript/TypeScript code.- If the app is a Python app, see [PYTHON guide](references/PYTHON.md) for how to modify the Python code.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/github) — claim your Tome and manage your conversions.

Frequently asked questions

Appinsights Instrumentation