Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/azure-keyvault-py
Azure Key Vault SDK for Python.
Passed 22 of 22 test cases with the skill, and 12 of 22 without it.
and 9 more in the full report
10 fixed12 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a Python snippet that lists all historical version IDs and creation timestamps for a secret named 'jwt-signing-secret' in Azure Key Vault. Provide code using azure-keyvault-secrets.
| Checked | Without skill | With skill |
|---|---|---|
| The SecretClient is wrapped in a `with` context manager | Missed | Passed |
| The code calls list_properties_of_secret_versions with secret name 'jwt-signing-secret' | Passed | Passed |
The instructions your model reads when the skill loads.
Secure storage and management for secrets, cryptographic keys, and certificates.
# Secrets
pip install azure-keyvault-secrets azure-identity
# Keys (cryptographic operations)
pip install azure-keyvault-keys azure-identity
# Certificates
pip install azure-keyvault-certificates azure-identity
# All
pip install azure-keyvault-secrets azure-keyvault-keys azure-keyvault-certificates azure-identity
AZURE_KEYVAULT_URL=https://<vault-name>.vault.azure.net/ # Required for all auth methods
AZURE_TOKEN_CREDENTIALS=prod # Required only if DefaultAzureCredential is used in production
🔑 Two rules apply to every code sample below:
- Prefer
DefaultAzureCredential. It works locally (Azure CLI / VS Code / Developer CLI) and in Azure (managed identity, workload identity) with no code change. Avoid connection strings, account/API keys — they bypass Entra audit and rotation.
- Local dev:
DefaultAzureCredentialworks as-is.- Production: set
AZURE_TOKEN_CREDENTIALS=prod(orAZURE_TOKEN_CREDENTIALS=<specific_credential>) to constrain the credential chain to production-safe credentials.- Wrap every client in a context manager so HTTP transports, sockets, and token caches are released deterministically:
- Sync:
with <Client>(...) as client:- Async:
async with <Client>(...) as client:andasync with DefaultAzureCredential() as credential:(fromazure.identity.aio)Snippets may abbreviate this setup, but production code should always follow both rules.
test cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.