Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Credential lifecycle security for agent workspaces. Audit credential exposure, detect misconfigured permissions, inventory all secrets, and identify stale credentials needing rotation. Free alert layer — upgrade to openclaw-vault-pro for automated remediation, credential rotation, and access control.
Credential lifecycle security for agent workspaces. Audit credential exposure, detect misconfigured permissions, inventory all secrets, and identify stale credentials needing rotation. Free alert layer — upgrade to openclaw-vault-pro for automated remediation, credential rotation, and access control.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Protects your credential lifecycle — not just finding secrets in source code (that's what Sentry does), but tracking how credentials are exposed through services, permissions, history, configs, containers, and time.
Credentials don't just leak through source code. They leak through: Permissions — .env files readable by every user on the system Shell history — passwords and tokens visible in .bash_history Git config — credentials embedded in remote URLs Config files — hardcoded secrets in JSON/YAML/TOML/INI configs Log files — tokens accidentally logged during debugging Docker configs — secrets baked into container images Staleness — credentials that haven't been rotated in months This skill watches the full credential lifecycle. Sentry finds secrets in files. Vault finds secrets that are exposed.
Comprehensive credential exposure audit: permission checks, shell history, git config, config file scanning, log file scanning, gitignore coverage, and staleness detection. python3 {baseDir}/scripts/vault.py audit --workspace /path/to/workspace
Detect credential exposure vectors: misconfigured permissions, public directory exposure, git history risks, Docker credential embedding, shell alias leaks, and URL query parameter credentials in code. python3 {baseDir}/scripts/vault.py exposure --workspace /path/to/workspace
Build a structured inventory of all credential files in the workspace. Categorizes by type (API key, database URI, token, certificate, SSH key, password), tracks age, and flags stale or exposed credentials. python3 {baseDir}/scripts/vault.py inventory --workspace /path/to/workspace
One-line summary: credential count, exposure count, staleness warnings. python3 {baseDir}/scripts/vault.py status --workspace /path/to/workspace
If --workspace is omitted, the script tries: OPENCLAW_WORKSPACE environment variable Current directory (if AGENTS.md exists) ~/.openclaw/workspace (default)
CategoryDetailsPermissions.env files with world-readable or group-readable permissionsShell HistoryCredentials in .bash_history, .zsh_history, .python_history, etc.Git ConfigCredentials embedded in git remote URLs, plaintext credential helpersConfig FilesHardcoded secrets in JSON, YAML, TOML, INI config filesLog FilesCredentials accidentally logged in .log filesGitignoreMissing patterns for .env, *.pem, *.key, credentials.json, etc.StalenessCredential files older than 90 days that may need rotationPublic DirsCredential files in public/, static/, www/, dist/, build/Git HistoryCredential files in git repos that may be committedDockerSecrets hardcoded in Dockerfile and docker-compose configsShell RCCredentials in .bashrc, .zshrc, .profile aliasesURL ParamsAPI keys/tokens passed in URL query strings in code
0 — Clean, no issues 1 — Warnings detected (review needed) 2 — Critical exposure detected (action needed)
Python standard library only. No pip install. No network calls. Everything runs locally.
Works with OpenClaw, Claude Code, Cursor, and any tool using the Agent Skills specification.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.