CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-storage-blob-ts

Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers.

Quality

76%

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-blob-ts/SKILL.md

The canonical home for this skill is azure-storage-blob-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.

A highly actionable, well-organized SDK reference whose code examples are copy-paste ready and cover the common cases. Its weaknesses are inlined reference material that should live in separate files, filler sections that waste tokens, and missing validation guidance around destructive delete operations.

Suggestions

Split reference-heavy sections (SAS token generation, TypeScript types list, platform differences table) into files under references/ and link to them from SKILL.md, keeping the main file to quick-start and common operations.

Add validation guidance before destructive operations, e.g., verify a container is empty or list blobs and confirm before delete(), and use deleteIfExists() in examples instead of bare delete().

Remove the filler "When to Use" section and the bare "TypeScript Types Reference" import list; if type names matter, mention them inline where each operation is demonstrated.

DimensionReasoningScore

Conciseness

The body is code-dense and mostly lean, but includes unnecessary padding: the closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview") is filler, the "TypeScript Types Reference" is just an import list, and "Current Version: 12.x" is time-sensitive information not placed in a deprecated/old-patterns section.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance: an install command, four complete authentication patterns, and concrete TypeScript for every common operation (upload, download, list, delete, copy, properties, SAS generation, error handling), with platform-specific methods clearly flagged.

5 / 5

Workflow Clarity

Well-sequenced single-purpose reference (install → auth → operations) with error handling and idempotent variants (deleteIfExists, createIfNotExists), but destructive operations (container/blob delete, delete with snapshots) have no validate-before-delete or verification guidance, capping this dimension at 3.

3 / 5

Progressive Disclosure

No bundle files exist; all ~480 lines are inlined in SKILL.md. Section headers make it navigable, but content that clearly belongs in separate reference files (SAS token generation, the types import reference, platform differences table) is inlined rather than split out.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description that names a specific SDK, lists concrete operations, and provides an explicit 'Use for' trigger clause. Its only weaknesses are a generic "managing" verb, missing synonyms/context variations, and a 'when' clause that restates the 'what' rather than adding user-context triggers.

DimensionReasoningScore

Specificity

Names the domain and lists concrete actions ("uploading, downloading, listing, and managing blobs and containers"), but "managing" is generic and operations like SAS generation, metadata, and copy are not mentioned, leaving minor gaps in coverage.

4 / 5

Completeness

Clearly states what the SDK does and includes an explicit "Use for uploading, downloading, listing, and managing blobs and containers" trigger clause with concrete operations, though the 'when' mirrors the 'what' without adding distinct situational triggers (e.g., 'when the user mentions Azure Storage').

4 / 5

Trigger Term Quality

"Azure Blob Storage", "@azure/storage-blob", "blobs", "containers", and "uploading/downloading/listing" are natural terms users would say, though common variations like "Node.js", "cloud storage", or "Azure Storage account" are missing.

4 / 5

Distinctiveness Conflict Risk

"Azure Blob Storage" plus the "@azure/storage-blob" package name pins a clear niche with distinct triggers; minimal risk of triggering for the wrong skill.

5 / 5

Total

17

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/azure-storage-blob-ts/SKILL.md

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.