Skip to content
TrustedSkillsbeta
Back to all skills

Secrets Manager

Checked
itsmostafa·vlatest·security·MIT

Securely stores and retrieves sensitive data like API keys and passwords, streamlining application development and enhancing security practices.

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 itsmostafa/aws-agent-skills --skill secrets-manager -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

itsmostafa

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

    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 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 itsmostafa/aws-agent-skills at e786d25128.

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

Commit
e786d25128
Manifest
skills/secrets-manager/SKILL.md
Scanned
2 files, 717 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

secrets-manager

What it does

This skill enables AI agents to securely retrieve and manage sensitive credentials within AWS environments. It facilitates the safe handling of secrets during automated workflows without requiring hardcoded values in code or prompts.

When to use it

  • Automating deployment pipelines that require database passwords or API keys.
  • Configuring application settings where hardcoding secrets poses a security risk.
  • Managing access tokens for third-party integrations within an AWS infrastructure.
  • Rotating credentials dynamically without manual intervention.

Key capabilities

  • Secure retrieval of AWS Secrets Manager entries.
  • Integration with AI agent workflows for credential management.
  • Support for various secret types including passwords, tokens, and keys.

Example prompts

  • "Retrieve the database password from AWS Secrets Manager for the production environment."
  • "Update the API key in our secrets store to the new value provided."
  • "List all active secrets associated with this specific AWS account."

Tips & gotchas

Ensure your AI agent has appropriate IAM permissions to access Secrets Manager before attempting operations. Always verify that the retrieved secrets are used only in secure, encrypted contexts to maintain data integrity.