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

85%

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

Quality

Content

76%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 concise, well-structured overview that leverages tables and a clear diagnostic workflow with concrete MCP tool references. Its main weakness is that the substantive troubleshooting guides are delegated to an external skill and the workflow lacks explicit validation/decision checkpoints.

Suggestions

Add explicit decision branches to the Diagnosis Workflow (e.g., 'If resource health is degraded, report and stop before continuing SDK diagnosis') to introduce validation checkpoints.

Inline at least one concrete example invocation, such as a sample KQL query for mcp_azure_mcp_monitor or a representative resource-health check command, to lift actionability.

Either co-locate a short troubleshooting reference in a local references/ file or summarize the top 2-3 common error→fix pairs inline so the skill stands alone without the azure-diagnostics dependency.

Dimension	Reasoning	Score
Conciseness	Lean body built from tables and short bullet lists with no over-explanation of concepts Claude already knows; every section earns its tokens. The 'When to Use' list slightly echoes the description's WHEN clause but stays brief.	5 / 5
Actionability	Names concrete MCP tools and commands ('mcp_azure_mcp_resourcehealth', 'logs_query', 'get') and a sequenced workflow, but substantive remediation is delegated to the external azure-diagnostics skill and no example KQL or command syntax is shown, leaving minor gaps.	4 / 5
Workflow Clarity	The 6-step Diagnosis Workflow is clearly sequenced, but checkpoints are implicit (e.g., 'Check resource health' with no stated branch if unhealthy) and there are no explicit validation/feedback loops, matching the steps-listed-but-checkpoints-implicit anchor.	3 / 5
Progressive Disclosure	Well-organized into clear sections with a one-level-deep, clearly signaled reference to the azure-diagnostics skill for detailed guides; slight gap is that the core troubleshooting content lives in another skill rather than co-located bundle files.	4 / 5
	Total	16 / 20 Passed

Description

95%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 strong, well-structured description: third-person voice, explicit what-and-when, and a dense set of natural trigger terms including language-specific variants. Minor room only in listing more granular concrete actions versus capability categories.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure Messaging SDKs for Event Hubs and Service Bus') and lists several concrete capability categories ('connection failures, authentication errors, message processing issues, and SDK configuration problems'), but stops at category-level rather than enumerating granular actions like the 5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Troubleshoot and resolve issues with Azure Messaging SDKs... Covers...') and 'when' (a WHEN: clause with concrete trigger phrases), matching the anchor that requires both answered explicitly.	5 / 5
Trigger Term Quality	The WHEN clause packs comprehensive natural terms including synonyms, language-specific variants ('eventhub python, servicebus java, eventhub javascript, servicebus dotnet'), and concrete error names ('message lock lost', 'idle timeout', 'link detach'), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Azure Messaging SDKs for Event Hubs and Service Bus) with highly specific triggers, making accidental triggering for unrelated skills minimal.	5 / 5
	Total	19 / 20 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
Path: .github/plugins/azure-skills/skills/azure-messaging/SKILL.md
Commit: 16dc8c5

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