CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

70%

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-claude/skills/azure-storage-queue-ts/SKILL.md

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

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

Highly actionable with comprehensive copy-paste code, but presented as a ~520-line monolithic reference with no bundle files and no validation feedback loops in its batch/destructive workflows. Splitting reference material into separate files and adding verify-then-proceed checkpoints would materially raise the weaker dimensions.

Suggestions

Move the TypeScript Types Reference, SAS token generation, and the four authentication methods into separate files under references/ and link to them from SKILL.md, keeping only a quick-start overview inline to improve progressive_disclosure and conciseness.

Add explicit validation feedback loops to the worker and batch patterns (e.g., verify the processed result before deleteMessage, and a validate->fix->retry note) so the batch/destructive workflows can score above the workflow_clarity cap of 3.

Trim redundant inline detail such as repeated client construction and the full enumerated type list to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly actionable code, but at ~520 lines it inlines a full type reference, four auth methods, and SAS generation that could be tightened or offloaded, fitting the mostly-efficient-but-could-be-tightened anchor 3.

3 / 5

Actionability

Provides copy-paste-ready TypeScript across installation, auth, queue/message operations, processing patterns, and error handling, with concrete examples covering the common cases as in anchor 5.

5 / 5

Workflow Clarity

Worker, poison-message, and visibility-extension patterns are clearly sequenced with try/catch recovery, but batch/destructive message operations lack explicit validate-then-proceed feedback loops, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the entire SDK reference, type listing, and SAS material is inlined into SKILL.md with zero external references, matching the content-clearly-belongs-in-separate-files-is-inlined anchor 2.

2 / 5

Total

13

/

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 clear, third-person description that names the SDK, its domain, and four concrete operations with an explicit Use-for trigger. It is strong but leaves minor gaps in action coverage and natural-term synonyms that keep it just below the top anchors.

DimensionReasoningScore

Specificity

Names the domain and lists four concrete actions ("sending, receiving, peeking, and deleting messages"), but omits queue-management and update/clear operations, leaving minor gaps versus the comprehensive anchor 5.

4 / 5

Completeness

Clearly states what the skill does and provides an explicit "Use for sending, receiving, peeking, and deleting messages" clause, but the when is action-based rather than user-mention-based, so it falls just short of the explicit trigger phrases at anchor 5.

4 / 5

Trigger Term Quality

Includes natural terms ("Azure Queue Storage", "message queue", "queues") plus the package name @azure/storage-queue, but lacks synonyms a user might say and is file-extension-free since queues are not file-based.

4 / 5

Distinctiveness Conflict Risk

The explicit Azure Queue Storage niche and @azure/storage-queue package name give it distinct triggers with minimal conflict risk against other skills.

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

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