CtrlK
BlogDocsLog inGet started
Tessl Logo

binding-event-subscribers

Turns event subscribers on and off dynamically using BindSubscription() and UnbindSubscription() with EventSubscriberInstance = Manual for conditional event handling. Use when disabling subscribers during batch jobs, enabling page-scoped validation, implementing feature toggles via setup, turning off event handlers for performance, or controlling dynamic event execution at runtime.

68

Quality

83%

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

78%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 concise, actionable skill body with a clearly sequenced procedure and explicit validation gates. The main gap is progressive disclosure: a provided bundle file (binding-patterns.md) is not linked from the overview, and validation gates lack an explicit retry/recovery loop.

Suggestions

Add a pointer to references/binding-patterns.md (e.g., a '## More patterns' line) so the bundled resource is discoverable from the overview.

Pair each Validation Gate with a brief recovery action (what to fix/re-check if subscribers still fire or fail to bind) to create a validate→fix→retry loop.

Note in the procedure that placeholders like <ID>, <PREFIX>, and <SourceTable> must be resolved to concrete object IDs and names before the code compiles.

DimensionReasoningScore

Conciseness

Lean and efficient: code-template blocks, terse bullet notes, and no padding or explanation of basic AL/event concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete, syntactically valid AL with real method calls and worked patterns (Conditional via Setup, Batch Job Optimization), but template placeholders like <ID>, <PREFIX>, and <SourceTable> require filling before the code is directly executable.

4 / 5

Workflow Clarity

A clear two-step procedure is paired with an explicit 'Validation Gates' section (After Step 1, After Step 2, Final) giving real checkpoints, but no error-recovery feedback loop describes what to do when a gate fails.

4 / 5

Progressive Disclosure

The body is well-sectioned and links out to authoritative MS Learn docs, but the bundled references/binding-patterns.md file is never referenced or signaled from the body, leaving a relevant deeper resource undiscoverable.

3 / 5

Total

16

/

20

Passed

Description

87%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, third-person description that concretely names the methods and property involved and supplies a rich, explicit 'Use when...' clause covering five realistic scenarios. Minor room remains in action breadth and lay-term synonyms, but distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Names the domain and concrete method calls ("BindSubscription() and UnbindSubscription() with EventSubscriberInstance = Manual") but the underlying capability is essentially one toggle action rather than a broad set of distinct actions, so it stops just short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ("Turns event subscribers on and off dynamically using BindSubscription() and UnbindSubscription()...with EventSubscriberInstance = Manual") and when ("Use when disabling subscribers during batch jobs, enabling page-scoped validation, implementing feature toggles via setup...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural-phrase coverage ("disabling subscribers during batch jobs", "feature toggles", "turning off event handlers for performance") with synonym variation between "subscribers" and "event handlers", though the terms are domain-specific and a few lay synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (AL/Business Central manual event subscriber binding) with distinct, specific triggers and minimal realistic overlap with other skills.

5 / 5

Total

18

/

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.