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.

51

Quality

56%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The skill is highly actionable with copy-paste-ready code across the full operation surface, but it is a long monolithic reference with redundancy and no bundle-file separation, and destructive operations lack the validation checkpoints the rubric requires.

Suggestions

Move the 'TypeScript Types Reference' and the bulk SAS/error-detail material into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Add validation checkpoints around destructive operations (e.g. verify share exists and confirm before delete, check snapshot count before deleteSnapshots) to lift workflow clarity above the destructive-cap of 3.

Trim redundancy — consolidate the four near-identical upload variants and replace the vacuous 'When to Use' line with a concrete trigger statement.

DimensionReasoningScore

Conciseness

The body is code-dense and avoids re-explaining basics Claude knows, but it runs ~490 lines with redundancy (four auth methods, multiple upload variants) and a vacuous closing line ('This skill is applicable to execute the workflow or actions described in the overview.'), so it could be tightened — anchor 3.

3 / 5

Actionability

Examples are fully executable and copy-paste ready across authentication, share/directory/file CRUD, upload/download variants, SAS generation, and error handling, covering the common cases per anchor 5.

5 / 5

Workflow Clarity

Operations are organized by category but destructive actions (delete share with deleteSnapshots, delete file/directory) are shown without validation checkpoints, and the judging guideline caps workflow clarity at 3 for destructive/batch operations lacking validation.

3 / 5

Progressive Disclosure

Section headers give it clear structure, but with no bundle files present the entire API surface — including a pure import-list 'TypeScript Types Reference' — is inlined in SKILL.md with no one-level-deep references, fitting anchor 3 (content that should be separate is inline, references absent).

3 / 5

Total

14

/

20

Passed

Description

48%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 specific to its Azure niche and names the relevant SDK and protocol, but it lists no concrete actions and omits an explicit 'Use when…' trigger clause, leaving both specificity and completeness at the midpoint.

Suggestions

Enumerate concrete actions, e.g. 'Create and manage SMB file shares, directories, and files; upload, download, and copy files; generate SAS tokens'.

Add an explicit 'Use when…' clause naming natural triggers such as 'Use when working with Azure Files, SMB file shares, or @azure/storage-file-share'.

Include common synonyms/extension cues (e.g. 'Azure Files') to broaden trigger-term coverage toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain ("Azure File Share", "SMB file share operations") and the SDK package, but the only action phrasing is the generic "file share operations" with no concrete actions enumerated, matching anchor 2.

2 / 5

Completeness

It clearly states what the skill covers (the SDK for SMB file share operations) but provides no "Use when…" trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("Azure File Share", "SMB file share", "@azure/storage-file-share") but misses common synonyms/variations such as "Azure Files", matching anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The Azure File Share / SMB niche and named package make it mostly distinct with only minor overlap risk against related Azure Blob storage skills, fitting anchor 4 rather than the fully-conflict-free anchor 5.

4 / 5

Total

12

/

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.