azure-storage
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier, and tier comparison. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. Includes lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, storage tiers, hot cool cold archive, storage tier comparison, when to use storage tiers, lifecycle management, Azure Storage concepts. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).
71
86%
Does it follow best practices?
Impact
—
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 strongly. It provides specific capabilities, comprehensive trigger terms, explicit use/don't-use guidance, and clear boundaries with other skills. The DO NOT USE FOR clause with skill routing suggestions is a particularly effective pattern for reducing conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: Blob Storage, File Shares, Queue Storage, Table Storage, Data Lake, access tiers (hot, cool, cold, archive), lifecycle management, object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. | 3 / 3 |
Completeness | Clearly answers both 'what' (Azure Storage Services with specific capabilities listed) and 'when' (explicit USE FOR clause with trigger terms, plus DO NOT USE FOR exclusions that help Claude route correctly). The explicit trigger guidance is thorough. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'blob storage', 'file shares', 'queue storage', 'upload files', 'download blobs', 'storage accounts', 'access tiers', 'hot cool cold archive', 'storage tier comparison', 'lifecycle management'. These are terms users would naturally use when asking about Azure Storage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit DO NOT USE FOR exclusions referencing specific alternative skills (azure-prepare for Cosmos DB, azure-messaging for Event Hubs/Service Bus). This clear boundary-setting makes it very unlikely to conflict with other Azure-related 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 excels at progressive disclosure and actionability, providing concrete MCP commands and CLI fallbacks in a scannable table-driven format. Its main weaknesses are minor redundancy (duplicate SDK sections) and the lack of workflow validation steps for storage operations. The content effectively serves as a quick-reference hub pointing to detailed SDK guides.
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., 'Verify upload: az storage blob show --account-name ACCOUNT --container-name CONTAINER --name BLOB') 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 contain information Claude likely already knows. Still, most content is well-structured and not overly verbose. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands with clear parameter placeholders, specific MCP tool commands with exact command names, and well-organized reference tables. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | The skill presents individual commands clearly but lacks sequenced workflows with validation steps. For storage operations (especially uploads/downloads), there are no verification steps (e.g., confirming upload succeeded, checking blob properties after upload). The MCP fallback to CLI is clearly signaled, which is good. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and well-signaled one-level-deep references to SDK guides across multiple languages, external documentation links, and a centralized SDK usage guide. Navigation is clear and organized by service and language. | 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/github-copilot-for-azure
- Commit
dd731da
- 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.