CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-eventgrid-dotnet

Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is azure-eventgrid-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

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 thorough, highly actionable .NET Event Grid reference with executable code across publishing, pull delivery, parsing, and error handling. Its weakness is progressive disclosure: it is a monolithic single-file reference that would benefit from splitting catalog material into bundle files.

Suggestions

Move the System Events catalog, Key Types reference, and Related SDKs/Reference Links tables into separate files under references/ and link to them from SKILL.md to reduce the inlined bulk.

Remove or replace the vacuous 'When to Use' boilerplate with a concrete decision guide for when to choose Event Grid over Service Bus / Event Hubs.

Add an explicit validation/checkpoint note in the pull-delivery workflow (e.g., verify lock tokens before acknowledging) to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient code-reference content where examples earn their tokens; minor trimmable padding such as the boilerplate 'When to Use' section ('applicable to execute the workflow or actions described in the overview').

4 / 5

Actionability

Fully executable, copy-paste-ready C# examples covering the common cases (publish EventGridEvent/CloudEvent, batch, domain routing, pull-delivery receive/ack/release/reject, parsing, auth, error handling).

5 / 5

Workflow Clarity

The pull-delivery flow is clearly sequenced (receive -> process in try/catch -> acknowledge or release) with an implicit feedback loop, but there is no explicit validation checkpoint for the batch receive/acknowledge operation.

4 / 5

Progressive Disclosure

Well-organized section headers, but ~480 lines are entirely inlined in SKILL.md with no bundle files; catalog material (System Events, Key Types, Related SDKs) that belongs in separate reference files is inline, and only external URLs are linked.

3 / 5

Total

16

/

20

Passed

Description

82%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 clearly states both purpose and trigger conditions with concrete, natural keywords. Main weakness is specificity: only two concrete actions are named, leaving the breadth of Event Grid capabilities implied rather than stated.

Suggestions

Expand the action list beyond 'publishing and consuming events' to name more concrete capabilities (e.g., 'publish to topics and domains, pull-deliver from namespaces, parse CloudEvents and EventGridEvents').

Add the package name 'Azure.Messaging.EventGrid' and a couple more natural synonyms (webhooks, topics) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure Event Grid SDK for .NET') and 1-2 concrete actions ('publishing and consuming events'), but does not comprehensively cover capabilities like domains, namespaces, pull delivery, parsing, or system events.

3 / 5

Completeness

Explicitly answers both 'what' ('Client library for publishing and consuming events with Azure Event Grid') and 'when' ('Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say ('Azure Event Grid', 'event-driven architectures', 'pub/sub messaging', 'CloudEvents', 'EventGridEvents'), though a few natural synonyms (webhooks, topics, domains) and the package name are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Azure Event Grid on .NET) with distinct triggers (EventGridEvents, CloudEvents); minimal overlap risk with sibling Azure messaging SDKs.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.