agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/query-app-insights/SKILL.md

query-app-insights

Skill1k starsChanged 27 days agoBSD-3-ClauseView on GitHub

Query Azure Application Insights telemetry data for command usage, extension activity, and performance metrics

  • Reads credentials

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Validate credentials: - check env vars exist

    line 19
  2. Distinctive:

    Find executor name: - if checking a command, find its executor name (see references)

    line 22
  3. Distinctive:

    Build KQL query: - use executor names, not command IDs

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Query App Insights

Query Azure Application Insights telemetry to answer questions about command usage, extension activity, performance.

Prerequisites

  • APP_INSIGHTS_API_KEY env var
  • APP_INSIGHTS_CLIENT_ID env var

Workflow

  1. Validate credentials - check env vars exist
  2. Test API - node scripts/queryAppInsights.mts "customEvents | take 1"
  3. Interpret question - identify commands, extensions, time ranges, metrics
  4. Find executor name - if checking a command, find its executor name (see references)
  5. Build KQL query - use executor names, not command IDs
  6. Execute - node scripts/queryAppInsights.mts "<kql-query>"
  7. Answer - interpret results, format clearly

Key Points

  • Telemetry uses executor names, not command IDs
  • Event pattern: ends with /commandExecution (Legacy/v2) or stored in dependencies table (OTEL/v3)
  • Tables: customEvents (Legacy), dependencies (OTEL Spans), requests (Root Spans)
  • OTEL Properties: name (Span name), cloud_RoleName (Extension name), operation_Id (Trace ID), operation_ParentId (Parent Span ID)
  • OTEL Root Filter: where operation_ParentId == operation_Id (Finds top-level spans in v3)
  • Measurements: customMeasurements.executionTime (ms for Legacy) or duration (ms for OTEL)

References

  • references/command-id-vs-executor.md - Finding executor names, shared executors, commands without telemetry
  • references/query-patterns.md - Common KQL patterns
  • references/script.md - Script implementation details

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free