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).
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill azure-storage95
Quality
93%
Does it follow best practices?
Impact
99%
1.08xAverage score across 3 eval scenarios
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 hits all the key criteria. It provides specific capabilities, comprehensive trigger terms users would naturally use, explicit 'USE FOR' and 'DO NOT USE FOR' clauses that clearly define scope, and strong differentiation from related Azure skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: 'object storage, SMB file shares, async messaging, NoSQL key-value, big data analytics, access tiers, lifecycle management, upload files, download blobs, storage accounts'. | 3 / 3 |
Completeness | Clearly answers both what (Azure Storage Services with specific capabilities) and when (explicit 'USE FOR:' clause with trigger terms, plus 'DO NOT USE FOR:' to clarify boundaries). The explicit trigger guidance is present and comprehensive. | 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'. These are terms users naturally use when working with Azure storage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries. The 'DO NOT USE FOR:' clause explicitly differentiates from SQL databases, Cosmos DB, Event Hubs, and Service Bus, directing to appropriate alternative skills. This significantly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 efficiently covers Azure Storage services with excellent use of tables for compressed information and clear MCP/CLI command references. The content excels at actionability and progressive disclosure but could benefit from explicit multi-step workflows for common operations like setting up storage accounts or managing blob lifecycle transitions.
Suggestions
Add a brief workflow section showing common multi-step operations (e.g., create storage account -> create container -> upload blob) with validation checkpoints
Include a verification step after upload commands (e.g., listing the blob to confirm successful upload)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables to compress information and avoiding explanations of concepts Claude already knows. Every section provides actionable reference data without padding. | 3 / 3 |
Actionability | Provides fully executable CLI commands with clear placeholders (ACCOUNT, CONTAINER, BLOB, LOCAL_PATH), specific MCP tool commands with exact syntax, and concrete guidance for both preferred and fallback approaches. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no explicit workflow for common multi-step operations like setting up a storage account, configuring access tiers, or migrating data. Missing validation steps for operations like uploads. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, well-organized tables, and clearly signaled one-level-deep references to SDK guides, external documentation, and detailed service docs. Navigation is intuitive. | 3 / 3 |
Total | 11 / 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.
Table of Contents
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.