CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-storage-file-share-ts

Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations.

47

Quality

50%

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 ./skills/azure-storage-file-share-ts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Scale 1-5

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

This skill is a thorough, highly actionable API reference for @azure/storage-file-share with excellent executable code examples covering all major operations. However, it suffers from being a monolithic document that would benefit from splitting into a concise overview plus separate reference files, and it lacks workflow sequencing and validation checkpoints for multi-step operations like file uploads or snapshot-based recovery.

Suggestions

Split the monolithic file into a concise SKILL.md overview (auth + core patterns + client hierarchy) with references to separate files like OPERATIONS.md, SAS.md, and TYPES.md

Add explicit workflow sequences with validation for multi-step operations, e.g., the upload flow (create → uploadRange → verify with getProperties) and the snapshot-before-modify pattern

Consolidate the four authentication methods into one primary example plus a brief table listing alternatives, rather than fully spelling out all four

Remove the 'When to Use' section (adds no value) and trim 'Best Practices' to only non-obvious guidance

DimensionReasoningScore

Conciseness

The skill is largely a comprehensive API reference with executable examples, which is useful, but it's quite long (~400 lines) and includes some content Claude would already know (e.g., basic streaming patterns, what connection strings are). The four authentication methods are all fully spelled out when a table + one example would suffice. The 'Best Practices' and 'When to Use' sections add little value for Claude.

3 / 5

Actionability

Nearly every section provides copy-paste ready TypeScript code covering common operations: authentication, CRUD for shares/directories/files, uploads via multiple methods, downloads, SAS generation, error handling, and range operations. The code is executable and complete with proper imports.

5 / 5

Workflow Clarity

The skill is primarily an API reference rather than a workflow guide. File upload requires a two-step process (create then uploadRange) which is shown but not explicitly called out as a required sequence. There are no validation checkpoints, no feedback loops for error recovery in multi-step operations like copy or snapshot-then-modify workflows. The error handling section exists but isn't integrated into workflows.

3 / 5

Progressive Disclosure

This is a monolithic ~400-line file with no references to external files and no bundle structure. The extensive API reference content (type imports, SAS generation, range operations, snapshot operations) would be better split into separate reference files, with the SKILL.md serving as a concise overview pointing to them. Everything is inlined in one large document.

2 / 5

Total

13

/

20

Passed

Description

39%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 identifies a clear technology niche (Azure File Share SDK) with the specific package name, which aids distinctiveness. However, it lacks concrete actions (what operations it performs) and completely omits 'when to use' guidance, making it difficult for Claude to confidently select this skill from a large pool. The description reads more like a library label than a functional skill description.

Suggestions

Add concrete actions such as 'create/delete file shares, upload/download files, list directories, manage permissions, set quotas'.

Add a 'Use when...' clause with trigger terms like 'Azure file share', 'SMB share', 'cloud file storage', '@azure/storage-file-share', 'mount share'.

Include natural user phrases and synonyms such as 'network file share', 'shared drive', 'Azure Files' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Azure File Share SDK) and mentions 'SMB file share operations' but provides no concrete actions like uploading, downloading, listing, creating shares, etc. The phrase 'operations' is generic.

2 / 5

Completeness

Provides a vague 'what' (SDK for SMB file share operations) but has no 'when' clause at all. The absence of explicit trigger guidance caps this at 3 per the rubric, and the weak 'what' brings it down to 2.

2 / 5

Trigger Term Quality

Includes relevant keywords like 'Azure File Share', 'JavaScript/TypeScript', '@azure/storage-file-share', and 'SMB', but misses natural user phrases like 'upload files', 'download files', 'create share', 'list directories', or 'cloud storage'.

3 / 5

Distinctiveness Conflict Risk

The specific mention of '@azure/storage-file-share' package name and 'SMB file share' makes it fairly distinct from other Azure storage skills (blob, queue, table) or general file operation skills. Minor overlap risk with broader Azure storage skills.

4 / 5

Total

11

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.