azure-messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/azure-messaging/SKILL.md

Quality

Content

57%

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

The skill is well-organized and concise, with good use of tables and a clear scope definition. However, it lacks concrete actionable content—no specific error-to-resolution mappings, no example KQL queries, no sample code—making it more of a high-level process outline than a practical troubleshooting guide. The references to external troubleshooting guides that don't exist in the bundle significantly undermine its utility.

Suggestions

Add concrete examples: include 2-3 common error messages with specific KQL queries to diagnose them and exact remediation steps (e.g., message lock expired → increase lock duration, add lock renewal code snippet)

Provide the referenced 'troubleshooting/messaging/' bundle files or inline the key error-to-fix mappings for the most common issues listed in the 'When to Use' section

Add feedback loops to the diagnosis workflow: e.g., 'After applying fix, verify with resource health check and re-run the KQL query to confirm errors have stopped'

Include at least one executable KQL query example for diagnostic log analysis via mcp_azure_mcp_monitor logs_query

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured with tables for quick reference. It avoids explaining what Event Hubs or Service Bus are, assumes Claude's competence, and every section serves a clear purpose without padding.	3 / 3
Actionability	The skill provides a clear diagnosis workflow and lists specific MCP tools with their purposes, but lacks concrete executable examples—no KQL queries, no sample connection string validation commands, no specific error-to-fix mappings. The troubleshooting guides are referenced but not provided in the bundle, and the guidance remains at a procedural rather than executable level.	2 / 3
Workflow Clarity	The 6-step diagnosis workflow provides a reasonable sequence, but lacks explicit validation checkpoints and feedback loops. There's no 'if this fails, do that' branching, no verification that a fix worked, and no error recovery guidance—important for troubleshooting workflows where iterative diagnosis is the norm.	2 / 3
Progressive Disclosure	The skill references 'troubleshooting/messaging/' under an azure-diagnostics skill but no bundle files are provided, making this a dead reference. There are no linked files for the language-specific troubleshooting guides mentioned in step 3, and the 'Troubleshooting Guides' section is essentially empty—pointing to content that doesn't exist in the bundle.	1 / 3
	Total	8 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and clear distinctiveness. The explicit WHEN clause with extensive natural keywords ensures Claude can reliably select this skill for relevant queries. The main weakness is that the 'what' portion could be more specific about concrete actions rather than listing broad categories of issues.

Suggestions

Enhance specificity by listing concrete actions like 'diagnose AMQP connection errors, resolve checkpoint store issues, configure dead letter queues, debug event processor host failures' instead of broad categories like 'connection failures, authentication errors'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Azure Messaging SDKs for Event Hubs and Service Bus) and lists categories of issues (connection failures, authentication errors, message processing issues, SDK configuration problems), but doesn't list specific concrete actions like 'diagnose AMQP link detach errors' or 'configure checkpoint stores'. The actions are more categorical than concrete.	2 / 3
Completeness	Clearly answers both 'what' (troubleshoot and resolve issues with Azure Messaging SDKs covering connection failures, authentication errors, etc.) and 'when' (explicit WHEN clause with extensive trigger terms). The WHEN clause serves as an explicit trigger guidance section.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say, including specific error conditions ('message lock lost', 'message lock expired', 'send timeout', 'receiver disconnected'), SDK-language combinations ('eventhub python', 'servicebus java', 'servicebus dotnet'), and common problem descriptions ('event hub not receiving messages', 'service bus dead letter', 'slow reconnect', 'duplicate events'). These closely match real user queries.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Azure Messaging SDKs specifically for Event Hubs and Service Bus. The trigger terms are very specific to this domain (AMQP errors, event processor host, checkpoint, dead letter) and unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: microsoft/github-copilot-for-azure
Commit: d4563f6

Reviewed: 3 days 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.