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".

63

Quality

75%

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-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

68%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, mostly executable SDK reference with concise code for the core key-management operations. The main gaps are the missing executable encrypt/sign examples and the absence of validation checkpoints around the destructive delete/restore operations.

Suggestions

Add a concrete, copy-paste Rust example for encrypt/decrypt or sign/verify in the Cryptographic Operations section, since 'encrypt' and 'sign' are headline triggers but currently only appear as comments.

Insert validation checkpoints around destructive operations, e.g. confirm the key exists / print key ID before delete_key, and verify the restored key name matches after restore_key.

Replace the filler 'When to Use' sentence with a concrete trigger-based usage statement (or remove it, since the frontmatter description already carries the triggers).

DimensionReasoningScore

Conciseness

The body is mostly lean code examples with little concept explanation, but the 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') is filler and the crypto section restates operations as comments rather than trimming.

4 / 5

Actionability

Most operations (get/create/create-EC/delete/list/backup/restore) ship copy-paste-ready Rust, but the Cryptographic Operations section only lists available ops as comments with no executable encrypt/sign example despite those being headline triggers.

4 / 5

Workflow Clarity

Operations are presented as independent recipes with no sequence or validation; destructive operations (delete_key, restore_key) lack any verify-before/after checkpoint, so the destructive-operations cap of 3 applies.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with an external Reference Links table; no bundle files exist to navigate, and the ~170-line body is self-contained with only minor content that could arguably be split out.

4 / 5

Total

15

/

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 description with an explicit what/when structure and concrete trigger phrases, occupying a distinct niche. Its only weakness is that the capability verbs (creating/managing/using) are somewhat generic compared to the specific crypto operations surfaced in the triggers.

DimensionReasoningScore

Specificity

The phrase 'creating, managing, and using cryptographic keys' names the domain and lists a few actions, but 'managing' and 'using' are generic rather than concrete operations like encrypt/sign/wrap, so it is not comprehensive.

3 / 5

Completeness

It explicitly states what ('Azure Key Vault Keys SDK for Rust... creating, managing, and using cryptographic keys') and when ('Use for...' plus an explicit 'Triggers:' list with concrete phrases), matching the anchor that requires both with concrete triggers.

5 / 5

Trigger Term Quality

The 'Triggers:' list ('keyvault keys rust', 'KeyClient rust', 'create key rust', 'encrypt rust', 'sign rust') provides good natural keyword coverage a user would actually say, though a few synonyms (e.g. 'azure keyvault', 'rust crypto') are missing.

4 / 5

Distinctiveness Conflict Risk

'Azure Key Vault Keys SDK for Rust' with triggers like 'KeyClient rust' and 'keyvault keys rust' carves a clear niche with distinct triggers and minimal overlap risk with other 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.