azure-servicebus-ts
Build Azure Service Bus Messaging Apps
This skill provides code examples and patterns for implementing Azure Service Bus messaging in JavaScript and TypeScript applications. It helps developers quickly implement queues, topics, and message handling.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "azure-servicebus-ts". Send message to queue
Expected outcome:
Code example showing how to create a ServiceBusClient, create a sender, and send a message with proper body and contentType.
Using "azure-servicebus-ts". Receive from subscription
Expected outcome:
Code example showing receiver setup with subscribe method, processMessage handler, and error handling callback.
Using "azure-servicebus-ts". Dead-letter handling
Expected outcome:
Code example showing how to create a receiver for the dead-letter subqueue and process messages from it.
Security Audit
SafeAll 46 static findings are false positives. The skill is legitimate Azure Service Bus documentation containing code examples in markdown. The backtick patterns are from markdown code fences, not shell execution. Environment variable access is for Azure configuration (standard practice). No cryptographic algorithms or malicious patterns present.
Low Risk Issues (3)
Quality Score
What You Can Build
Backend Developer Building Event-Driven Systems
Implement async communication between microservices using Azure Service Bus queues and topics.
Cloud Architect Designing Messaging Patterns
Create scalable pub-sub architectures with topics, subscriptions, and message sessions.
DevOps Engineer Setting Up Integration
Connect Azure services and external systems using Service Bus message routing.
Try These Prompts
Use the Azure Service Bus skill to show me how to send a JSON message to a queue named 'orders'.
Show me how to set up a message subscription receiver that processes messages from a topic subscription.
How do I process messages from a dead-letter queue to handle failed messages?
Show me how to use message sessions to ensure ordered processing of related messages.
Best Practices
- Use Entra ID (Azure AD) authentication instead of connection strings in production
- Reuse ServiceBusClient instances across your application for connection pooling
- Always close senders and receivers when done to free resources
- Implement proper error handling with processError callbacks
- Use message sessions when order matters within a group of messages
Avoid
- Creating a new ServiceBusClient for each message (causes connection overhead)
- Hardcoding connection strings in source code (use environment variables)
- Not handling dead-letter messages (leads to lost data)
- Not closing senders/receivers (causes resource leaks)
Frequently Asked Questions
What authentication methods does this skill support?
Can I use this skill with Azure Event Hubs?
How do I handle messages that fail processing?
What is the difference between peekLock and receiveAndDelete?
Can I send messages to multiple queues in one batch?
Do I need to install the Azure Identity package?
Developer Details
Author
sickn33License
MIT
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-servicebus-tsRef
main
File structure
📄 SKILL.md