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 key dimensions thoroughly. It lists specific Azure Storage services and capabilities, includes comprehensive natural trigger terms users would use, explicitly defines both when to use and when not to use the skill, and clearly distinguishes itself from related Azure skills through explicit exclusion clauses. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and services: 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 like object storage, SMB file shares, access tier guidance, lifecycle management) and 'when' (explicit 'USE FOR' clause with trigger terms, plus a 'DO NOT USE FOR' clause that further clarifies boundaries). | 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 a clear niche (Azure Storage Services) and explicit boundary-setting via the 'DO NOT USE FOR' clause that redirects SQL databases, Cosmos DB, Event Hubs, and Service Bus to other skills. This significantly reduces conflict risk. | 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 Azure Storage reference skill that effectively uses tables for quick lookup and provides concrete CLI commands and MCP tool references. Its main weaknesses are a slightly redundant SDK section at the bottom and the lack of validation/verification guidance for storage operations. The progressive disclosure is strong with clear pointers to language-specific SDK references.
Suggestions
Remove or merge the duplicate 'Azure SDKs' section at the bottom with the 'SDK Quick References' section to eliminate redundancy.
Add a brief verification step after upload/download CLI 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 what 'SDK Quick References' already covers. The MCP tool listing could be slightly more compact. Overall mostly lean but not perfectly tight. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands with clear placeholders (ACCOUNT, CONTAINER, BLOB, LOCAL_PATH), specific MCP tool commands with exact command names, and well-structured reference tables for decision-making on tiers and redundancy. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/lookup skill rather than a multi-step workflow, so explicit sequencing is less critical. However, there are no validation steps for storage operations (e.g., verifying upload success, checking blob existence before download), and the MCP vs CLI fallback path could be more explicitly sequenced. | 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 Microsoft documentation, and an 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
915f809
- 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.