Guidance and reference material for instrumenting webapps with Azure Application Insights.
Works with
Covers SDK setup, telemetry patterns, and configuration for ASP.NET Core and Node.js applications hosted in Azure
Distinguishes between this skill (reference and guidance) and azure-prepare (actual implementation); invoke azure-prepare when the user wants to add instrumentation to their project
Provides auto-instrumentation guidance for C# ASP.NET Core apps in Azure App Service, plus manual ins
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionappinsights-instrumentationExecute the skills CLI command in your project's root directory to begin installation:
Fetches appinsights-instrumentation from microsoft/azure-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate appinsights-instrumentation. Access via /appinsights-instrumentation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
582
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
582
stars
This skill provides guidance and reference material for instrumenting webapps with Azure Application Insights.
⛔ ADDING COMPONENTS?
If the user wants to add App Insights to their app, invoke azure-prepare instead. This skill provides reference material—azure-prepare orchestrates the actual changes.
The app in the workspace must be one of these kinds
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.).
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 the app by creating the AppInsights resource and update the app's code.
Use one of the following options that fits the environment.
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.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
appinsights-instrumentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
appinsights-instrumentation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: appinsights-instrumentation is focused, and the summary matches what you get after install.
Useful defaults in appinsights-instrumentation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend appinsights-instrumentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
appinsights-instrumentation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added appinsights-instrumentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: appinsights-instrumentation is the kind of skill you can hand to a new teammate without a long onboarding doc.
appinsights-instrumentation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
appinsights-instrumentation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 41