# Build Azure Key Vault Key Workflows in Rust

Rust developers need reliable patterns for managing cryptographic keys in Azure Key Vault. This skill provides focused guidance for authentication, lifecycle operations, backup, restore, and RBAC.

## Install

```bash
npx skillstore add sickn33/azure-keyvault-keys-rust
```

## Metadata

- Status: approved
- Slug: sickn33-azure-keyvault-keys-rust
- Skillstore revision: r2
- Version status: missing
- Tree hash: bebc92dcafda88557c4fb4cbc03830efb1a87faa09a2d911961ee8b4412a6417
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-keyvault-keys-rust
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-keyvault-keys-rust
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-keyvault-keys-rust/manifest

## Capabilities

- Shows how to add the Azure Key Vault Keys and Azure Identity crates.
- Explains KeyClient setup with developer credentials and an Azure vault endpoint.
- Provides examples for creating RSA and elliptic-curve keys.
- Covers key retrieval, listing, deletion, backup, and restore operations.
- Summarizes supported cryptographic operations, RBAC roles, and production practices.

## Use Cases

- Add Key Management to a Rust Service: Create a KeyClient and implement common key lifecycle operations for an application.
- Select Keys and Access Roles: Compare RSA, EC, and HSM options while identifying suitable Key Vault RBAC roles.
- Plan Backup and Recovery: Design controlled key backup, restore, soft-delete, and rotation procedures for production.

## Prompt Templates

### Connect to a Vault

```
Show me how to add the required Rust crates and initialize KeyClient for my Azure Key Vault. Use developer credentials and explain each placeholder.
```

### Create and List Keys

```
Create a Rust example that adds one RSA key and one P-256 EC key, then lists their names. Include error-handling guidance.
```

### Design a Safe Lifecycle

```
Plan Rust workflows for key creation, retrieval, rotation, backup, restore, and deletion. Add confirmation steps and recovery controls for destructive actions.
```

### Review a Production Architecture

```
Review my Rust Key Vault design for identity, RBAC, HSM selection, rotation, backup protection, logging, and failure handling. Identify risks and concrete improvements.
```

## Limitations

- The snippets are partial examples and do not form a complete runnable application.
- Cryptographic operations are summarized but not implemented with complete encrypt, decrypt, sign, or verify examples.
- The skill does not provision Key Vault, configure networking, or assign Azure roles.
- Users need an Azure subscription, a vault, suitable permissions, and environment-specific testing.

## Best Practices

- Use managed identity in production and grant the smallest suitable Key Vault role.
- Enable soft delete, purge protection, rotation, and monitored recovery procedures.
- Protect backup bytes with encryption, access controls, retention policies, and logging exclusions.

## Anti Patterns

- Do not embed vault credentials, key material, or backup bytes in source code.
- Do not delete keys without confirming scope, dependencies, approval, and recovery controls.
- Do not grant broad administrative roles when an application only needs cryptographic operations.

## Security Audit

- Audited at: 2026-07-23T20:25:46.812\+00:00
- Summary: All 31 static findings are false positives caused by Markdown formatting, fixed Azure package installation, expected service endpoints, trusted reference links, and non-secret key terminology. The skill has no prompt injection or malicious intent, but its deletion and backup examples need stronger operational safeguards. These semantic risks are limited to legitimate Key Vault lifecycle guidance.

## Stats

- Views: 110
- Downloads: 10
- Favorites: 0
- Popularity score: 0