azure-storage
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. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, lifecycle management. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).
91
86%
Does it follow best practices?
Impact
99%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that covers all evaluation dimensions well. It names specific Azure Storage services and their capabilities, provides comprehensive trigger terms in a USE FOR clause, and explicitly delineates boundaries with a DO NOT USE FOR clause that references alternative skills. The description is well-structured, concise, and would allow Claude to confidently select or reject this skill from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: object storage, SMB file shares, async messaging, NoSQL key-value, big data analytics, access tiers, and lifecycle management across five named Azure Storage services. | 3 / 3 |
Completeness | Clearly answers both 'what' (Azure Storage Services with specific capabilities) and 'when' (explicit USE FOR and DO NOT USE FOR clauses with trigger terms and routing guidance to other skills). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'blob storage', 'file shares', 'queue storage', 'table storage', 'data lake', 'upload files', 'download blobs', 'storage accounts', 'access tiers', 'lifecycle management'. These are terms users would naturally use when working with Azure Storage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit DO NOT USE FOR boundaries that route SQL databases, Cosmos DB, Event Hubs, and Service Bus to other specific skills, minimizing conflict risk with related Azure skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured reference skill that effectively uses tables for quick lookup and provides concrete CLI commands and MCP tool references. Its main weaknesses are minor redundancy between the SDK sections and the lack of any validation/verification guidance for storage operations. The progressive disclosure pattern with per-language SDK references is a notable strength.
Suggestions
Remove the duplicate 'Azure SDKs' section at the bottom since 'SDK Quick References' already covers the same content with more detail.
Add a brief verification step after upload/download commands (e.g., `az storage blob show` to confirm upload success) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables, but has some redundancy—the 'Azure SDKs' section at the bottom largely repeats the 'SDK Quick References' section above it. The redundancy options and storage account tiers tables, while informative, are reference material Claude likely already knows or could look up. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands with clear parameter placeholders, specific MCP tool commands with exact command names, and direct links to SDK guides per language. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/lookup skill rather than a multi-step workflow, so complex sequencing isn't strictly required. However, there are no validation steps for operations like uploads/downloads (e.g., verifying upload success, checking blob properties after upload), and the MCP vs CLI decision path could be more explicitly sequenced. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file, well-organized tables for quick reference, and clearly signaled one-level-deep references to SDK guides per language and external documentation. Navigation is intuitive and well-structured. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
9d594ab
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.