CtrlK
BlogDocsLog inGet started
Tessl Logo

implementing-telemetry

Logs custom events to Application Insights using Feature Telemetry or Session.LogMessage, tracks feature adoption with LogUptake, and queries telemetry data with KQL. Use when instrumenting BC extensions, debugging production issues, monitoring API integrations, or tracking feature usage.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with explicit validation gates and a clean reference split. The main improvement is making code examples more copy-paste-ready by reducing templated placeholders.

Suggestions

Reduce <PREFIX>/<Record>/<FieldName> placeholders in code examples toward literal, runnable snippets, or provide one fully concrete worked example alongside the templates.

Tighten the 'Important Notes' prose into the existing tables to trim a few explanatory tokens.

Consider noting which EventId range examples (APP-0001…) map to the <PREFIX> placeholder so users can copy a concrete starting registry.

DimensionReasoningScore

Conciseness

Mostly lean with tables and code dominating over prose, and the 'Key Concept' EventId-prefix note earns its place; a few explanatory notes and templated placeholder code could be trimmed slightly, keeping it just below the top anchor.

4 / 5

Actionability

Provides concrete AL code, an app.json snippet, a KQL query, and EventId registry tables, but the code uses <PREFIX>/<Record>/<FieldName> placeholders rather than literal copy-paste-ready values, leaving minor gaps.

4 / 5

Workflow Clarity

Seven numbered Steps plus an explicit 'Validation Gates' section with three checkpoints and a Troubleshooting feedback loop (Fix → Re-deploy → Wait 5 min → Re-check), matching the top anchor for sequenced validation.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with two real, clearly signaled one-level-deep references (references/kql-queries.md and references/job-queue-telemetry.md, both verified present), giving clear navigation.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely names both capabilities and trigger conditions with little fluff. Adding synonym variants (e.g., 'Business Central', 'App Insights') would round out trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named APIs — 'Logs custom events… using Feature Telemetry or Session.LogMessage', 'tracks feature adoption with LogUptake', 'queries telemetry data with KQL' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers 'what' (three named actions) and 'when' via a concrete 'Use when…' clause with multiple trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural triggers ('instrumenting BC extensions', 'debugging production issues', 'monitoring API integrations', 'tracking feature usage') but 'BC extensions' is jargon-shorthand and synonym/file-extension variants are absent, so just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (AL/BC telemetry instrumentation) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
emgreppi/Business-Central-AI-Skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.