← Back to Skills Marketplace
callmedas69

Credential Manager

by Mr. TeeClaw · GitHub ↗ · v1.3.0
cross-platform ⚠ suspicious
6754
Downloads
2
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install credential-manager
Description
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.
Usage Guidance
Install only if you intend to let this skill read and reorganize credentials across your account. Before running consolidation or cleanup, review the exact files it found, avoid --yes for sensitive migrations, protect or encrypt backups yourself, do not store wallet seed phrases or irreplaceable private keys unless you fully accept the risk, and do not delete originals until you have verified the new store and backups work.
Capability Analysis
Type: OpenClaw Skill Name: credential-manager Version: 1.3.0 This skill is classified as suspicious due to its extensive use of high-risk capabilities, including scanning the entire filesystem for credential files, reading their contents, modifying sensitive files like `.env` and `.gitignore`, changing file permissions (`chmod 600`), and deleting original credential files. While these actions are explicitly stated as necessary for its security-enhancing purpose (centralizing and securing credentials), they represent significant control over the user's sensitive data and system configuration. The `SKILL.md` and other documentation files use strong, imperative language to instruct the agent to perform these actions, which, while aimed at enforcing security, constitutes a form of prompt injection directing the agent to execute sensitive operations.
Capability Assessment
⚠ Credentials
Default discovery covers broad cross-application locations such as ~/.config/*/credentials.json, ~/.local/share/*/credentials.json, OpenClaw memory files, skill directories, workspace .env files, and custom paths, then reads values and aggregates them without per-file approval.
ℹ Install Mechanism
The artifact contains local Python scripts and Markdown documentation with no observed remote payload retrieval, package installation, install hook, network exfiltration, or obfuscation; users invoke the scripts manually or through documented commands.
⚠ Instruction Scope
The instructions frame consolidation as mandatory with no exceptions, tell other skills to depend on this skill for credential access, and include bash examples that source ~/.openclaw/.env directly, which can execute shell syntax from a tampered or malformed .env file.
⚠ Persistence & Privilege
The skill persistently writes ~/.openclaw/.env, .env.example, .gitignore, and plaintext backups, and cleanup can permanently unlink original credential files after confirmation without proving each file was successfully migrated and backed up.
⚠ Purpose & Capability
The stated purpose is credential consolidation, and the scripts do scan, parse, back up, merge, validate, and clean up credentials; however, the default design intentionally centralizes many high-value secrets, including API tokens, private keys, mnemonics, and seed phrases, into one plaintext file.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install credential-manager
  3. After installation, invoke the skill by name or use /credential-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
Consolidation Rule enforcement - all credentials MUST be in ~/.openclaw/.env ONLY. Enhanced detection for workspace/skills/scripts .env files. New CONSOLIDATION-RULE.md documentation.
v1.2.0
Added crypto-specific sensitive key patterns (private_key, passphrase, mnemonic, seed_phrase, signing_key, wallet_key) and updated documentation
v1.0.0
Initial publish: MANDATORY security foundation for OpenClaw. Consolidate scattered API keys and credentials into a secure .env file with proper permissions.
v1.1.0
🔒 MANDATORY security foundation. Consolidates scattered credentials into secure .env with proper permissions. Includes enforcement tools for skill developers. Non-negotiable security infrastructure for OpenClaw deployments.
Metadata
Slug credential-manager
Version 1.3.0
License —
All-time Installs 0
Active Installs 0
Total Versions 4
Frequently Asked Questions

What is 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. It is an AI Agent Skill for Claude Code / OpenClaw, with 6754 downloads so far.

How do I install Credential Manager?

Run "/install credential-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Credential Manager free?

Yes, Credential Manager is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Credential Manager support?

Credential Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Credential Manager?

It is built and maintained by Mr. TeeClaw (@callmedas69); the current version is v1.3.0.

💬 Comments