CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-storage-blob-java

Build blob storage applications using the Azure Storage Blob SDK for Java.

55

Quality

63%

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

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

The skill body is a highly actionable, lean code reference with strong section organization, but it lacks sequenced workflows with validation checkpoints for its destructive/batch operations and keeps a large API surface inlined rather than split into progressively disclosed reference files.

Suggestions

Add explicit validation/verification steps around destructive operations (e.g., confirm a blob exists or check deleteWithResponse status codes before proceeding) to lift workflow clarity above the cap.

Split the large API reference into one-level-deep reference files (e.g., references/upload.md, references/sas.md) and link them from the body so SKILL.md stays a concise overview.

Replace the generic 'When to Use' line with concrete trigger guidance, or remove it if the frontmatter description covers it.

DimensionReasoningScore

Conciseness

The body is dominated by lean, directly-usable code blocks with minimal prose and assumes Claude's competence; only minor trimmable fluff remains (e.g., the generic 'When to Use' line), placing it just below the top anchor.

4 / 5

Actionability

It provides copy-paste-ready, fully executable Java code covering the common cases (client creation, upload/download variants, list, delete, copy, SAS, lease, properties, error handling, proxy), matching the 'fully executable; covers common cases' anchor.

5 / 5

Workflow Clarity

The content is a pattern catalog rather than a sequenced workflow, and destructive operations (delete, delete with snapshots) and batch operations (list blobs) appear without validation/verification steps, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but ~390 lines of API reference are inlined in a single file with no external references or bundle files; content that could be split into separate reference files stays inline, fitting the 'some structure but could be better organized' anchor.

3 / 5

Total

15

/

20

Passed

Description

53%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 a clear niche but generic in its action language and lacks any 'Use when' trigger guidance. It would benefit from naming concrete operations and adding explicit trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming the scenarios that should trigger this skill (e.g., 'Use when uploading, downloading, or managing blobs in Azure Storage from Java').

Replace the generic verb 'Build blob storage applications' with several concrete operations (upload, download, list, lease, generate SAS tokens).

Include natural trigger synonyms and file/extension hints users would actually say (e.g., 'Azure Blob', 'blob Java SDK', 'block blob').

DimensionReasoningScore

Specificity

The description names the domain ('Azure Storage Blob SDK for Java') and one action ('Build blob storage applications'), but the action is generic and not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

It states a clear 'what' (build blob storage applications with the SDK) but provides no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant technical keywords ('blob storage', 'Azure Storage Blob SDK', 'Java') but misses natural synonyms, file extensions, and common phrasings users might say, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The phrase 'Azure Storage Blob SDK for Java' targets a clear, narrow niche with minimal conflict risk, though it could marginally overlap with other Azure SDK skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

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.