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.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-eventgrid-dotnet/SKILL.md

Quality

Content

75%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 strong, executable SDK reference with comprehensive, copy-paste-ready code examples and a well-sequenced pull-delivery workflow including ack/release feedback loops. The chief weakness is conciseness: overall length, repeated boilerplate, a filler 'When to Use' sentence, and inlined version-specific information that should live in a versioned/deprecated section.

Suggestions

Consolidate repeated EventGridPublisherClient construction into a single shared snippet and reference it, or drop the duplicate boilerplate from later examples to reduce length and redundancy.

Replace the filler 'When to Use' sentence with concrete invocation triggers, or remove it since the description already covers when-to-use.

Move time-sensitive information ('Current Version: 5.0.0 (stable)') into a dedicated, clearly labeled version/deprecated section so staleness does not penalize conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference content with minimal concept over-explanation, but it is long (~488 lines), repeats client-construction boilerplate across examples, includes the filler line 'This skill is applicable to execute the workflow or actions described in the overview', and inlines time-sensitive version info ('Current Version: 5.0.0') outside a deprecated/old-patterns section, which the guidelines say should penalize conciseness.	3 / 5
Actionability	Fully executable, copy-paste-ready C# covering the common cases: single/batch publishing of EventGridEvent and CloudEvent, domain routing, pull delivery send/receive/acknowledge/release/reject, Functions triggers, parsing, custom serialization, error handling, and failover.	5 / 5
Workflow Clarity	The pull-delivery section is a clearly sequenced process (receive -> try process -> ack success / release failures for retry) with an explicit validation/feedback loop, and the failover and error-handling sections add checkpoints; below 5 because most of the skill is a reference catalog of snippets rather than a fully checkpointed end-to-end workflow.	4 / 5
Progressive Disclosure	Well-organized single file with clear section headers and a clearly signaled 'Reference Links' table pointing one level out to external docs; no nested references and no bundle files to mismanage. Below 5 because some inline reference tables (Key Types, Event Schemas Comparison, Related SDKs) are sizable and could be split out, though they are appropriately placed for an SDK reference skill.	4 / 5
	Total	16 / 20 Passed

Description

70%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 concise, third-person description that clearly states what the skill covers and provides explicit 'Use for' trigger guidance with concrete, natural keywords. Its main limitation is that the 'when' clause lists scenarios rather than user-intent phrasings, and it names only two concrete actions.

Suggestions

Reframe the 'Use for' clause toward user intent, e.g. 'Use when the user asks to publish or consume events with Azure Event Grid, build event-driven or pub/sub architectures, or work with CloudEvents/EventGridEvents'.

Add one or two more concrete actions (e.g., 'parse incoming event payloads', 'deliver events via pull subscriptions') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure Event Grid SDK for .NET') and two concrete actions ('publishing and consuming events'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not at 4 because only two actions are listed.	3 / 5
Completeness	Has both a clear 'what' ('Client library for publishing and consuming events with Azure Event Grid') and an explicit 'Use for' trigger clause listing concrete scenarios; below 5 because the 'when' reads as capability/technology scenarios rather than explicit user-intent phrasings ('when the user asks to...').	4 / 5
Trigger Term Quality	Good natural keyword coverage with 'event-driven architectures', 'pub/sub messaging', 'CloudEvents', and 'EventGridEvents' that users would actually say; a few common variations (e.g., 'Event Grid topics/domains') are missing, keeping it just below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The 'Azure Event Grid' niche is clearly distinct with EventGridEvents/CloudEvents triggers, but there is minor overlap risk with closely related Azure messaging skills (Service Bus, Event Hubs), placing it at the 4 anchor rather than 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/azure-eventgrid-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 13 hours ago

Table of Contents

Discovery Implementation Validation

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.