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.

50

Quality

55%

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

61%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 comprehensive executable snippets and clear client-hierarchy framing, but it is an oversized monolithic reference wall that inlines material better split into separate files and lacks validation/feedback steps around its destructive and copy operations. Splitting reference material into bundle files and adding verify-checkpoints would lift the two weakest dimensions.

Suggestions

Move the bulk API catalog and the TypeScript types reference into separate files under references/ (e.g. REFERENCE.md, TYPES.md) and link to them from a concise overview, keeping only quick-start examples inline.

Add explicit validation/checkpoint steps for destructive operations — e.g. verify a share exists and check for dependent snapshots before `shareClient.delete({ deleteSnapshots: 'include' })`, and confirm copy status via `pollUntilDone` before treating a copied file as ready.

Trim repeated import and client-construction boilerplate across snippets (a single setup block referenced once) to reduce token cost without losing actionability.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference code with minimal prose padding, but it is ~490 lines of inline API catalog (every operation with a full snippet) that repeats import/client-setup patterns many times, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Nearly every section gives complete, copy-paste-ready TypeScript snippets with real method calls and parameters covering common cases (auth, CRUD, upload/download variants, SAS, error handling), matching 'Fully executable; copy-paste ready code covering common cases'.

5 / 5

Workflow Clarity

Operations are grouped by client level and listed logically, but destructive/batch operations (delete share, delete with snapshots, clearRange, startCopy polling) have no validation checkpoints or feedback loops, so per the feedback-loops cap such skills cannot exceed 3.

3 / 5

Progressive Disclosure

There are no bundle files (references/scripts/assets all absent) yet ~490 lines of API reference, a full TypeScript types block, and a platform-diff table are all inlined in SKILL.md — content that clearly belongs in separate reference files — fitting 'content that clearly belongs in separate files is inlined'.

2 / 5

Total

13

/

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 correctly names the SDK and domain in third person and is reasonably distinct, but it states only a generic 'operations' rather than concrete actions and omits any explicit 'Use when...' trigger guidance. Adding concrete capabilities and a trigger clause would lift specificity and completeness.

Suggestions

Replace the generic 'operations' with 2-3 concrete capabilities (e.g., 'create and manage SMB shares, directories, and files; upload/download with ranges; generate SAS tokens').

Add an explicit trigger clause, e.g., 'Use when working with Azure File Shares, SMB shares, or the @azure/storage-file-share SDK.'

Include natural synonyms/extensions users might say (e.g., 'Azure Files', 'file share', '.txt uploads') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the SDK and domain ('Azure File Share JavaScript/TypeScript SDK... for SMB file share operations') but lists no concrete actions beyond a generic 'operations', matching the 'Names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It states a clear 'what' (SDK for SMB file share operations) but provides no 'Use when...' / 'when should Claude use it' guidance, so per the boundary guidance a missing explicit trigger clause caps completeness at 3 ('clear what but when missing').

3 / 5

Trigger Term Quality

It surfaces natural terms users say ('Azure File Share', 'SMB file shares', 'file operations') plus the package name, but misses common synonyms and the extension/file-type signals a user might verbalize, fitting 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The Azure File Share / SMB niche plus the specific package '@azure/storage-file-share' is clearly distinguishable from other storage skills with only minor overlap risk with sibling Azure storage SDKs, fitting 'Mostly distinct; minor overlap risk'.

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.