Skip to content
TrustedSkillsbeta
Back to all skills

Find Credential Usage

Listed
dalehurley·vlatest·security

This skill identifies how specific credentials are being utilized across your systems for improved security and compliance management.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dalehurley/phpbot --skill find-credential-usage -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dalehurley

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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/find-credential-usage/SKILL.md:37OS keychain / credential manager
      security find-generic-password -w -s "{{SEARCH_TERM}}" 2>/dev/null || echo "Not found in Keychain"

  • 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 dalehurley/phpbot at 6128f14773.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6128f14773
Manifest
skills/find-credential-usage/SKILL.md
Scanned
1 file, 55 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, find-credential-usage, helps locate and understand how credentials are being utilized within a system. It can identify where specific usernames or passwords appear in code or configuration files. This is valuable for security audits, troubleshooting access issues, and ensuring best practices around credential management.

When to use it

  • Security Audit: You need to quickly find all instances of a particular username or password used within your codebase.
  • Troubleshooting Access Errors: An application isn't working as expected, and you suspect incorrect credentials are being used somewhere.
  • Credential Rotation Planning: Before rotating passwords, you want to identify every location where the current password is in use.
  • Code Review: During a code review, you need to verify that sensitive information like API keys or database passwords aren't hardcoded.

Key capabilities

  • Credential identification
  • Location tracking within files
  • Support for various file types (implied)

Example prompts

  • "Find all uses of the password 'MySecretPassword' in this project."
  • "Where is the username 'adminUser' used?"
  • "Show me every location where an API key appears in these files."

Tips & gotchas

The effectiveness of this skill depends on having access to the relevant codebase or configuration files. It’s best suited for projects with well-defined file structures and clear credential usage patterns.