CtrlK
BlogDocsLog inGet started
Tessl Logo

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

73

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A concise, action-oriented overview with executable CLI/MCP commands and well-structured one-level-deep references. Its main gap is the absence of validation/verification checkpoints for mutating operations like blob upload, which caps workflow clarity.

Suggestions

Add a verification step after uploads/mutations (e.g. re-list the container or check the returned ETag) to introduce a validate-fix-retry feedback loop for destructive/batch operations.

Clarify how to detect which MCP command actually ran versus when to fall back to CLI, so the MCP-vs-CLI sequence has an explicit decision checkpoint.

Consider noting the tier rehydration latency/minimum-days caveats inline or via a one-line reference, since the access-tier table omits the operational consequence of moving to Archive.

DimensionReasoningScore

Conciseness

The body is lean: tables and executable CLI snippets carry the information with no explanation of what Azure Storage is or how the SDK works. Not score 2 because there is no padded or unnecessary prose; every line is reference material.

3 / 3

Actionability

Provides concrete, copy-paste-ready CLI commands ('az storage blob upload --account-name ACCOUNT ...') and named MCP tools with exact command identifiers. Not score 2 because commands are complete and executable rather than pseudocode.

3 / 3

Workflow Clarity

MCP Server is marked '(Preferred)' with a CLI fallback and a clear enablement step, but there is no validation/verification checkpoint for batch or mutating operations (e.g. upload), so per the rubric feedback-loop guidance workflow clarity is capped at 2. Not score 1 because the MCP-vs-CLI sequence is explicit.

2 / 3

Progressive Disclosure

The body is an overview pointing one level deep to verified reference files (references/sdk/* and references/sdk-usage.md, all confirmed present) plus external docs, with clear per-language links. Not score 2 because navigation is well-signaled and content is appropriately split rather than inlined.

3 / 3

Total

11

/

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.

A high-quality, dense description that clearly states capabilities, includes rich natural trigger terms, and uses explicit USE FOR / DO NOT USE FOR boundaries to avoid skill conflicts. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities: 'object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics' and 'lifecycle management', naming the five storage services and their functions.

3 / 3

Completeness

Explicitly answers 'what' (the storage services and capabilities) and 'when' via both a 'USE FOR' trigger clause and a 'DO NOT USE FOR' exclusion clause, far exceeding the implicit-trigger threshold.

3 / 3

Trigger Term Quality

The 'USE FOR' clause densely covers natural terms a user would say ('upload files, download blobs, storage accounts, access tiers, hot cool cold archive') plus variants like 'storage tiers' and 'when to use storage tiers'.

3 / 3

Distinctiveness Conflict Risk

The 'DO NOT USE FOR' clause explicitly routes SQL databases, Cosmos DB, and Event Hubs/Service Bus to other skills (azure-prepare, azure-messaging), carving a clear niche with low conflict risk.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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