azure-storage
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics capabilities. Includes access tiers (hot, cool, archive) and lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, lifecycle management. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-storage95
Does it follow best practices?
Evaluation — 99%
↑ 1.08xAgent success when using this skill
Validation for skill structure
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 a well-crafted skill description that excels across all dimensions. It provides comprehensive coverage of Azure Storage capabilities with specific actions, includes natural trigger terms users would actually say, and explicitly defines both when to use and when NOT to use this skill with references to alternative skills. The 'USE FOR' and 'DO NOT USE FOR' structure is particularly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: 'object storage, SMB file shares, async messaging, NoSQL key-value, big data analytics, access tiers, lifecycle management, upload files, download blobs, storage accounts'. | 3 / 3 |
Completeness | Clearly answers both what (Azure Storage Services with specific capabilities) and when with explicit 'USE FOR:' and 'DO NOT USE FOR:' clauses that provide clear trigger guidance and disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, lifecycle management' - these are terms users would naturally use when working with Azure storage. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills with 'DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging)' - this clear boundary-setting minimizes conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 efficiently presents Azure Storage services with excellent use of tables for quick lookup and clear MCP/CLI command references. The progressive disclosure is exemplary with organized links to SDK guides. The main weakness is the lack of explicit multi-step workflows with validation checkpoints for common operations like bulk uploads or tier migrations.
Suggestions
Add a workflow section showing a complete multi-step process (e.g., 'Upload files with verification: 1. List existing blobs, 2. Upload, 3. Verify upload succeeded, 4. Set access tier')
Include validation commands to verify operations completed successfully (e.g., checking blob exists after upload, verifying tier change)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands and specific MCP tool commands with exact parameters. The examples are executable and complete. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no explicit workflow for multi-step operations like uploading multiple files or managing lifecycle policies. Missing validation steps for operations that could fail. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview tables, well-signaled one-level-deep references to SDK guides and external documentation. Content is appropriately split between quick reference and detailed materials. | 3 / 3 |
Total | 11 / 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.
- 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.