CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-keyvault-secrets-rust

Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys. Triggers: "keyvault secrets rust", "SecretClient rust", "get secret rust", "set secret rust".

65

Quality

79%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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, well-organized reference with copy-paste code for every operation. It loses points on workflow clarity (no validation around the destructive delete) and has minor conciseness blemishes from a filler closing section.

Suggestions

Add a validation/verification checkpoint around delete_secret (e.g., confirm the secret is gone via list before proceeding) to satisfy the destructive-operation feedback-loop requirement.

Replace the generic 'When to Use' filler with concrete guidance on when this skill applies versus alternatives, or remove it entirely to tighten conciseness.

Consider moving the per-operation code into a references file and keeping SKILL.md as a tighter overview with one-level-deep links to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable code and minimal prose, assuming Claude's competence; the only padding is the generic 'When to Use' filler line ('applicable to execute the workflow or actions described in the overview') that earns no information.

4 / 5

Actionability

Copy-paste-ready Rust snippets cover installation, auth, and every core operation (get, set, update, delete, list, versioned get) with imports shown per example, fully covering the common cases.

5 / 5

Workflow Clarity

Content is organized as a logical install-configure-auth-use sequence, but there are no validation checkpoints, and the destructive delete_secret operation has no verify step, which caps workflow clarity at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

Well-structured with clear section headers and an explicit external reference-links table; no bundle files exist so all content is inline, but it is appropriately sized and organized with only minor gaps (the filler 'When to Use' section).

4 / 5

Total

16

/

20

Passed

Description

82%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, third-person description with explicit trigger guidance and a clear, distinct niche. Its only weak spot is specificity, which names just two of the supported operations rather than the full CRUD surface.

Suggestions

Expand the capability list to mention listing, updating, and deleting secrets alongside storing and retrieving to lift specificity.

Add a couple of natural trigger variants (e.g. 'azure key vault rust', 'list secrets rust') to round out trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure Key Vault Secrets SDK for Rust') and two concrete actions ('storing and retrieving secrets'), but does not enumerate the broader CRUD coverage (list, update, delete) shown in the body, so it stops at 1-2 actions rather than comprehensive.

3 / 5

Completeness

Clearly states what ('Azure Key Vault Secrets SDK for Rust' storing/retrieving secrets) and provides explicit when guidance via both a 'Use for' clause and concrete 'Triggers:' phrases, matching the anchor that requires concrete trigger phrases.

5 / 5

Trigger Term Quality

Four natural trigger phrases ('keyvault secrets rust', 'SecretClient rust', 'get secret rust', 'set secret rust') give good keyword coverage a user would actually say, though common variants like 'list secrets rust' or 'azure key vault rust' are missing.

4 / 5

Distinctiveness Conflict Risk

The triple niche of Azure Key Vault + Secrets + Rust with operation-specific trigger phrases is highly distinct and unlikely to fire for 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.