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

71

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 users would naturally use, explicit 'USE FOR' and 'DO NOT USE FOR' clauses that clearly delineate scope, and distinct boundaries that prevent conflicts with related Azure skills. The description uses proper third-person voice throughout.

DimensionReasoningScore

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 sub-services and capabilities) and 'when' (explicit 'USE FOR' clause with trigger terms, plus a 'DO NOT USE FOR' clause that further clarifies boundaries). The explicit trigger guidance is comprehensive.

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 clear boundaries. The 'DO NOT USE FOR' clause explicitly excludes SQL databases, Cosmos DB, Event Hubs, and Service Bus, even pointing to alternative skills. This makes it very unlikely to conflict with related Azure 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 Azure Storage reference skill that makes good use of tables for quick lookup and provides concrete CLI commands and MCP tool references. Its main weaknesses are minor redundancy between the SDK sections and the lack of workflow sequencing for common multi-step operations like setting up storage from scratch. Overall it serves well as a quick-reference skill with good progressive disclosure 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.

Consider adding a brief common workflow sequence (e.g., create account -> create container -> upload blob) to improve workflow clarity for users performing end-to-end operations.

DimensionReasoningScore

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 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 direct references to SDK guides per language. Fully actionable for the tasks described.

3 / 3

Workflow Clarity

The skill is primarily a reference/lookup skill rather than a multi-step workflow, so explicit validation steps are less critical. However, there's no guidance on sequencing operations (e.g., create account -> create container -> upload blob), and no error handling or validation mentioned for any operations. For a reference skill this is acceptable but not exemplary.

2 / 3

Progressive Disclosure

Excellent structure with a concise overview in the main file and well-signaled one-level-deep references to SDK guides per language, external Microsoft documentation, and an SDK usage guide. Navigation is clear and organized by service type 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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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.