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/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 well-structured, highly actionable reference skill with executable code for every common operation. Its main weakness is the absence of validation/verification checkpoints around destructive and batch operations, which caps workflow clarity.

Suggestions

Add validation checkpoints before destructive operations (e.g., confirm the secret name exists, verify retention/recovery window before delete_secret) and a verify-after step for list/update flows.

Remove or replace the generic "When to Use" filler with a concrete statement of when this skill applies versus alternatives.

Consider moving the full per-operation API detail or advanced scenarios into a one-level-deep reference file to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean with minimal prose and mostly executable code, but the generic "When to Use" filler line ("This skill is applicable to execute the workflow or actions described in the overview.") is mild padding that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready Rust snippets with real types (SecretClient, SetSecretParameters, SecretClientGetSecretOptions, ResourceExt), a real install command, and coverage of get/set/update/delete/list/version operations.

5 / 5

Workflow Clarity

Operations are listed but destructive and batch actions (delete_secret, list_secrets, update) lack validation or verification checkpoints, and the rubric caps workflow_clarity at 3 for destructive/batch skills without validation.

3 / 5

Progressive Disclosure

Well-organized single-file reference with clear section headers and a clean external-links table, but all operational detail is inline with no one-level-deep reference files for advanced material.

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.

The description is specific, distinct, and complete with both a clear purpose and explicit trigger guidance. Trigger terms are good but slightly jargon-heavy and missing synonym/extension coverage.

Suggestions

Broaden the action list in the description to mention listing, deleting, and versioning secrets for fuller capability coverage.

Add more natural, non-jargon trigger phrases (e.g., "azure secrets", "list keyvault secrets") and any relevant file-type or CLI terms to improve trigger_term_quality.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("storing and retrieving secrets, passwords, and API keys") but omits other operations like deleting, listing, and versioning, so coverage is not comprehensive.

3 / 5

Completeness

Clearly states what the skill does ("Azure Key Vault Secrets SDK for Rust... storing and retrieving secrets") and when to use it via an explicit "Use for" clause plus concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes an explicit "Triggers:" clause with several natural phrases ("keyvault secrets rust", "get secret rust", "set secret rust"), though it leans on SDK jargon ("SecretClient rust") and lacks synonyms or file extensions.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (Azure Key Vault Secrets in Rust) with Rust-specific triggers, making conflict with other skills unlikely.

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.