AB credential-manager
MANDATORY security foundation for OpenClaw. Consolidate scattered API keys and credentials into a secure .env file with proper permissions. Use when setting up OpenClaw, migrating credentials, auditing security, or enforcing the .env standard. This is not optional — centralized credential management is a core requirement for secure OpenClaw deployments. Scans for credential files across common locations, backs up existing files, creates a unified .env with mode 600, validates security, and enforces best practices.
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting
The same skill appears in 1 more place: ClawHub
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
read-dotenvCONSOLIDATION-RULE.md:84Reads a .env file (documentation of a security skill)source ~/.openclaw/.env
security skill -
low Exfiltration
read-dotenvreferences/security.md:109Reads a .env file (documentation of a security skill)set -a && source ~/.openclaw/.env && set +a
security skill -
low Exfiltration
read-dotenvSKILL.md:277Reads a .env file (documentation of a security skill)source ~/.openclaw/.env
security skill -
low Exfiltration
read-dotenvSKILL.md:307Reads a .env file (documentation of a security skill)source ~/.openclaw/.env
security skill
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 41 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1949 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 519: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.