CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-storage-blob-rust

Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.

62

Quality

73%

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

The canonical home for this skill is azure-storage-blob-rust in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 content is well-structured and actionable, with concrete executable examples throughout. Its main weakness is the absence of validation/verification steps around destructive and batch blob operations, which holds workflow clarity down.

Suggestions

Add an explicit validation/checkpoint step to destructive flows — e.g., confirm a blob exists and verify identity before `blob_client.delete(...)`, and check for an empty/errored page when iterating `list_blobs`.

Replace the generic "When to Use" boilerplate with concrete trigger conditions, or remove it since the frontmatter description already covers usage.

Consider splitting the RBAC permissions and full API reference into a referenced file to lighten the body and deepen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean — short labeled code blocks, tables, and minimal prose — but the generic "When to Use" boilerplate ("This skill is applicable to execute the workflow or actions described in the overview") is a small trim opportunity.

4 / 5

Actionability

Concrete, mostly executable Rust snippets cover auth, upload, download, properties, delete, and container create/list with a real install command and env vars; gaps like `<account>` placeholders and an omitted tokio runtime keep it from being fully copy-paste ready.

4 / 5

Workflow Clarity

Operations are grouped and each is unambiguous, but destructive (delete blob) and batch (list blobs) flows lack explicit validation or verification checkpoints, which caps workflow clarity per the rubric.

3 / 5

Progressive Disclosure

Clean section headers and an external reference-links table give good one-level navigation, though at ~127 lines some inline material (RBAC details, full API examples) could be split into referenced files since no bundle files are provided.

4 / 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.

The description is concise, names a specific niche, and covers both what the skill does and when to use it. It is held below a perfect score by slightly limited action coverage and trigger-term breadth rather than any real defect.

DimensionReasoningScore

Specificity

"Use for uploading, downloading, and managing blobs and containers" lists several concrete actions covering the core surface, but coverage is not comprehensive (no listing, properties, leases, SAS).

4 / 5

Completeness

It answers both "what" (Azure Blob Storage SDK for Rust) and "when" ("Use for uploading, downloading, and managing blobs and containers"), though the when clause could be more explicit with varied trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "Azure Blob Storage", "blob", "container", "upload", "download", and "Rust" appear; a few natural synonyms or extensions ("Azure Storage", "object storage") are missing.

4 / 5

Distinctiveness Conflict Risk

"Azure Blob Storage SDK for Rust" carves a clear, narrow niche with distinct triggers and minimal risk of overlapping unrelated 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.