Azure Messaging β Event Hubs & Service Bus Doctor
Troubleshoot Azure messaging SDKs β AMQP errors, connection failures, message lock loss and dead letters for Event Hubs and Service Bus
- What
- Troubleshoot Azure messaging SDKs β AMQP errors, connection failures, message lock loss and dead letters for Event Hubs and Service Bus
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid Azure subscription required β Curated by Skill Harbor β Microsoft's troubleshooting skill for the Azure Messaging SDKs: diagnose Event Hubs and Service Bus issues β connection failures, authentication errors, AMQP link detaches, idle timeouts, message and session lock loss, dead letters, duplicate events and checkpoint resets β with a six-step workflow (identify SDK version, check resource health, match the error, search Microsoft Learn, verify configuration, recommend the fix) and language-specific guides under the azure-diagnostics references. By @microsoft, listed here with credit to its creator. Honest caveats: diagnosis only β it pinpoints SDK and configuration issues and points to fixes, it doesn't patch your code for you. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Azure Messaging β Event Hubs & Service Bus Doctor" for me. Troubleshoot Azure messaging SDKs β AMQP errors, connection failures, message lock loss and dead letters for Event Hubs and Service Bus Repository: https://github.com/microsoft/azure-skills/blob/main/.github/plugins/azure-skills/skills/azure-messaging/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "microsoft-azure-messaging". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.