CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-skills/skills/azure-messaging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 diagnostic overview with concrete MCP tool names, but it functions as a pointer document whose substantive content (language-specific troubleshooting guides) lives in another skill not present in this bundle, and its workflow lacks outcome-based branching. The result is guidance that names the right tools yet stops short of being self-sufficiently actionable.

Suggestions

Include the language-specific troubleshooting guides (or at least an error-to-guide index with per-language error signatures) in this bundle's references/ instead of pointing to the separate 'azure-diagnostics' skill, since step 3 of the workflow depends on them.

Add one concrete example per MCP tool — e.g., a sample logs_query KQL statement for connection drops and a sample resourcehealth invocation — so the workflow steps are executable rather than descriptive.

Add outcome-based checkpoints to the diagnosis workflow: what to conclude and do next when resource health is degraded, when the error matches no known guide, and when a configuration check fails.

DimensionReasoningScore

Conciseness

The body is lean: tables, a numbered workflow, and no explanations of concepts Claude already knows. Minor duplication keeps it off the top anchor — MCP tools appear in both the Quick Reference and MCP Tools tables, and the Microsoft Learn documentation tip appears in both the workflow (step 4) and the References section. Not 3: nothing is padded or over-explained.

4 / 5

Actionability

Concrete tool names and commands are given ("mcp_azure_mcp_monitor | logs_query | Query diagnostic logs with KQL") and the workflow names a tool per step, but there are no example invocations or KQL samples, and the key matching resource ("language-specific troubleshooting guide") is delegated to a separate 'azure-diagnostics' skill whose files are not in this bundle. This sits between 'some concrete guidance but incomplete' and 'mostly executable guidance'; the missing in-bundle detail and lack of any example call pull it to 3.

3 / 5

Workflow Clarity

A clear six-step diagnosis sequence is present with one checkpoint (step 2, resource health verification), but there are no feedback loops or branch guidance for what to do with each step's outcome — e.g., what if resource health is degraded, or the error matches no guide entry. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, which requires most checkpoints with only minor gaps.

3 / 5

Progressive Disclosure

Sections are well-organized for a short skill, but the only reference to deeper content is a single prose line ("guides are located in the azure-diagnostics skill under `troubleshooting/messaging/`") pointing to files outside this bundle — no references/, scripts/, or assets/ directories exist here — so the pointer is neither clearly signaled nor resolvable. This matches 'references present but not clearly signaled' rather than 4, where references are mostly clear and in-bundle.

3 / 5

Total

13

/

20

Passed

Description

91%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 description: concrete domain statement, explicit WHEN clause, and an unusually thorough list of natural trigger terms including SDK-language variants. The only weakness is a handful of generic trigger phrases that create minor cross-ecosystem overlap risk.

DimensionReasoningScore

Specificity

Names the domain ("Azure Messaging SDKs for Event Hubs and Service Bus") and several concrete issue categories ("connection failures, authentication errors, message processing issues, and SDK configuration problems"), matching the 'several specific actions; minor gaps' anchor. Not 5: the only action verbs are 'Troubleshoot and resolve', with issue categories rather than a comprehensive list of concrete actions.

4 / 5

Completeness

Explicitly answers 'what' ("Troubleshoot and resolve issues with Azure Messaging SDKs... Covers connection failures, authentication errors...") and 'when' via an explicit "WHEN:" clause with concrete trigger phrases, matching the top anchor. It clearly exceeds the 4 anchor, where the 'when' is present but less explicit.

5 / 5

Trigger Term Quality

Roughly forty natural trigger phrases users would actually say ("event hub SDK error", "message lock lost", "send timeout", "eventhub python", "servicebus java"), including SDK/language variants like "eventhub javascript", "servicebus dotnet", and symptom phrasings like "event hub not receiving messages". Comprehensive synonym coverage; the anchor below (4) is for coverage with a few natural terms missing, which does not apply.

5 / 5

Distinctiveness Conflict Risk

Mostly distinct niche (Azure Event Hubs/Service Bus SDK troubleshooting with SDK-specific triggers like "event processor host issue" and "service bus dead letter"), but several generic trigger terms ("idle timeout", "session error", "duplicate events", "offset reset", "receive batch") could fire for non-Azure messaging work (Kafka, RabbitMQ), giving minor overlap risk. Not 5 for that overlap; not 3 since the bulk of triggers are clearly Azure-specific.

4 / 5

Total

18

/

20

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 — 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

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.