Agent skill · DevOps & Cloud

azure-keyvault-secrets-rust

Azure Key Vault Secrets library for Rust. Store and retrieve secrets, passwords, and API keys.

Microsoft293,217★ · +1,988/wk · 14 repos on radarProfile →
copilotMIT
Install
npx skills add microsoft/skills --skill azure-keyvault-secrets-rust --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Declared author: Microsoft
Path: .github/plugins/azure-sdk-rust/skills/azure-keyvault-secrets-rust/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,860
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Azure Key Vault Secrets library for Rust Secure storage for passwords, API keys, and connection strings. Use this skill when: - An app needs to store or retrieve secrets from Azure Key Vault in Rust - You need to set, get, update, or delete secrets - You need to list secret properties with pagination - You need error handling for missing secrets > **IMPORTANT:** Only use the official `azure_secu

More from skills
All skills →
About this skill
What does the azure-keyvault-secrets-rust skill do?

Azure Key Vault Secrets library for Rust. Store and retrieve secrets, passwords, and API keys.

How do I install it?

Run `npx skills add microsoft/skills --skill azure-keyvault-secrets-rust --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From microsoft/skills, a repository with 2,860 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going