CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-eventhub-ts

High-throughput event streaming and real-time data ingestion.

50

Quality

55%

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-claude/skills/azure-eventhub-ts/SKILL.md

The canonical home for this skill is azure-eventhub-ts 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.

The body is a strong, code-heavy Azure Event Hubs reference with executable examples across the common workflows, though it is somewhat verbose through duplicated client setup and inlines API-reference material that belongs in separate files. It lacks an explicit validation/feedback loop for its batch streaming operations.

Suggestions

Move the Key Types, Event Properties, and Batch Processing Options sections into a references file and link to them from SKILL.md.

Factor the producer/consumer client construction into a single setup block instead of repeating it in Authentication, Send, and Receive.

Add an explicit receive workflow sequence with a validate->checkpoint->on-error-retry checkpoint loop rather than only inline code.

DimensionReasoningScore

Conciseness

The body is code-first and lean with almost no concept explanation, fitting 'Efficient; minor instances of over-explanation that could be trimmed'; it does not reach 5 because client construction is repeated across the Authentication, Send, and Receive sections and a standalone 'Key Types' import listing could be folded away.

4 / 5

Actionability

It provides extensive executable TypeScript covering send, receive, checkpointing, partitioning, and error handling ('Mostly executable guidance; concrete code... with minor gaps'); it falls short of 5 because snippets inconsistently reference `namespace`/`fullyQualifiedNamespace`, so individual blocks are not fully copy-paste self-contained.

4 / 5

Workflow Clarity

Streaming/consuming is a batch operation and, while processError and checkpoint-on-failure notes exist, there is no explicit validate->fix->retry checkpoint sequence, so per the batch-operations cap workflow clarity stays at 3.

3 / 5

Progressive Disclosure

Headers are well organized, but ~265 lines of inline API reference (Key Types, Event Properties, Batch Processing Options) live in SKILL.md with zero reference files, matching 'Some structure but... content that should be separate is inline'; not a 4 because no content is split into separate files.

3 / 5

Total

14

/

20

Passed

Description

45%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 a concise, third-person domain statement but is generic: it never names Azure Event Hubs, lists no concrete actions, and lacks any 'Use when...' trigger guidance. It is recognizable as streaming/ingestion yet indistinguishable from competing stream platforms.

Suggestions

Name the platform explicitly, e.g. 'Send and receive events from Azure Event Hubs using the TypeScript SDK'.

Add concrete actions such as producing batches, consuming with checkpointing, and partition targeting.

Append a 'Use when...' trigger clause referencing Azure Event Hubs, event streaming, or real-time ingestion.

DimensionReasoningScore

Specificity

The description names the domain via characteristic phrases like 'High-throughput event streaming and real-time data ingestion' but states no concrete actions (e.g. send/receive/checkpoint events), matching 'Names the domain but actions are minimal or generic'; it does not reach 3 because it lists no discrete actions.

2 / 5

Completeness

It offers a recognizable 'what' but contains no 'Use when...' trigger clause, so per the judging guideline a missing explicit trigger caps completeness at 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

'event streaming' and 'real-time data ingestion' are relevant natural terms, but the description omits the platform name 'Azure Event Hubs' and common synonyms, fitting 'Some relevant keywords but missing common variations or synonyms'; not a 4 because keyword coverage is incomplete.

3 / 5

Distinctiveness Conflict Risk

'event streaming and real-time data ingestion' is a recognizable niche but, without naming Azure Event Hubs, could overlap with Kafka/Kinesis-style skills, matching 'Somewhat specific but could still overlap'; not a 4 because the platform is unnamed.

3 / 5

Total

11

/

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.