Azure Key Vault Certificates library for Rust. Create, manage, and use X.509 certificates including self-signed and CA-issued. Triggers: "keyvault certificates rust", "CertificateClient rust", "create certificate rust", "self-signed certificate rust", "X.509 rust".
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 8/11/2026
What it changes
Passed 22 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill100%
Checks it passed that the model alone missed
The response uses the ResourceExt trait.
The response passes None for the options parameter.
The response warns against selecting version 0.21.0.
and 21 more in the full report
13 fixed9 passed either way0 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+50%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/11/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
When building a Rust application that uses Key Vault certificates, do we need to add azure_core as a direct dependency in Cargo.toml alongside azure_security_keyvault_certificates?
What was checked, without and with the skill
Checked
Without skill
With skill
The response states that direct azure_core dependency is optional when using crate re-exports.
Missed
Passed
The response recommends adding azure_core when directly importing azure_core types.
Passed
Passed
case-08 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md210 linessingle file
Azure Key Vault Certificates library for Rust
Manage X.509 certificates for TLS/SSL, code signing, and authentication.
Use this skill when:
An app needs to create or manage X.509 certificates in Key Vault from Rust
You need self-signed or CA-issued certificates
You need long-running operations (LRO) for certificate issuance
You need to sign data using a certificate's key
IMPORTANT: Only use the official azure_security_keyvault_certificates crate published by the azure-sdk crates.io user. Do NOT use unofficial or community crates. Official crates use underscores in names and none have version 0.21.0.
Installation
cargo add azure_security_keyvault_certificates azure_identity tokio futures
If your code uses azure_core types directly, add azure_core to Cargo.toml. If you only use azure_security_keyvault_certificates re-exports, direct azure_core dependency is optional.
Environment Variables
AZURE_KEYVAULT_URL=https://<vault-name>.vault.azure.net/ # Required for all operations
Authentication
Rust Azure SDK code must not use DefaultAzureCredential. The Rust identity crate does not provide that type.
use azure_identity::DeveloperToolsCredential;
use azure_security_keyvault_certificates::CertificateClient;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
// Local dev: DeveloperToolsCredential. Production: use ManagedIdentityCredential.
let credential = DeveloperToolsCredential::new(None)?;
let client = CertificateClient::new(