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).

Quality

86%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 format. Its main weaknesses are a redundant SDK section at the bottom and the lack of workflow sequences for common multi-step storage operations (e.g., create account → create container → upload → verify).

Suggestions

Remove the redundant 'Azure SDKs' section at the bottom since 'SDK Quick References' already covers the same content and links to the same guide.

Add a brief workflow example for a common multi-step operation (e.g., setting up storage and uploading a blob) with validation checkpoints like verifying the upload succeeded.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of tables, but the 'Azure SDKs' section at the bottom is redundant with the 'SDK Quick References' section just above it, both pointing to the same sdk-usage.md. The redundancy options and storage account tiers tables, while useful, include information Claude likely already knows.	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 any sequenced workflow for common multi-step operations (e.g., creating a storage account, then container, then uploading). There are no validation checkpoints or error handling guidance for operations like uploads/downloads.	2 / 3
Progressive Disclosure	Excellent structure with a concise overview in the main file and well-signaled one-level-deep references to SDK guides by language and service, plus links to external Microsoft documentation for deep dives. Navigation is clear and organized.	3 / 3
	Total	10 / 12 Passed

Description

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 well. It provides specific capabilities, comprehensive trigger terms, explicit 'USE FOR' and 'DO NOT USE FOR' clauses, and clear differentiation from related Azure skills. The description uses proper third-person voice throughout and is both comprehensive and well-organized.

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 blob storage, file shares, queue storage, etc.) and 'when' via the explicit 'USE FOR' clause listing trigger scenarios. Additionally includes 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', '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 clear boundaries. The 'DO NOT USE FOR' clause explicitly differentiates from SQL databases, Cosmos DB, and messaging services (Event Hubs/Service Bus), even pointing to alternative skills. The focus on Azure Storage specifically creates a clear niche.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: d4563f6

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.