BC Observatoryunofficial, made by waldo
community postAL Developmentcommunity - not Microsoftreviewed - checked by Opus

🧠 Agent Skills + MCPs: check your BC extension health in VS Code 🔍

Agent Skills are reusable instruction packages in VS Code that orchestrate external tools like YAMPI and BC Telemetry Buddy to analyze Business Central extension health across environments. A three-level loading model activates only relevant skills without penalizing context, enabling developers to check extension status, versions, deployments, and lifecycle events in production through a single chat message.

Open in Claude13993.md

post Gerardo Rentería Blog

Gerardo Renteria · 2026-03-07 · 1,410 words · about 6 min

"The description is critical because it's what Copilot reads at Level 1 to decide if the skill is relevant."
Show the post hereRead on Gerardo Rentería Blog

Key points

  • An Agent Skill is a folder under .github/skills/ with a required SKILL.md and optional reference files, loaded by Copilot through a three-level model only when relevant.
  • The description in the SKILL.md frontmatter is what Copilot reads first to decide relevance; vague use cases mean the skill will not activate.
  • The bc-extension-health skill reads app.json, calls YAMPI for active environments, installed versions and available updates, and uses BC Telemetry Buddy to run a KQL query over six lifecycle events (LC0010, LC0011, LC0016, LC0017, LC0022, LC0023).
  • Results from parallel tool calls are consolidated into two Markdown tables showing extension status per environment in the tenant.
  • The skill runs no code of its own; it only tells Copilot what tools to use, in what order, and how to present results.

Quotes

  • “The description is critical because it’s what Copilot reads at Level 1 to decide if the skill is relevant.” (Explains why proper skill documentation is essential for activation and why poorly described use cases will prevent skill loading)
  • “You can have many skills installed without penalizing the context, so Copilot only loads what is relevant for each requirement.” (Highlights the efficiency advantage of the three-level loading model for managing multiple skills in development environments)

Context

  • Features: Agent Skills, Extension lifecycle event analysis, Telemetry query integration, Multi-environment extension status, YAMPI integration, BC Telemetry Buddy integration

Source: Gerardo Renteria, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.