CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-storage-queue-py

Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-storage-queue-py/SKILL.md

The canonical home for this skill is azure-storage-queue-py 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 highly actionable, concise reference with excellent executable coverage of the SDK's common operations. Its main weaknesses are the absence of validation checkpoints for destructive/batch operations and a monolithic inline structure with no external references for a skill of this length.

Suggestions

Add explicit validation before destructive/batch operations, e.g. confirm the queue name and approximate message count before clear_messages or delete_queue.

Move advanced material (async client, base64 encoding, full property/metadata reference) into one-level-deep reference files with clear links from the overview.

De-duplicate the repeated receive_messages blocks by referencing a single receive pattern.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable code with brief, useful inline comments and no over-explanation of basic concepts, though a little redundancy (receive_messages repeated across sections) and the fluff intro line could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready Python covering the common cases (send, receive, peek, update, delete, clear, properties, async, base64) with real SDK method names and parameters.

5 / 5

Workflow Clarity

Operations are individually clear and the delete pattern shows try/except recovery, but destructive/batch operations (clear_messages, delete_queue) lack explicit validation checkpoints, which caps workflow clarity per the rubric.

3 / 5

Progressive Disclosure

Content is well-organized into clear section headers but is entirely inline in a ~207-line SKILL.md with no bundle files; material such as the async client and base64 encoding that could live in one-level-deep references is inlined rather than split out.

3 / 5

Total

15

/

20

Passed

Description

73%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 clear, distinct description that identifies both the domain and trigger use-cases, but the capability phrasing is somewhat generic and the 'when' guidance lacks explicit user-mention trigger framing. It is solid but stops short of the top anchor on specificity and completeness.

Suggestions

Replace generic use-case labels with concrete SDK actions, e.g. 'Send, receive, peek, update, and delete queue messages'.

Add an explicit user-mention trigger clause, e.g. 'Use when the user asks about Azure Queue Storage, message queues, or task distribution in Python'.

Include natural synonyms such as 'Azure Queue' and 'queue messages' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Azure Queue Storage SDK for Python') and lists capability categories ('reliable message queuing, task distribution, and asynchronous processing'), but these are generic use-case labels rather than concrete SDK actions like send/receive/peek, so it is not comprehensive.

3 / 5

Completeness

It answers both 'what' (Azure Queue Storage SDK for Python) and 'when' ('Use for reliable message queuing, task distribution, and asynchronous processing'), but the 'when' is framed as use-cases rather than explicit user-mention trigger phrases, so it could be more explicit.

4 / 5

Trigger Term Quality

It includes natural terms a user would say ('Azure Queue Storage', 'message queuing', 'task distribution', 'asynchronous processing', 'Python') with good coverage, though it misses common synonyms like 'Azure Queue' or 'queue messages'.

4 / 5

Distinctiveness Conflict Risk

The description targets a specific Azure service and language ('Azure Queue Storage SDK for Python'), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.