<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telemetry on Top AI Skills</title><link>https://topaiskills.com/tags/telemetry/</link><description>Recent content in Telemetry on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/telemetry/index.xml" rel="self" type="application/rss+xml"/><item><title>appinsights-instrumentation: The App Insights Guidance Skill</title><link>https://topaiskills.com/skills/automation/appinsights-instrumentation/</link><pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/appinsights-instrumentation/</guid><description>&lt;p&gt;Microsoft&amp;rsquo;s &lt;code&gt;appinsights-instrumentation&lt;/code&gt; skill (v1.2.1, MIT) is the rare Azure skill that refuses to act. Its SKILL.md opens with a block-quoted rule: if the user wants to &lt;em&gt;add&lt;/em&gt; App Insights to an app, invoke &lt;code&gt;azure-prepare&lt;/code&gt; instead — this skill only provides reference material that the orchestrator consumes during its research phase. I read the full SKILL.md plus every reference (auto, ASP.NET Core, Node.js, Python, Container Apps, OpenTelemetry SDK pages, the Bicep example, the CLI script) and scraped skills.sh on 2026-09-18: 587,409 installs, rank 55, weekly curve [17111, 16383, 16130, 14987, 13426, 13612, 12124, 12809] — lockstep with the pack counter we keep seeing across microsoft/azure-skills.&lt;/p&gt;</description></item></channel></rss>