openclaw-vault-pro

What This Skill Does

OpenClaw Vault Pro is an advanced security automation agent designed for developers and DevOps teams to manage the full lifecycle of sensitive credentials. Building upon the foundational detection capabilities of the free vault, this Pro version introduces active countermeasures to protect sensitive assets. It goes beyond mere identification to provide automated remediation, including permission hardening, file quarantine, and deep Git history analysis. The tool scans for misconfigured permissions, embedded Docker credentials, shell alias leaks, and plaintext secrets, ensuring that your local and remote workspaces remain hardened against unauthorized access.

Installation

To integrate this security suite into your workspace, execute the following command in your terminal:

clawhub install openclaw/skills/skills/atlaspa/openclaw-vault-pro

Ensure you have the necessary system-level permissions to modify file attributes, as the 'fix-permissions' and 'quarantine' functions require write access to your workspace directories.

Use Cases

This skill is ideal for:

• Automated Compliance: Regularly auditing developer machines to ensure compliance with security policies regarding key rotation.
• Incident Response: Quickly quarantining files identified as exposed to prevent accidental push-to-production or remote exposure.
• Git Hygiene: Scanning repositories for sensitive tokens that were committed in the past, even if they have since been deleted from the working directory.
• Privilege Hardening: Automatically correcting weak file permissions on local .env and configuration files to prevent local lateral movement.

Example Prompts

1. "OpenClaw, run a full security audit on my current project directory and fix any loose file permissions you find."
2. "I think I may have leaked an AWS key in my history; use git-guard to check my repository for any previous commits containing credentials."
3. "Show me a status report of my credentials and list any files that are currently overdue for rotation based on the 90-day policy."

Tips & Limitations

• Permissions: Always verify that 'fix-permissions' does not interfere with specific build tools that require group-readable access; use with caution in shared team environments.
• Git Guard: Remember that Git history scanning is a local tool; it will not scrub remote history (like GitHub/GitLab). If a secret is found in history, treat it as compromised and rotate the credential immediately.
• Quarantine: Be aware that moving files into the .quarantine folder will break hardcoded paths in your local development environment. Ensure you use the 'unquarantine' command to restore functional access.