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

A well-structured, actionable reference for the Azure Blob Storage Rust SDK with concrete code examples and clear sections. It lacks workflow sequencing and validation checkpoints for destructive operations, and carries a small amount of vague filler.

Suggestions

Add an explicit validation step around the destructive 'Delete Blob' operation (e.g. confirm via get_properties or a guard) to satisfy the feedback-loop requirement.

Replace the vague 'When to Use' line with concrete trigger conditions or remove it since the description already covers usage.

Consider extracting the RBAC permissions and Reference Links tables into a bundled reference file to tighten the core SKILL.md body.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-scoped code blocks and tables, though the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') is vague filler.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready Rust snippets for upload, download, properties, delete, and container operations, with only placeholder values like '<account>' needing substitution.

4 / 5

Workflow Clarity

Operations are presented as individual reference snippets rather than a sequenced workflow, and the destructive 'Delete Blob' operation has no validation checkpoint or feedback loop, capping this dimension at 3.

3 / 5

Progressive Disclosure

The content is organized into clear, well-labeled sections (Installation, Authentication, Client Types, Core Operations, etc.) with external reference links, though no bundle files exist to split content further.

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.

A solid, mostly concise description that names the domain, lists concrete actions, and provides a 'Use for' clause. It would benefit from more explicit trigger phrasing and broader synonym coverage.

Suggestions

Add an explicit 'Use when...' trigger clause naming user phrases, e.g. 'Use when the user asks to upload, download, or manage blobs in Azure Storage from Rust.'

Include broader synonyms such as 'object storage' or 'Azure Storage' to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('uploading, downloading, and managing blobs and containers') but stops short of comprehensive coverage of blob/container lifecycle operations.

4 / 5

Completeness

It answers both 'what' (Azure Blob Storage SDK for Rust) and 'when' ('Use for uploading, downloading, and managing blobs and containers'), but the 'when' lacks explicit trigger phrases like 'when the user mentions...'.

4 / 5

Trigger Term Quality

It includes natural terms users would say ('Azure Blob Storage', 'blobs', 'containers', 'uploading', 'downloading', 'Rust') but misses common synonyms like 'object storage' or file extensions.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly defined (Azure Blob Storage, Rust-specific) with distinct triggers, making conflict with other skills minimal.

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.