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).
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 DO NOT USE FOR guidance that routes to 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 to azure-prepare and messaging to azure-messaging, clearly carving out its niche and reducing 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 solid reference-style skill that effectively covers Azure Storage services with good use of tables for quick scanning and clear progressive disclosure to detailed SDK guides. The main weaknesses are some content redundancy (SDK sections appear twice) and lack of workflow validation steps for storage operations. The actionability is strong with concrete CLI commands and specific MCP tool names.
Suggestions
Remove the duplicate 'Azure SDKs' section since 'SDK Quick References' already covers the same content with more detail.
Add a brief validation step after upload/download operations (e.g., 'Verify upload: az storage blob show --account-name ACCOUNT --container-name CONTAINER --name BLOB').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables, but has some redundancy — the 'Azure SDKs' section largely repeats the 'SDK Quick References' section above it, and the Reference Index partially overlaps with Service Details links. The redundancy options and storage account tiers tables, while informative, are reference material Claude likely already knows. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands with clear placeholder patterns (ACCOUNT, CONTAINER, BLOB, LOCAL_PATH). MCP tool commands are specific with exact command names. Both primary (MCP) and fallback (CLI) paths are clearly defined. | 3 / 3 |
Workflow Clarity | The skill covers multiple discrete operations (list, upload, download) but doesn't sequence them into workflows with validation steps. For operations like blob upload, there's no verification step (e.g., confirming upload succeeded, checking blob properties after upload). The MCP fallback instruction is clear but the overall flow between choosing MCP vs CLI could be more explicit. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-organized one-level-deep references to SDK guides by language, external documentation links, and on-demand reference files. The 'Load these on demand — do NOT read all at once' instruction is a strong pattern. | 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
- jonathan-vella/azure-agentic-infraops
- Commit
ec7b8ff
- 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.