Name: azure-servicebus-py
Rating: 61.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-servicebus-py

Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.

Quality

73%

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-py/SKILL.md

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

Quality

Content

72%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 well-organized, highly actionable reference with copy-paste-ready code for the core Service Bus operations. Its weaknesses are missing validation checkpoints for batch/settlement operations and reference files that are listed but not actually present in the bundle.

Suggestions

Add explicit validation/verification steps around batch sending and message settlement (e.g. confirm batch size, verify complete/abandon succeeded) to lift workflow clarity above the batch-operation cap.

Create the referenced bundle files (references/patterns.md, references/dead-letter.md, scripts/setup_servicebus.py) or remove the Reference Files table so navigation is not broken.

Move the bulk of the inline API examples (sessions, scheduled messages, dead-letter queue) into the reference files and keep SKILL.md as a tighter overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code with section headers and minimal prose, assuming Claude's competence; only minor inline comments and the brief intro line could be trimmed, fitting 'efficient; minor instances of over-explanation' rather than the fully-lean anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready async and sync examples cover send, receive, batch, sessions, scheduled messages, and dead-lettering across the common cases, matching the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	Content is organized as topical reference sections with an error-handling settlement example, but there are no explicit validation/verification checkpoints, and batch operations (message batching, dead-lettering) appear without a validate→fix→retry loop, triggering the cap at 3.	3 / 5
Progressive Disclosure	Section structure is clear and a Reference Files table signals references, but the referenced files (references/patterns.md, references/dead-letter.md, scripts/setup_servicebus.py) do not exist in the bundle, and bulk API reference is inlined rather than split out, fitting 'some structure but could be better organized'.	3 / 5
	Total	15 / 20 Passed

Description

73%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 concise, domain-specific description that clearly identifies the Azure Service Bus Python SDK and provides an explicit 'Use for' trigger clause. Its main weakness is generic action language ('messaging', 'enterprise messaging patterns') instead of concrete verbs.

Suggestions

Replace generic action terms with concrete verbs, e.g. 'Send, receive, batch, and settle messages on Azure Service Bus queues and topics'.

Add natural synonyms/variations users might say, such as 'pub/sub' or 'service bus messaging', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure Service Bus SDK for Python messaging') and concrete entities ('queues, topics, subscriptions'), but describes no concrete verbs — actions are covered only by the generic term 'messaging', matching the 'names domain and 1-2 concrete actions' anchor loosely rather than the comprehensive multi-action anchor.	3 / 5
Completeness	Both 'what' (Azure Service Bus SDK for Python messaging) and 'when' ('Use for queues, topics, subscriptions, and enterprise messaging patterns') are present with an explicit trigger clause, but the 'when' is slightly generic ('enterprise messaging patterns'), placing it just below the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	Natural terms a user would say ('Azure Service Bus', 'Python messaging', 'queues', 'topics', 'subscriptions') are present and domain-appropriate, but synonyms and variations are limited, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Names a specific Azure service and SDK with distinct, product-specific triggers, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-servicebus-py/SKILL.md
Commit: 57c135b

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