CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-storage-file-share-py

Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-storage-file-share-py/SKILL.md

The canonical home for this skill is azure-storage-file-share-py in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, code-dense SDK cheat-sheet that is highly actionable and well-structured. Its main gaps are the absence of validation checkpoints around destructive operations and a pointless filler 'When to Use' line.

Suggestions

Add a validation/confirmation step before destructive calls (e.g., verify the share exists and confirm with the user before delete_share).

Remove or replace the filler 'When to Use' line with concrete guidance on when to prefer File Share vs Blob storage.

Consider splitting the detailed API reference or async patterns into a references/ file to lighten the main SKILL.md.

DimensionReasoningScore

Conciseness

A lean, code-forward reference with minimal prose, but the closing 'When to Use' line ('applicable to execute the workflow or actions described in the overview') is filler that earns no token.

4 / 5

Actionability

Provides copy-paste-ready, executable snippets across shares, directories, files, ranges, snapshots, and async clients, covering the common cases.

5 / 5

Workflow Clarity

Organized as an API reference by operation type with no multi-step sequencing, and destructive operations (delete share/directory/file) lack validation or confirmation checkpoints, capping this dimension per the rubric.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a client-types table, though all content is inlined in a ~230-line SKILL.md with no external reference files for advanced material.

4 / 5

Total

16

/

20

Passed

Description

62%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 concise, third-person, and targets a clear niche, but it leans on generic 'operations' language and a domain-focused 'Use for' clause instead of explicit user-trigger phrases. Listing concrete actions and natural trigger synonyms would raise specificity, trigger quality, and completeness.

Suggestions

Replace generic 'file operations' with concrete verbs, e.g. 'create, upload, download, and delete SMB file shares, directories, and files'.

Add explicit user-trigger phrasing, e.g. 'Use when the user asks to manage Azure file shares or SMB shares in the cloud.'

Include common synonyms such as 'Azure file share' and 'SMB share' to improve natural trigger matching.

DimensionReasoningScore

Specificity

Names the domain (Azure File Share) and the share/directory/file areas, but relies on the generic term 'file operations' rather than concrete verbs like create, upload, or delete.

3 / 5

Completeness

States what ('Azure Storage File Share SDK for Python') and provides a 'Use for...' trigger clause, but the 'when' is domain-focused rather than tied to explicit user trigger phrases.

4 / 5

Trigger Term Quality

Includes 'SMB file shares', 'directories', and 'file operations' but misses common user phrasings such as 'Azure file share' or 'SMB share' and offers no synonyms or extensions.

3 / 5

Distinctiveness Conflict Risk

Anchored to a specific Azure service (SMB File Share), clearly distinct from most skills with only minor overlap risk against other Azure storage SDKs.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.