Skip to content
TrustedSkillsbeta
Back to all skills

Secrets Management

Checked
wshobson·vlatest·devops·MIT

Securely stores, retrieves, and rotates sensitive credentials like API keys and passwords using encrypted vaults.

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 wshobson/agents --skill secrets-management -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

wshobson

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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

    Only contacts known or declared hosts: 127.0.0.1.

    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.

    Hosts contacted

    127.0.0.1local
  • 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 credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • 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 wshobson/agents at 46891e7e60.

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

Scanned
1 file, 324 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

The secrets-management skill enables AI agents to securely store, retrieve, and manage sensitive information such as API keys, passwords, and other credentials. It ensures that these secrets are handled with encryption and access controls to prevent unauthorized exposure.

When to use it

  • When deploying applications that require secure handling of API keys or database credentials.
  • During development workflows where sensitive data must be accessed without hardcoding values into source code.
  • In environments where multiple users or services need controlled access to shared secrets.
  • For automating tasks that involve third-party APIs, ensuring credentials are not exposed in logs or configuration files.

Key capabilities

  • Secure storage of sensitive information using encryption.
  • Access control mechanisms for managing who can retrieve or modify secrets.
  • Integration with popular secret management tools and platforms.
  • Automatic retrieval of secrets during runtime without exposing them in code.

Example prompts

  • "Retrieve the API key for the payment gateway service."
  • "Store this database password securely in the secret manager."
  • "Grant read access to the 'analytics' secret for the reporting team."

Tips & gotchas

  • Ensure that your environment is properly configured with the necessary permissions to access the secret management system.
  • Avoid storing highly sensitive data unless absolutely required, and always follow the principle of least privilege when granting access.