CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-storage-queue-ts

Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues.

Quality

83%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

An excellent executable reference: complete, correct, copy-paste-ready code with practical processing patterns and error handling. Its main weakness is structure — it is a monolithic single file with no progressive disclosure, inlining API-types and SAS reference material that should live in separate reference files.

Suggestions

Split the 'TypeScript Types Reference' and 'SAS Token Generation' sections into a references/ file (e.g., references/api.md), keeping SKILL.md to auth, core message operations, and the processing patterns.

Convert the implicit delete-on-success checkpoints in the worker patterns into explicit validation steps (e.g., 'verify processing succeeded before deleteMessage; on failure, rely on visibility timeout or extend it').

Remove the time-sensitive 'Current Version: 12.x' line or move version guidance into a clearly marked section so it does not silently go stale.

DimensionReasoningScore

Conciseness

The body is almost entirely lean, executable code with terse SDK-specific comments and no padding of concepts Claude already knows, though the full "TypeScript Types Reference" import listing and the time-sensitive "Current Version: 12.x" line could be trimmed or moved.

4 / 5

Actionability

Copy-paste-ready TypeScript covers all four authentication methods, every message and queue operation, worker/poison/batch processing patterns, RestError status-code handling, and a limits table — fully executable across the common cases.

5 / 5

Workflow Clarity

The worker, poison-message, and batch patterns sequence receive → process → delete with try/catch and dequeueCount guards around the destructive delete path, but checkpoints are implicit rather than explicit validation steps (no verify-before-delete or re-validation loop).

4 / 5

Progressive Disclosure

No bundle files exist; all 528 lines — including the TypeScript types listing and SAS-generation detail that clearly belong in a references file — are inlined in a single monolithic SKILL.md with headers but no external structure.

3 / 5

Total

16

/

20

Passed

Description

83%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 strong description: it names the precise SDK, states concrete capabilities, and includes an explicit usage-trigger clause. The only gaps are a few missing natural trigger synonyms and minor overlap risk with other Azure messaging services.

DimensionReasoningScore

Specificity

Names the exact SDK and four concrete actions ("sending, receiving, peeking, and deleting messages") with only minor gaps — queue-level create/list/delete and SAS operations from the body are omitted, keeping it just below comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ("SDK... for message queue operations") and when ("Use for sending, receiving, peeking, and deleting messages in queues") with concrete trigger phrases tied to specific operations.

5 / 5

Trigger Term Quality

"Azure Queue Storage", "@azure/storage-queue", "message queue", and "JavaScript/TypeScript" are natural user phrasings with good keyword coverage, but common variations like "enqueue/dequeue" or "Azure queue messages" are missing.

4 / 5

Distinctiveness Conflict Risk

The exact package name gives a clear niche, but the generic queue-messaging phrasing ("sending, receiving... messages in queues") creates minor overlap risk with closely related Azure messaging skills such as Service Bus.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (529 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/azure-storage-queue-ts/SKILL.md

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.