Skills azure-servicebus-ts
๐Ÿ“ฆ

azure-servicebus-ts

Content revision r2 Safe โš™๏ธ External commands๐Ÿ”‘ Env variables

Build Azure Service Bus Workflows in TypeScript

Reliable Azure Service Bus integrations require correct authentication, settlement, ordering, and recovery patterns. This skill provides focused TypeScript examples for common messaging workflows.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "azure-servicebus-ts" from https://skillstore.io/skills/sickn33-azure-servicebus-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-servicebus-ts/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "azure-servicebus-ts". Plan a queue consumer for order validation.

Expected outcome:

  • Use peek-lock mode so failed orders can be abandoned or dead-lettered.
  • Complete each message only after validation and durable processing succeed.
  • Record validation failures with a clear dead-letter reason.

Using "azure-servicebus-ts". Choose between a queue and a topic for billing events.

Expected outcome:

Use a topic when billing, analytics, and notifications need independent copies. Use a queue when one competing consumer should process each event.

Using "azure-servicebus-ts". Improve throughput for a high-volume sender.

Expected outcome:

  • Reuse one Service Bus client and sender.
  • Build SDK message batches and send each accepted batch.
  • Close resources during application shutdown.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 39 static alerts are false positives caused by Markdown fences, TypeScript template literals, a normal namespace environment variable, and security guidance. No executable Ruby backticks, sensitive file access, system reconnaissance, prompt injection, or malicious intent were found.

1
Files scanned
244
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-azure-servicebus-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-servicebus-ts/security.svg)](https://skillstore.io/skills/sickn33-azure-servicebus-ts?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-servicebus-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-servicebus-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-servicebus-ts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). azure-servicebus-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-servicebus-ts/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-servicebus-ts-2026, author = {sickn33}, title = {azure-servicebus-ts security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-servicebus-ts/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "azure-servicebus-ts security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-azure-servicebus-ts/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-servicebus-ts:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Build an order queue worker

Create a TypeScript producer and consumer with explicit message settlement and error handling.

Standardize cloud messaging patterns

Define passwordless authentication, client reuse, batching, and resource lifecycle conventions for a team.

Investigate failed deliveries

Inspect dead-letter messages and plan safe recovery or completion workflows.

Try These Prompts

Create a basic queue example
Show a TypeScript example that sends one message to [queue name] and receives it with peek-lock settlement.
Design topic subscriptions
Design a TypeScript publisher and subscriber for [topic] and [subscription], including application properties and error handling.
Add ordered processing
Create a session-based workflow for [process], preserving order by [group key] and maintaining session progress.
Review production reliability
Review my Service Bus design for authentication, batching, settlement, dead-letter recovery, client lifecycle, and receive-mode risks.

Best Practices

  • Prefer Entra ID authentication and grant only required Service Bus roles.
  • Reuse clients and close senders, receivers, and subscriptions during shutdown.
  • Use peek-lock settlement and process the dead-letter queue explicitly.

Avoid

  • Do not embed production connection strings or credentials in source code.
  • Do not complete messages before business processing finishes successfully.
  • Do not use receive-and-delete when message loss is unacceptable.

Frequently Asked Questions

Does this skill provision Azure Service Bus resources?
No. It focuses on TypeScript SDK usage and assumes required namespaces and messaging entities already exist.
Which authentication method does it recommend?
It recommends DefaultAzureCredential with Entra ID and a namespace supplied through environment configuration.
Does it cover queues and topics?
Yes. It includes queue senders and receivers, topic publishers, and subscription receivers.
Can it help preserve message order?
Yes. It demonstrates sessions, session identifiers, and session state for ordered workflows.
Does it explain failed message handling?
Yes. It shows dead-lettering, dead-letter queue receiving, and explicit completion.
Is the generated guidance production ready?
Not by itself. Validate permissions, retries, lock duration, observability, shutdown behavior, and deployment settings in your environment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads ยท 90 views

File structure

๐Ÿ“„ SKILL.md