CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

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

72%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 thorough, highly actionable API reference with executable TypeScript for the full blob/container lifecycle. Its weaknesses are the lack of validation feedback loops around destructive operations and a monolithic structure that inlines material which could be progressively disclosed into separate files.

Suggestions

Add explicit validation checkpoints before destructive calls (e.g., confirm container exists / list blobs before delete) and a validate-then-proceed loop, so destructive workflows are not executed blindly.

Move the SAS generation, blob-type, and TypeScript Types Reference sections into separate files (e.g. references/sas.md, references/types.md) and link to them from the overview to improve progressive disclosure.

Remove or relocate the "Current Version: 12.x" note into a versioning/deprecation section so time-sensitive information does not penalize conciseness.

DimensionReasoningScore

Conciseness

Dense, mostly executable TypeScript with minimal prose padding and no over-explanation of concepts Claude knows; a "Current Version: 12.x" line and the long import reference block are the main trimmable bits keeping it off a 5.

4 / 5

Actionability

Fully executable, copy-paste-ready code across upload, download, list, delete, copy, SAS generation, properties/metadata, and error handling, with concrete examples covering the common cases.

5 / 5

Workflow Clarity

The skill is a reference catalog rather than a sequenced process, and destructive operations (container/blob delete, delete-with-snapshots) lack validation checkpoints or validate-then-proceed feedback loops, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist; everything lives in one ~480-line SKILL.md that is well-sectioned but inlines a large API reference (SAS generation, blob-type details, type reference) that could be split into separate reference files.

3 / 5

Total

15

/

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 specific, well-targeted description that names the SDK and its core operations with an explicit "Use for" trigger clause. It distinguishes itself clearly from other storage skills while remaining concise.

DimensionReasoningScore

Specificity

Lists several concrete actions — "uploading, downloading, listing, and managing blobs and containers" — giving broad coverage, but omits specifics like SAS generation, copy, properties/metadata that the body covers, so it is not a full 5.

4 / 5

Completeness

Both "what" (SDK for blob operations) and "when" ("Use for uploading, downloading, listing, and managing...") are present and explicit; the when-clause lists activities rather than user-mention triggers, keeping it just below a 5.

4 / 5

Trigger Term Quality

Strong natural keywords ("Azure Blob Storage", "@azure/storage-blob", "blobs and containers", "blob operations") that users would actually say, though synonyms like "object storage" or "Azure storage" are missing.

4 / 5

Distinctiveness Conflict Risk

Names Azure Blob Storage and the @azure/storage-blob package specifically, carving a clear niche with distinct triggers and minimal overlap with non-Azure storage skills.

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.

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.