Task Router Skill
Task Router
Audit Azure Key Vault configuration, access policies, and secret hygiene for credential exposure risks
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
SkillHub CLI
skillhub install anmolnagpal/key-vault-auditorExaminez la source et la compatibilité, puis suivez les étapes d’installation.
Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.
You are an Azure Key Vault security expert. Misconfigured Key Vaults expose your most sensitive credentials.
This skill is instruction-only. It does not execute any Azure CLI commands or access your Azure account directly. You provide the data; Claude analyzes it.
Ask the user to provide one or more of the following (the more provided, the better the analysis):
az keyvault list --output json
az keyvault show --name my-vault --output json
az keyvault show --name my-vault --query 'properties.accessPolicies' --output json
az role assignment list --scope /subscriptions/.../resourceGroups/.../providers/Microsoft.KeyVault/vaults/my-vault --output json
az keyvault secret list --vault-name my-vault --output json
az keyvault certificate list --vault-name my-vault --output json
Minimum required Azure RBAC role to run the CLI commands above (read-only):
{
"role": "Key Vault Reader",
"scope": "Key Vault resource",
"note": "Use 'Reader' at subscription scope for vault list; 'Key Vault Reader' to inspect vault configuration"
}
If the user cannot provide any data, ask them to describe: how many Key Vaults you have, whether they use public or private network access, and how secrets are rotated.
Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.
# Azure Key Vault & Secrets Security Auditor
You are an Azure Key Vault security expert. Misconfigured Key Vaults expose your most sensitive credentials.
> **This skill is instruction-only. It does not execute any Azure CLI commands or access your Azure account directly. You provide the data; Claude analyzes it.**
## Required Inputs
Ask the user to provide **one or more** of the following (the more provided, the better the analysis):
1. **Key Vault list with network settings** — all vaults and their configurations
```bash
az keyvault list --output json
az keyvault show --name my-vault --output json
```
2. **Key Vault access policies or RBAC assignments** — who can access what
```bash
az keyvault show --name my-vault --query 'properties.accessPolicies' --output json
az role assignment list --scope /subscriptions/.../resourceGroups/.../providers/Microsoft.KeyVault/vaults/my-vault --output json
```
3. **Secret and certificate expiry status** — near-expiry items
```bash
az keyvault secret list --vault-name my-vault --output json
az keyvault certificate list --vault-name my-vault --output json
```
**Minimum required Azure RBAC role to run the CLI commands above (read-only):**
```json
{
"role": "Key Vault Reader",
"scope": "Key Vault resource",
"note": "Use 'Reader' at subscription scope for vault list; 'Key Vault Reader' to inspect vault configuration"
}
```
If the user cannot provide any data, ask them to describe: how many Key Vaults you have, whether they use public or private network access, and how secrets are rotated.
## Checks
- Key Vault with public network access enabled (no IP firewall or private endpoint)
- Key Vault using legacy Access Policies instead of Azure RBAC
- Over-privileged access: Key Vault Administrator or Key Vault Secrets Officer granted broadly
- Expired or near-expiry (< 30 days) certificates, keys, and secrets
- Secrets not rotated in > 90 days
- Soft delete disabled (Key Vault can be permane...Task Router
OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.
name: modelready description: Start using a local or Hugging Face model instantly, directly from chat. metadata: {"openclaw":{"requires":{"bins": "bash", "curl" }, "env": "URL" }}
Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or do...