Credential Scanner
ListedThis tool swiftly verifies credentials like licenses & certifications against databases, saving time and ensuring accuracy for due diligence.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add useai-pro/openclaw-skills-security --skill credential-scanner -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
useai-pro
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No credential access: failed
Touches credential material in 1 place.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found
- skills/credential-scanner/SKILL.md:109password manager store
3. Consider using a secret manager (e.g., 1Password CLI, Vault, Doppler)
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned useai-pro/openclaw-skills-security at 4645f2d047.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4645f2d047
- Scanned
- 1 file, 116 lines
About this skill
What it does
The credential-scanner skill identifies and extracts credentials (like API keys, passwords, and tokens) from text. It can parse various file formats including JSON, YAML, and environment files to locate sensitive information. This helps automate the process of finding potential security vulnerabilities related to exposed credentials.
When to use it
- Reviewing code repositories: Scan newly committed code for accidentally included API keys or passwords.
- Analyzing configuration files: Identify any hardcoded credentials within infrastructure-as-code configurations (e.g., Terraform, Ansible).
- Auditing environment variables: Check for sensitive information stored in
.envfiles or other environment variable sources. - Incident response: Quickly search through logs or documents to locate potentially compromised credentials after a security event.
Key capabilities
- Supports JSON, YAML, and environment file formats.
- Identifies common credential patterns (e.g., API keys, passwords).
- Provides detailed location of found credentials within files.
Example prompts
- "Scan this file for any exposed API keys: [file content]"
- "Find all potential passwords in my Terraform configuration."
- "Analyze this JSON file and report any credentials it contains."
Tips & gotchas
The skill's effectiveness relies on recognizing common credential patterns. It may not identify every possible type of credential, so manual review is still recommended for critical security assessments.