Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Consolidation Rule enforcement - all credentials MUST be in ~/.openclaw/.env ONLY. Enhanced detection for workspace/skills/scripts .env files. New CONSOLIDATION-RULE.md documentation.
What This Skill Does
Consolidates scattered API keys and credentials into a single ~/.openclaw/.env file with mode 600 permissions. Scans common config locations, backs up existing files with timestamps, merges everything, and validates the result. Other OpenClaw skills use it as a security gate before loading any credentials.
Enforces a single git-ignored file with mode 600 rather than leaving credentials spread across config directories where permissions and git-ignore status vary per file.
When to use it
- Setting up OpenClaw on a new machine for the first time
- Migrating credentials from multiple scattered config files
- Auditing credential security before sharing a workstation
- Fixing a skill that fails because credentials are in the wrong location
- Cleaning up old credential files after consolidation
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Migrate my scattered API credentials to a secure location
- 1Run scan.py to discover credential files in ~/.config, ~/.openclaw/workspace/memory, and other common paths
- 2Run consolidate.py to back up existing files with timestamps and merge into ~/.openclaw/.env
- 3Set ~/.openclaw/.env permissions to mode 600
- 4Run validate.py to confirm permissions, format, and git-ignore protection
- 5Run cleanup.py --confirm to remove old credential files while preserving backups
All credentials unified in ~/.openclaw/.env (mode 600), old files backed up under ~/.openclaw/backups/, .gitignore updated