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. The main weakness is that the 'what' portion could be more specific about concrete actions (e.g., 'diagnose connection errors', 'configure retry policies', 'analyze dead-letter queues') rather than listing broad categories. The extensive keyword list is a strength for discoverability but borders on being a keyword dump rather than a readable description.
Suggestions
Enhance specificity by listing concrete actions like 'diagnose AMQP link detach errors', 'configure retry and timeout policies', 'analyze dead-letter queue messages', 'set up SDK logging' instead of broad categories like 'connection failures' and 'SDK configuration problems'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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'. | 2 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot and resolve issues with Azure Messaging SDKs covering connection failures, auth errors, message processing, SDK config) and 'when' with an explicit 'WHEN:' clause followed by an extensive list of 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'), and common scenarios ('event hub not receiving messages', 'service bus dead letter', 'duplicate events', 'offset reset'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Azure Messaging SDKs for Event Hubs and Service Bus troubleshooting) with domain-specific trigger terms like 'AMQP error', 'event processor host issue', 'message lock lost' that are 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 skill excels at organization and progressive disclosure, providing a clean hub that routes to language-specific and service-specific guides. It's concise and well-structured. However, it lacks concrete actionable examples (KQL queries, code snippets, specific error-to-fix mappings) in the main file, and the workflow could benefit from explicit validation/feedback loops.
Suggestions
Add 1-2 concrete KQL query examples for common diagnostic scenarios (e.g., querying for connection failures or message lock expirations) to improve actionability.
Add a feedback loop to the diagnosis workflow, e.g., 'After applying fix, verify by re-checking resource health and monitoring logs for recurrence' to improve workflow clarity.
Include a small quick-reference table mapping 2-3 of the most common error messages to their likely causes and fixes directly in this file, rather than requiring navigation to sub-guides for every issue.
| 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 diagnosis workflow provides a clear sequence of steps with specific tool names, but lacks concrete executable examples—no KQL queries, no code snippets for enabling logging, no specific connection string formats or configuration examples. The guidance is directional rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 6-step diagnosis workflow is clearly sequenced and references specific tools, but lacks explicit validation checkpoints or feedback loops. There's no 'if this fails, try that' branching, and no verification step to confirm the fix worked after applying remediation. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview that clearly signals one-level-deep references to 8 SDK-specific guides and a service troubleshooting guide. Navigation is well-organized by service and language, and references are clearly labeled. | 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
9d594ab
- 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.