.agent/skills/azure-storage/SKILL.md
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics capabilities. Includes access tiers (hot, cool, archive) and lifecycle management.
npx skillsauth add Tyler-R-Kendrick/agent-skills azure-storageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Service | Use When | MCP Tools | CLI |
|---------|----------|-----------|-----|
| Blob Storage | Objects, files, backups, static content | azure__storage | az storage blob |
| File Shares | SMB file shares, lift-and-shift | - | az storage file |
| Queue Storage | Async messaging, task queues | - | az storage queue |
| Table Storage | NoSQL key-value (consider Cosmos DB) | - | az storage table |
| Data Lake | Big data analytics, hierarchical namespace | - | az storage fs |
When Azure MCP is enabled:
azure__storage with command storage_account_list - List storage accountsazure__storage with command storage_container_list - List containers in accountazure__storage with command storage_blob_list - List blobs in containerazure__storage with command storage_blob_get - Download blob contentazure__storage with command storage_blob_put - Upload blob contentIf Azure MCP is not enabled: Run /azure:setup or enable via /mcp.
# List storage accounts
az storage account list --output table
# List containers
az storage container list --account-name ACCOUNT --output table
# List blobs
az storage blob list --account-name ACCOUNT --container-name CONTAINER --output table
# Download blob
az storage blob download --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH
# Upload blob
az storage blob upload --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH
| Tier | Use Case | Performance | |------|----------|-------------| | Standard | General purpose, backup | Milliseconds | | Premium | Databases, high IOPS | Sub-millisecond |
| Tier | Access Frequency | Cost | |------|-----------------|------| | Hot | Frequent | Higher storage, lower access | | Cool | Infrequent (30+ days) | Lower storage, higher access | | Cold | Rare (90+ days) | Lower still | | Archive | Rarely (180+ days) | Lowest storage, rehydration required |
| Type | Durability | Use Case | |------|------------|----------| | LRS | 11 nines | Dev/test, recreatable data | | ZRS | 12 nines | Regional high availability | | GRS | 16 nines | Disaster recovery | | GZRS | 16 nines | Best durability |
For deep documentation on specific services:
For building applications that interact with Azure Storage programmatically, Azure provides SDK packages in multiple languages (.NET, Java, JavaScript, Python, Go, Rust). See SDK Usage Guide for package names, installation commands, and quick start examples.
tools
Use when building or maintaining a design system — the coordinated set of design tokens, component libraries, documentation, and tooling that ensures visual and behavioral consistency across products. USE FOR: design system architecture, choosing token formats vs component frameworks, connecting Figma to code, design-to-development workflows, multi-platform consistency DO NOT USE FOR: specific token authoring (use design-tokens), Figma workflows (use figma), component cataloging (use storybook), token transformation (use style-dictionary), cross-framework components (use mitosis)
tools
Use when implementing the x402 protocol for HTTP-native micropayments. Covers server middleware, client payment flows, facilitator integration, and stablecoin payments for APIs and AI agents. USE FOR: API micropayments, monetizing endpoints, stablecoin HTTP payments, automated agent payments for API access DO NOT USE FOR: full commerce flows with cart/checkout (use ap2), agent communication (use a2a), tool integration (use mcp)
tools
Use when implementing or integrating with the Model Context Protocol (MCP) for AI tool servers, resources, prompts, and context management. USE FOR: building MCP tool servers, exposing resources to agents, prompt templates, connecting agents to external APIs DO NOT USE FOR: agent-to-agent communication (use a2a), interactive UI rendering (use mcp-apps), agent payments (use x402 or ap2)
tools
Use when building MCP Apps that serve interactive UI from MCP servers. Covers the ui:// URI scheme, HTML rendering in sandboxed iframes, and bidirectional communication between UI and host. USE FOR: rich UI in agent conversations, interactive dashboards from MCP servers, sandboxed iframe rendering DO NOT USE FOR: basic tool responses without UI (use mcp), agent communication (use a2a), full web applications