azure-servicebus-ts

Enterprise messaging with queues, topics, and subscriptions.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-servicebus-ts/SKILL.md

Quality

Content

72%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid API reference skill with excellent actionability—every section provides complete, executable TypeScript code. However, it reads more like a comprehensive API cookbook than a workflow-oriented skill, lacking explicit validation steps and feedback loops for operations that could fail silently. The progressive disclosure could be improved by actually splitting advanced patterns into referenced files rather than inlining everything.

Suggestions

Add explicit validation/verification steps after critical operations (e.g., confirm message was sent successfully, verify DLQ processing completed)

Move advanced sections (Sessions, Deferral, Scheduled Messages, Peek) into a referenced ADVANCED.md file to keep the main skill focused on core send/receive workflows

Remove the 'When to Use' boilerplate section at the end as it adds no value

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples and minimal unnecessary explanation. The 'Best Practices' section and 'When to Use' boilerplate at the end add some minor padding, but overall it respects Claude's intelligence and avoids over-explaining concepts.	4 / 5
Actionability	Fully executable, copy-paste ready TypeScript code covering all major Service Bus operations: sending, receiving, sessions, dead-letter handling, scheduling, deferral, and peeking. Each code block is complete and demonstrates concrete usage patterns.	5 / 5
Workflow Clarity	The content presents individual operations clearly but lacks an explicit multi-step workflow with validation checkpoints. For messaging operations that can lose messages (receiveAndDelete mode, dead-letter handling), there are no verification steps or feedback loops to confirm successful processing.	3 / 5
Progressive Disclosure	The skill references 'Queues vs Topics Patterns' and 'Error Handling and Reliability' documents but no bundle files are provided, making these references unverifiable. The content itself is somewhat long (~200 lines of code examples) with sections like Message Sessions, Deferral, and Peek that could be in separate reference files.	3 / 5
	Total	15 / 20 Passed

Description

36%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 too terse and lacks actionable detail. It names the domain and a few structural components but fails to describe concrete actions the skill performs and provides no guidance on when Claude should select it. Without specifying the technology, concrete operations, or trigger conditions, this description would be difficult to reliably match in a multi-skill environment.

Suggestions

Add a 'Use when...' clause with explicit trigger phrases, e.g., 'Use when the user asks about message queues, pub/sub messaging, topic subscriptions, or enterprise messaging patterns.'

List concrete actions the skill performs, such as 'Creates and manages message queues, publishes messages to topics, configures subscriptions, and monitors message delivery.'

Specify the technology or platform (e.g., Azure Service Bus, RabbitMQ, AWS SQS) to improve distinctiveness and reduce overlap with other messaging-related skills.

Dimension	Reasoning	Score
Specificity	Names the domain (enterprise messaging) and lists components (queues, topics, subscriptions) but does not describe any concrete actions like 'send messages', 'create queues', 'manage subscriptions', or 'consume from topics'.	2 / 5
Completeness	Provides a vague 'what' (enterprise messaging with queues, topics, subscriptions) but completely lacks any 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per guidelines, and the 'what' is also weak, bringing it to 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'queues', 'topics', and 'subscriptions', but misses natural user terms like specific technologies (e.g., RabbitMQ, Kafka, Azure Service Bus), actions ('send message', 'publish', 'subscribe'), or common phrases users would say.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to messaging systems, but 'enterprise messaging' is broad enough to overlap with multiple potential skills covering different messaging platforms, event-driven architectures, or pub/sub systems without clear differentiation.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-servicebus-ts/SKILL.md
Commit: 57c135b

Reviewed: 20 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.