CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-eventhub-py

Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.

60

Quality

71%

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

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, code-rich reference for the Azure Event Hubs SDK with good section organization. It is held back by missing validation/feedback loops in batch and checkpoint workflows and by reference files that are listed but not present in the bundle.

Suggestions

Add explicit validation checkpoints to the batch-send and checkpointed-receive workflows (e.g. verify batch was accepted, confirm checkpoint persisted, retry/recover on failure) to raise workflow clarity.

Create the referenced references/checkpointing.md, references/partitions.md, and scripts/setup_consumer.py files, or remove the 'Reference Files' table, so signaled references resolve to real bundle files.

Tighten redundancy by factoring shared client-construction setup into one introductory snippet referenced by later examples, and add the missing EventData import to the async example.

DimensionReasoningScore

Conciseness

Mostly lean code-first content that assumes Claude's competence, with minor redundancy from re-constructing the same clients across several self-contained examples.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready code across the common cases (send, receive, checkpoint, async, partitions, properties), with small gaps such as the async snippet using EventData without importing it.

4 / 5

Workflow Clarity

Content is organized as a feature cookbook rather than a sequenced workflow, and lacks explicit validation checkpoints; the batch-send loop has error handling but the receive/checkpoint path has no validation or recovery feedback loop.

3 / 5

Progressive Disclosure

Section structure is clear, but the 'Reference Files' table points to references/checkpointing.md, references/partitions.md, and scripts/setup_consumer.py that do not exist, and detailed patterns remain inline rather than split into the missing files.

3 / 5

Total

14

/

20

Passed

Description

78%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 solid, domain-specific description that names concrete capabilities and includes a 'Use for' trigger clause. It would reach the top level by adding explicit user-mention trigger phrasing.

DimensionReasoningScore

Specificity

Names the domain ('Azure Event Hubs SDK for Python streaming') and several concrete actions ('event ingestion, producers, consumers, and checkpointing'), with only minor coverage gaps such as error handling or schema registry.

4 / 5

Completeness

Provides a clear 'what' and a 'Use for high-throughput event ingestion...' 'when' clause, but the 'when' lacks explicit user-mention trigger phrases (e.g. 'when the user mentions Event Hubs'), capping it below 5.

4 / 5

Trigger Term Quality

Includes natural terms like 'Azure Event Hubs', 'streaming', 'event ingestion', 'producers', 'consumers', and 'checkpointing', but misses common user phrasings like 'event hub' or messaging-synonym variants.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (Azure Event Hubs Python SDK) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

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.