Skills azure-storage-queue-ts
๐Ÿ“ฆ

azure-storage-queue-ts

Content revision r2 Medium Risk โš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Build Azure Queue Workflows in TypeScript

Azure Queue Storage integrations require careful authentication and message lifecycle handling. This skill provides TypeScript patterns for queue administration, processing, retries, encoding, SAS access, and errors.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 69 Adequate

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-storage-queue-ts" from https://skillstore.io/skills/sickn33-azure-storage-queue-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-storage-queue-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.

Test it

Using "azure-storage-queue-ts". Create a worker that receives messages in batches and removes successful items.

Expected outcome:

  • A worker flow receives up to ten messages with a bounded visibility timeout.
  • Successful messages are deleted with their current pop receipts.
  • Failed messages remain available for retry and move to a poison queue after the limit.

Using "azure-storage-queue-ts". Recommend authentication for a Node.js service running in Azure.

Expected outcome:

Use DefaultAzureCredential with the storage account URL and a managed identity that has only the required queue role.

Using "azure-storage-queue-ts". Plan support for a task that may run longer than the visibility timeout.

Expected outcome:

Renew visibility before expiry, retain the latest pop receipt, stop the timer after processing, and delete only after successful completion.

Security Audit

Medium Risk
v5 โ€ข 8/14/2026 Open versioned report

All 87 static findings are false positives caused by Markdown fences, TypeScript template literals, expected Azure endpoints, named environment variables, and standard Base64 decoding. These examples do not execute shell commands, read environment files, or send credentials to unrelated services. One medium concern remains: the account SAS example grants broad permissions across all resource types for 24 hours.

1
Files scanned
534
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Overprivileged Account SAS Example
The account SAS example grants every listed queue permission across service, container, and object resources for 24 hours. Following it unchanged creates excessive access.
The permission string and resource types are explicit, and the expiration is set 24 hours ahead. The example does not apply least privilege.
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-storage-queue-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-storage-queue-ts/security.svg)](https://skillstore.io/skills/sickn33-azure-storage-queue-ts?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-storage-queue-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-storage-queue-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-storage-queue-ts/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-storage-queue-ts-2026, author = {sickn33}, title = {azure-storage-queue-ts security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-storage-queue-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-storage-queue-ts security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-14" url: "https://skillstore.io/skills/sickn33-azure-storage-queue-ts/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-storage-queue-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
78
Spec Compliance

What You Can Build

Create a Queue Client

Configure secure Azure Queue Storage access and select the correct authentication method.

Build a Reliable Worker

Implement message polling, visibility renewal, deletion, retry limits, and poison queue handling.

Review Queue Operations

Check SDK methods, service limits, error handling, and platform compatibility before release.

Try These Prompts

Configure Authentication
Create a TypeScript QueueServiceClient using DefaultAzureCredential and validate the required account name.
Process Messages
Design a worker that receives ten messages, handles each safely, and deletes only successful messages.
Handle Repeated Failures
Add retry limits and a poison queue while preserving message content and avoiding premature deletion.
Design Production Processing
Design a production worker with visibility renewal, idempotency, bounded concurrency, least-privilege access, observability, and graceful shutdown.

Best Practices

  • Prefer managed identity and DefaultAzureCredential over shared keys or long-lived connection strings.
  • Use idempotent processing, bounded retries, and a poison queue for repeated failures.
  • Set visibility timeouts from observed processing duration and renew them for long tasks.

Avoid

  • Do not delete a message before its work completes successfully.
  • Do not grant broad SAS permissions or expose SAS URLs in logs.
  • Do not run an unbounded polling loop without backoff, cancellation, and monitoring.

Frequently Asked Questions

Which Azure package does this skill cover?
It covers the @azure/storage-queue package and uses @azure/identity for identity-based authentication.
Which authentication method is preferred?
Use DefaultAzureCredential with managed identity when the deployment environment supports it.
Can this skill create and delete queues?
Yes. It documents queue creation, listing, properties, metadata, and deletion operations.
How are failed messages handled?
Use dequeue counts, bounded retries, and a separate poison queue for messages that repeatedly fail.
Does it support browser applications?
Basic queue operations and SAS access work in browsers, but shared keys, SAS generation, and DefaultAzureCredential are Node.js features.
Does the skill execute Azure operations automatically?
No. It provides implementation guidance, and users must run and validate the resulting application in their own environment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

5a26d1d61d694db29af9b138c661c1981076d9df

Maintenance freshness

8/15/2026

Usage

7 downloads ยท 94 views

File structure

๐Ÿ“„ SKILL.md