Azure Keyvault Py
v0.1.0Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage. Triggers: "key vault", "SecretClient", "KeyClient", "CertificateClient", "secrets", "encryption keys".
⭐ 1· 1.5k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md is a legitimate set of instructions for the Azure Key Vault Python SDK (secrets, keys, certificates) and the listed pip packages align with that purpose. However the registry metadata claims no required environment variables or primary credential while the instructions reference AZURE_KEYVAULT_URL and rely on DefaultAzureCredential, so the declared requirements do not fully match the actual usage. Source/homepage is missing which reduces provenance.
Instruction Scope
Instructions stay within Key Vault operations (set/get/list/delete secrets, manage keys/certificates, crypto ops). They explicitly access secret values (including cert private-key material via secrets) and show destructive operations (purge, delete). They do not instruct reading unrelated local files, but they do rely on authentication behavior (DefaultAzureCredential) that may cause the agent to use any available local Azure credentials/tokens.
Install Mechanism
No install spec in registry (instruction-only). SKILL.md recommends pip installing official azure-keyvault-* and azure-identity packages from PyPI, which is expected and proportionate for a Python SDK integration.
Credentials
Registry metadata lists no required env vars, but SKILL.md references AZURE_KEYVAULT_URL and uses DefaultAzureCredential. DefaultAzureCredential can pull credentials from multiple sources (AZURE_CLIENT_ID/CLIENT_SECRET/TENANT_ID env vars, Azure CLI tokens, managed identity, developer tooling). The skill therefore implicitly requires/consumes sensitive credentials but fails to declare them, which is disproportionate and risky.
Persistence & Privilege
always is false and the skill is user-invocable (normal). disable-model-invocation is false so the agent could call the skill autonomously — by itself this is a platform default, but combined with the skill's ability to access and delete secrets it increases potential impact. The skill does not request persistent installation or system-wide config changes.
What to consider before installing
Things to consider before installing: (1) Provenance — the skill has no listed source or homepage; prefer official Microsoft/published sources. (2) Environment mismatch — SKILL.md requires AZURE_KEYVAULT_URL and implicitly uses DefaultAzureCredential (which can consume AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, Azure CLI tokens, managed identity). The registry metadata did not declare those — verify expected env/credentials before use. (3) Privilege scope — the sample code shows reading secret values and performing destructive actions (delete/purge). Only grant the minimum Azure identity permissions required (use a limited service principal with least privilege rather than broad credentials). (4) Autonomy — the agent may invoke the skill automatically; if you allow that, be confident in credential granularity and the skill owner. (5) If you need higher assurance, ask the publisher for a homepage/repo and confirm the SKILL.md matches an official azure-keyvault SDK example.Like a lobster shell, security has layers — review code before you run it.
latestvk9725kmwknmdsphm9hxgbezm3d808kd8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.