CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-eventhub-ts

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

48

Quality

53%

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-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 content is a well-structured, actionable Azure Event Hubs TypeScript reference with strong code examples, but it functions as an inlined catalog rather than a sequenced workflow with validation checkpoints, and it does not use progressive disclosure to offload reference material.

Suggestions

Add a short sequenced quickstart (install -> configure env vars -> send -> receive with checkpoint) with an explicit verification step such as confirming received events or checking partition lag.

Replace the generic "When to Use" closing line with concrete trigger guidance consistent with the description.

Move the Key Types and Event Properties API reference into a separate references file and link to it, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is code-heavy with minimal prose and does not re-explain concepts Claude already knows; the main excess is duplicated producer/consumer setup between Authentication and Core Workflow, plus the vapid closing "When to Use" line.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready TypeScript covering send, partition, receive, checkpointing, and error handling; minor gaps come from snippets using undefined placeholders (e.g. bare `namespace`, `storageAccount`, `containerName`) rather than the env vars defined earlier.

4 / 5

Workflow Clarity

The skill is organized as a feature catalog rather than a sequenced workflow, and although it involves batch send/checkpoint operations there is no explicit validate-then-retry feedback loop beyond the Error Handling try/catch; the rubric caps workflow clarity at 3 for batch operations lacking validation.

3 / 5

Progressive Disclosure

All ~270 lines live in a single SKILL.md with no bundle files or external references; section structure is reasonable, but reference-style content (Key Types, Event Properties, full option tables) that could be split into a separate file is inlined.

3 / 5

Total

14

/

20

Passed

Description

41%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 terse, domain-level tagline that conveys the general area but lacks concrete capabilities, explicit trigger guidance, and the product-specific identity needed to distinguish it from rival streaming skills.

Suggestions

Add concrete actions, e.g. "Send, receive, and checkpoint events on Azure Event Hubs from TypeScript."

Append an explicit trigger clause: "Use when working with Azure Event Hubs, event streaming, telemetry ingestion, or @azure/event-hubs in TypeScript."

Include the product name and language so the skill is distinguishable from Kafka/Kinesis/Pub-Sub skills.

DimensionReasoningScore

Specificity

The description "High-throughput event streaming and real-time data ingestion" names the streaming domain but only offers generic action verbs ("streaming", "ingestion") rather than concrete capabilities like sending, receiving, checkpointing, or partitioning events.

2 / 5

Completeness

It states a clear "what" (event streaming / data ingestion) but provides no "when" / "Use when..." trigger guidance at all, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"event streaming" and "data ingestion" are reasonably natural terms, but the description omits the product name "Azure Event Hubs", the language (TypeScript), and common synonyms (telemetry, event hubs, pub/sub) that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Without naming Azure Event Hubs, the description is provider-agnostic and could plausibly trigger for Kafka, Kinesis, Pub/Sub, or other streaming skills, creating high overlap risk.

2 / 5

Total

10

/

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.