huytran1120/vietnam-agentic-skills/azure-storage-queue-rust
Claude Code and agent skill by huytran1120/vietnam-agentic-skills
- community
Checking that the SKILL.md file is still in the repository.
Azure Queue Storage library for Rust. Send, receive, and manage queue messages. Triggers: "queue storage rust", "QueueClient rust", "send message rust", "receive messages rust", "QueueServiceClient rust", "queue rust".
Install
npx vskill@latest install huytran1120/vietnam-agentic-skills/azure-storage-queue-rustSKILL.md
The same SKILL.md was published earlier as sickn33/agentic-awesome-skills/azure-storage-queue-rust.
Azure Queue Storage library for Rust
When to Use
Use this skill when you need azure Queue Storage library for Rust. Send, receive, and manage queue messages. Triggers: "queue storage rust", "QueueClient rust", "send message rust", "receive messages rust", "QueueServiceClient rust", "queue rust".
Client library for Azure Queue Storage — send, receive, and manage queue messages.
Use this skill when:
- An app needs to send or receive messages from Azure Queue Storage in Rust
- You need to create or manage queues
- You need to peek, receive, or delete queue messages
- You need RBAC-based auth for queue operations
IMPORTANT: Only use the officialazure_storage_queuecrate published by the azure-sdk crates.io user. Do NOT use unofficial or community crates. Official crates use underscores in names and none have version 0.21.0.
Installation
If your code usesazure_coretypes directly, addazure_coretoCargo.toml. If you only useazure_storage_queuere-exports, directazure_coredependency is optional.
Environment Variables
Authentication
Client Types
| Client | Purpose | Access | |
|---|---|---|---|
QueueServiceClient | Account-level operations, list queues | QueueServiceClient::new() | |
QueueClient | Queue operations, send/receive/delete | service_client.queue_client("<name>")? |
Core Workflow
Send a Message
Receive Messages
Delete a Message
After receiving a message, delete it using the message ID and pop receipt:
Peek Messages
Peek at messages without removing them from the queue:
RBAC Roles
For Entra ID auth, assign one of these roles to the identity:
| Role | Access | |
|---|---|---|
Storage Queue Data Reader | Read and peek messages | |
Storage Queue Data Contributor | Read/write messages | |
Storage Queue Data Message Sender | Send messages only | |
Storage Queue Data Message Processor | Receive and delete |
Best Practices
- Use `cargo add` to manage dependencies, never edit `Cargo.toml` directly. Add and remove Rust SDK dependencies with cargo commands instead of manual manifest edits.
- Add `azure_core` only when importing `azure_core` types directly. If your code imports
azure_core::http::Url,azure_core::http::RequestContent, orazure_core::error::ErrorKind, includeazure_core; otherwise a direct dependency is optional. - Use `DeveloperToolsCredential` for local dev, `ManagedIdentityCredential` for production — Rust does not provide a single
DefaultAzureCredentialtype - Never hardcode credentials — use environment variables or managed identity
- Assign RBAC roles — ensure appropriate queue data roles for the identity
- Use `QueueServiceClient` as the entry point and derive
QueueClientfrom it viaqueue_client() - Delete messages after processing — use the message ID and pop receipt from
receive_messages - Reuse clients — clients are thread-safe; create once, share across tasks
Reference Links
| Resource | Link | |
|---|---|---|
| API Reference | https://docs.rs/crate/azure_storage_queue/latest | |
| crates.io | https://crates.io/crates/azure_storage_queue | |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/storage/azure_storage_queue |
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
Queue delivery can repeat. Make processing idempotent, extend visibility only within a bounded policy and delete a message only after the intended durable effect succeeds. A received message is not completed work; handle poison messages and expired pop receipts explicitly. Pin compatible crate versions and enable the Tokio runtime/macro features required by the chosen example.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/azure-storage-queue-rust/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/huytran1120/vietnam-agentic-skills/azure-storage-queue-rust)