CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-keyvault-keys-rust

Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys. Triggers: "keyvault keys rust", "KeyClient rust", "create key rust", "encrypt rust", "sign rust".

58

Quality

68%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 mostly executable, well-organized reference for Key Vault key operations that stumbles on its cryptographic-operations section (advertised in the triggers but shown only as comments) and lacks validation around destructive ops.

Suggestions

Replace the comment-only Cryptographic Operations section with real executable encrypt/decrypt and sign/verify code, since 'encrypt rust' and 'sign rust' are headline triggers.

Add a validation or confirmation checkpoint before delete_key (e.g., back up first, confirm the key is not in use) to satisfy the destructive-operation workflow requirement.

Remove or replace the vacuous 'When to Use' boilerplate with concrete guidance on when this skill applies versus other Azure SDK skills.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable code with minimal prose, though the 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview.') is vapid filler that could be trimmed.

4 / 5

Actionability

Seven of eight operations ship complete copy-paste Rust, but the Cryptographic Operations section — covering headline triggers encrypt and sign — is comment-only with no executable code, leaving key details missing.

3 / 5

Workflow Clarity

Operations are individually clear but presented as an unsequenced reference rather than a workflow, and the destructive delete_key has no validation or confirmation checkpoint, capping this dimension at 3.

3 / 5

Progressive Disclosure

The skill is a well-sectioned single file over 50 lines with no bundle files or one-level-deep references; everything is inline, so structure is present but content that could be split out is not.

3 / 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, well-structured description that explicitly answers both what and when with concrete trigger phrases. Its main weakness is generic action verbs where specific cryptographic operations would be more precise.

DimensionReasoningScore

Specificity

Names the domain ('Azure Key Vault Keys SDK for Rust') and three actions ('creating, managing, and using cryptographic keys'), but the verbs are generic and not the concrete operations (encrypt, sign, rotate) a comprehensive description would list.

3 / 5

Completeness

Clearly states what the skill does and provides an explicit 'when' via concrete trigger phrases ('Use for... Triggers: ...'), matching the anchor that requires both what and when with triggers.

5 / 5

Trigger Term Quality

Five explicit natural triggers ('keyvault keys rust', 'KeyClient rust', 'create key rust', 'encrypt rust', 'sign rust') give good keyword coverage, though common synonyms like decrypt, rotate, and HSM are missing.

4 / 5

Distinctiveness Conflict Risk

The Rust + Key Vault Keys niche and 'KeyClient rust' trigger are clearly distinct, with only minor overlap risk against sibling Azure Key Vault Secrets/Certificates SDK skills.

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