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. USE FOR: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, 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 DO NOT USE FOR: creating Event Hub or Service Bus resources (use azure-prepare), cost analysis (use azure-cost-optimization)
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill azure-messaging91
Quality
86%
Does it follow best practices?
Impact
99%
1.67xAverage score across 3 eval scenarios
Quality
Discovery
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.
This is an excellent skill description that hits all the key criteria. It provides specific troubleshooting capabilities, extensive natural trigger terms covering multiple languages and error types, explicit 'USE FOR' and 'DO NOT USE FOR' clauses, and clear boundaries to prevent conflicts with related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'connection failures, authentication errors, message processing issues, and SDK configuration problems' - these are specific troubleshooting scenarios rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Troubleshoot and resolve issues with Azure Messaging SDKs') and when (explicit 'USE FOR:' clause with extensive trigger terms, plus 'DO NOT USE FOR:' to prevent misuse). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including SDK-specific terms ('AMQP error', 'message lock lost', 'send timeout'), language-specific variants ('eventhub python', 'servicebus java', 'servicebus dotnet'), and common issue phrases ('not receiving messages', 'dead letter'). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Azure Messaging SDK troubleshooting with explicit boundaries via 'DO NOT USE FOR' clause that distinguishes from resource creation and cost analysis skills. | 3 / 3 |
Total | 12 / 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 token efficiency, providing a clean overview with well-structured references to detailed SDK guides. However, it lacks concrete executable examples and validation checkpoints in the diagnosis workflow, making it more of a navigation hub than an actionable troubleshooting guide.
Suggestions
Add at least one concrete code example showing how to enable SDK logging for a common language (e.g., Python or .NET) directly in the skill
Enhance the diagnosis workflow with explicit validation steps, e.g., 'If resource health shows degraded, check Azure Status page before proceeding'
Include a sample KQL query for the `logs_query` tool to demonstrate how to search diagnostic logs for common errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | The diagnosis workflow provides clear steps, but lacks concrete executable code examples. The guidance is procedural but relies heavily on external references rather than providing copy-paste ready commands or code snippets. | 2 / 3 |
Workflow Clarity | The 6-step diagnosis workflow is clearly sequenced, but lacks explicit validation checkpoints or feedback loops for error recovery. No guidance on what to do if a step fails or how to verify each step succeeded. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to SDK-specific guides and service troubleshooting. Navigation is clear with organized links by language and service type. | 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.
- 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.