Name: azure-servicebus-dotnet
Rating: 51.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-servicebus-dotnet

Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions.

Quality

56%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-servicebus-dotnet/SKILL.md

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

Quality

Content

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

A comprehensive, highly actionable Service Bus reference with executable code across all common workflows, but it inlines everything into one file and omits validation checkpoints around destructive and batch operations. Token efficiency is decent though slightly weighed down by a hardcoded version number.

Suggestions

Add verification/validation steps before destructive operations (e.g., confirm queue name before DeleteQueueAsync) and after batch sends (verify batch was accepted).

Move detailed API reference or administration examples into separate reference files and link to them from SKILL.md to improve progressive disclosure.

Remove the hardcoded 'v7.20.1' version number or relocate it to a versioned/deprecated section, and trim redundant code comments and the repeated opening summary.

Dimension	Reasoning	Score
Conciseness	Mostly lean code and tables, but it inlines a time-sensitive version number ('v7.20.1') outside a deprecated section and repeats the summary line plus a few redundant comments ('// Message added successfully').	3 / 5
Actionability	Nine workflows of concrete, executable C# using real API calls (CreateSender, SendMessageAsync, ReceiveMessageAsync, etc.), with only a minor gap being the unimplemented '// Retry with backoff' placeholder in error handling.	4 / 5
Workflow Clarity	Workflows are individually sequenced, but destructive operations (DeleteQueueAsync) and batch operations (CreateMessageBatchAsync/SendMessagesAsync) lack validation or verification checkpoints, which caps the score at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized with clear section headers, but a large volume of API reference content (9 workflows, key types, administration CRUD) is inlined in a single ~330-line file with no internal bundle references to split it out.	3 / 5
	Total	13 / 20 Passed

Description

56%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 clearly names a distinct product and domain with good trigger keywords, but lacks a 'Use when' trigger clause and concrete action verbs. It is specific enough to avoid conflicts but incomplete on usage guidance.

Suggestions

Add a 'Use when...' clause listing concrete triggers (e.g., 'Use when the user mentions Azure Service Bus, .NET messaging, queues, or publish/subscribe patterns').

Replace entity nouns with action verbs to raise specificity (e.g., 'Send, receive, and process messages across queues, topics, and sessions').

Include common synonyms like 'publish/subscribe', 'pub/sub', or 'message broker' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ('Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions.') but lists entity nouns rather than concrete action verbs, so actions are minimal or generic.	2 / 5
Completeness	Clearly states what the SDK is but provides no 'Use when...' trigger clause, so the 'when' is missing — the rubric caps completeness at 3 in that case.	3 / 5
Trigger Term Quality	Includes the natural product name 'Azure Service Bus' and '.NET' plus messaging terms (queues, topics, subscriptions, sessions) a developer would say, with only minor synonyms like 'publish/subscribe' or 'message broker' missing.	4 / 5
Distinctiveness Conflict Risk	The named product 'Azure Service Bus' is a clear niche with minimal conflict risk, aside from minor overlap with sibling Azure messaging SDKs such as Event Hubs and Event Grid.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-servicebus-dotnet/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.