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

86%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A concise, well-organized diagnostic skill body that routes effectively to named MCP tools and external guides. Its weakness is that remediation guidance and validation checkpoints are largely deferred rather than provided inline.

Suggestions

Add one or two concrete remediation snippets inline (e.g., a sample KQL logs_query for a common error, or the typical fix for 'message lock expired') so the skill is actionable without leaving to the azure-diagnostics skill.

Insert validation/feedback checkpoints into the diagnosis workflow, such as 'If resource health is degraded, check region/failover status' and 'Re-verify after applying a fix' to create a validate-fix-retry loop.

Include at least one worked example mapping a specific error string to its remediation, rather than relying solely on 'Match against language-specific troubleshooting guide'.

Dimension	Reasoning	Score
Conciseness	The ~45-line body is lean and well-structured with tables and bullets, explaining no concepts Claude already knows; every section earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Names concrete MCP tools and operations ('mcp_azure_mcp_resourcehealth to verify the namespace is healthy', 'mcp_azure_mcp_documentation to search Microsoft Learn') but actual remediation is deferred to the azure-diagnostics skill and external docs rather than given inline, leaving key fix details missing.	2 / 3
Workflow Clarity	The diagnosis workflow is a clear 6-step numbered sequence, but it lacks explicit validation checkpoints or feedback loops for error recovery (no 'verify the fix' or 'if health check fails, do X' steps), matching the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	A short, well-organized overview (clear sections: Quick Reference, When to Use, MCP Tools, Diagnosis Workflow) that points one level deep to detailed guides in the azure-diagnostics skill under troubleshooting/messaging/, appropriately splitting overview from detail.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 strong, third-person description that concisely states what the skill does and provides a rich, natural set of WHEN triggers. It is specific, complete, and clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	Names concrete capabilities ('Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus') and enumerates specific issue categories ('connection failures, authentication errors, message processing issues, and SDK configuration problems'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what ('Troubleshoot and resolve issues with Azure Messaging SDKs...') and when (explicit 'WHEN:' trigger clause), matching the 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	The WHEN clause provides extensive natural user terms ('message lock lost', 'event hub not receiving messages', 'service bus dead letter', 'eventhub python', 'AMQP error') that a user would actually say, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Azure Event Hubs and Service Bus SDKs) with highly specific triggers ('event processor host issue', 'link detach', 'offset reset') unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/azure-skills
Commit: 39464cb

Reviewed: about 5 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.