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

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured reference with concrete executable CLI and MCP guidance and clean progressive disclosure to verified per-language SDK docs. Minor conciseness loss from a duplicate SDK paragraph and the lack of explicit verification checkpoints in the fallback workflow.

Suggestions

Remove or merge the trailing '## Azure SDKs' section with '## SDK Quick References' since both point to sdk-usage.md and partially repeat each other.

Add a verification step after upload/download (e.g., 'az storage blob list' or a blob exists check) to give the workflow an explicit validation checkpoint.

Either reference the existing references/auth-best-practices.md from the body or note why it is kept, so no bundle file is orphaned from the skill's navigation.

Dimension	Reasoning	Score
Conciseness	Dense scannable tables and no concept over-explanation, but the closing '## Azure SDKs' paragraph repeats the SDK Quick References pointer to sdk-usage.md and the MCP tool list overlaps conceptually with the CLI fallback.	4 / 5
Actionability	Provides copy-paste ready CLI commands with real placeholders ('az storage blob download --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH') and concrete MCP tool/command pairs, covering the common cases across both access paths.	5 / 5
Workflow Clarity	Clear precedence chain (MCP preferred -> /azure:setup if not enabled -> CLI fallback), but no explicit validation or verification steps for upload/download operations; not a destructive/batch skill so the workflow_clarity-3 cap does not apply.	4 / 5
Progressive Disclosure	SKILL.md is an overview with well-signaled one-level-deep references to verified-real bundle files split by language under references/sdk/, with easy navigation and content appropriately separated from the body.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it concretely lists five storage services and capabilities, provides comprehensive natural trigger terms, answers both what and when explicitly, and sets clear boundaries against sibling skills. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists all five Azure Storage services plus concrete capabilities ('object storage, SMB file shares, async messaging, NoSQL key-value, big data analytics') and lifecycle management, giving comprehensive coverage rather than minor gaps.	5 / 5
Completeness	Explicitly answers what ('Azure Storage Services including...') and when with concrete trigger phrases ('USE FOR:', 'DO NOT USE FOR:'), both clearly and explicitly stated.	5 / 5
Trigger Term Quality	The 'USE FOR' clause provides extensive natural terms including synonyms ('access tiers'/'storage tiers', 'hot cool cold archive') and user actions ('upload files, download blobs'), matching comprehensive coverage of natural terms.	5 / 5
Distinctiveness Conflict Risk	Has a clear Azure Storage niche with explicit boundaries excluding adjacent skills ('DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging)'), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 11 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 11 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/azure-storage/SKILL.md
Commit: 16dc8c5

Reviewed: about 13 hours 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.