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

—

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.

The body is concise and well-structured with a clear diagnosis workflow and one-level references to detailed guides. Its weaknesses are actionability and workflow clarity: actual remediation steps are deferred elsewhere and the workflow lacks explicit error-recovery feedback loops.

Suggestions

Add concrete remediation snippets inline (e.g., example KQL diagnostic queries via mcp_azure_mcp_monitor, or a sample lock-renewal code pattern) so the skill is actionable without always deferring to the azure-diagnostics skill or docs.

Add an explicit error-recovery branch to the Diagnosis Workflow, e.g. 'If mcp_azure_mcp_resourcehealth reports unhealthy: check for service incidents via mcp_azure_mcp_monitor logs_query before continuing', to give the workflow a real feedback loop.

Expand the Troubleshooting Guides section with direct links or anchors into the azure-diagnostics messaging paths so navigation to the deferred detail is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — compact tables for Quick Reference and MCP Tools, a tight 6-step workflow, and no padding or explanation of concepts Claude already knows. Every section earns its place, fitting the top anchor.	3 / 3
Actionability	It names concrete MCP tools and their uses, but the actual remediation guidance is offloaded ('Recommend fix — Apply remediation, citing documentation found') and detailed fixes live in the azure-diagnostics skill. Concrete guidance is present but incomplete, matching the middle rather than the top anchor.	2 / 3
Workflow Clarity	The Diagnosis Workflow is a clear numbered sequence with a resource-health checkpoint (step 2), but it lacks explicit error-recovery feedback loops (e.g., what to do if the namespace is unhealthy). Sequence is present but checkpoints/feedback are implicit, so it does not reach the top anchor.	2 / 3
Progressive Disclosure	The short body is well-organized into clear sections and signals one-level-deep external detail ('troubleshooting guides are located in the azure-diagnostics skill under troubleshooting/messaging/'), with no deeply nested references. No local bundle files exist, so the well-structured overview qualifies for the top anchor.	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.

The description is strong: it states concrete capabilities, includes an explicit WHEN trigger list with natural user terms, and is tightly scoped to Azure Messaging SDKs. It clearly answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and scope: 'Troubleshoot and resolve issues', 'Covers connection failures, authentication errors, message processing issues, and SDK configuration problems' across Event Hubs and Service Bus. Not vague or abstract, so it sits at the top anchor rather than 2.	3 / 3
Completeness	Explicitly answers both what ('Troubleshoot and resolve issues with Azure Messaging SDKs...') and when (an explicit 'WHEN:' clause with triggers), matching the top anchor. Not 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	The 'WHEN:' clause supplies a broad set of natural terms users would say ('message lock lost', 'send timeout', 'idle timeout', 'event hub not receiving messages', 'service bus dead letter'), covering common variations rather than only jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Azure Messaging SDKs for Event Hubs and Service Bus with service-specific triggers, giving it a clear niche unlikely to conflict with 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: 2cd48ca

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