CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-eventgrid-py

Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.

59

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-eventgrid-py/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is a lean, mostly executable reference with strong code coverage of publishing patterns. Its main weaknesses are the absence of a real workflow with validation checkpoints for batch operations and no progressive disclosure to supporting files.

Suggestions

Add a short receive/consume example and an error-handling/retry pattern to round out actionability for the common cases.

Provide an explicit publish workflow with a validation checkpoint (e.g. confirm delivery/ack response before considering an event sent) to lift workflow clarity above 3 for batch publishing.

Split detailed property tables and advanced examples into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is code-focused and largely assumes Claude's competence, with only minor fluff such as the vague 'When to Use' line ('applicable to execute the workflow or actions described in the overview').

4 / 5

Actionability

Most sections provide copy-paste-ready executable code for publishing CloudEvents/EventGridEvents, async, and namespace topics; minor gaps remain (no receive/consume examples, no error-handling).

4 / 5

Workflow Clarity

The body is reference-style with no sequenced multi-step workflow and no validation checkpoints for batch publishing; 'Best Practices' lists tips but lacks a validate->fix->retry loop.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections, but at ~170 lines everything is inlined in SKILL.md with no one-level-deep references to split out detailed API material.

4 / 5

Total

15

/

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.

The description is concrete and distinguishable, covering what the skill does and when to use it with a 'Use for' clause. It could be tightened by replacing the abstract 'event-driven architectures' with more specific actions and adding natural trigger synonyms.

Suggestions

Replace the abstract 'event-driven architectures' with concrete actions like 'subscribing to events' or 'routing events between services' to lift specificity.

Add natural trigger synonyms such as 'Azure', 'event grid topics', or 'pub/sub' to broaden trigger-term coverage.

Make the 'when' clause more explicit, e.g. 'Use when publishing or handling Azure Event Grid events, CloudEvents, or pub/sub workflows.'

DimensionReasoningScore

Specificity

Names the domain ('Azure Event Grid SDK for Python') and concrete actions ('publishing events, handling CloudEvents'), but 'event-driven architectures' is abstract and coverage is not comprehensive.

3 / 5

Completeness

Both 'what' (the SDK and its actions) and 'when' ('Use for ...') are present; the 'Use for' clause is an explicit trigger, though the when could be more specific.

4 / 5

Trigger Term Quality

Natural terms like 'Azure Event Grid', 'publishing events', and 'CloudEvents' appear, but common variations/synonyms (e.g. 'Azure', 'event grid topics', 'pub/sub') are partially missing.

4 / 5

Distinctiveness Conflict Risk

The Azure Event Grid niche is distinct and unlikely to collide with unrelated skills, with only minor overlap risk against broader Azure/messaging skills.

4 / 5

Total

15

/

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.