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.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 completeness via the explicit WHEN clause. Its main weakness is that the 'what' portion describes categories of issues rather than specific concrete troubleshooting actions. The extensive keyword list in the WHEN clause is highly effective for skill selection but borders on being a keyword dump rather than natural prose.
Suggestions
Strengthen specificity by listing concrete actions such as 'diagnose AMQP connection errors', 'resolve checkpoint store configuration', 'debug dead-letter queue processing' instead of broad categories like 'connection failures' and 'message processing issues'.
| 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 connection errors' or 'configure checkpoint stores'. The actions are more categorical than concrete. | 2 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot Azure Messaging SDK issues for Event Hubs and Service Bus covering connection failures, auth errors, message processing, and config problems) and 'when' with an explicit 'WHEN:' clause containing extensive trigger scenarios. | 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 symptoms ('event hub not receiving messages', 'service bus dead letter', 'duplicate events', 'slow reconnect'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Azure Messaging SDKs (Event Hubs and Service Bus). The combination of specific Azure services, AMQP protocol references, and SDK-specific trigger terms makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured overview skill that excels at progressive disclosure and conciseness, serving as an effective routing document to detailed SDK-specific guides. Its main weakness is the lack of concrete inline examples—no sample KQL queries, no example error messages with their fixes, and no executable diagnostic commands—which limits immediate actionability. The workflow would benefit from explicit validation checkpoints and error-recovery branching.
Suggestions
Add 1-2 concrete KQL query examples for common diagnostic scenarios (e.g., querying for connection failures or message lock expirations) to make the diagnosis workflow immediately actionable.
Include a small inline table mapping 2-3 of the most common error messages to their root causes and quick fixes, so Claude doesn't always need to navigate to reference files.
Add explicit validation/feedback steps to the diagnosis workflow, e.g., 'After applying fix, verify with resource health check' or 'If error persists after config change, re-query diagnostic logs to confirm.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what Azure Event Hubs or Service Bus are, assumes Claude's competence, and every section serves a clear purpose. The tables are efficient information delivery. | 3 / 3 |
Actionability | The skill provides specific MCP tool names and a diagnosis workflow, but lacks concrete executable examples—no KQL queries, no example connection string validation commands, no specific error-to-fix mappings inline. The actionable details are deferred to reference files. | 2 / 3 |
Workflow Clarity | The 6-step diagnosis workflow is clearly sequenced, but lacks explicit validation checkpoints or feedback loops. There's no 'if this fails, do X' branching except implicitly ('ask later if needed'). For a troubleshooting skill involving potentially destructive operations like configuration changes, the absence of verification steps is notable. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, well-organized tables, and clearly signaled one-level-deep references to SDK-specific guides and the service troubleshooting guide. Navigation is easy with language-specific links clearly laid out. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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/azure-skills
- Commit
742d20b
- Reviewed
Table of Contents
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.