Skip to content
TrustedSkillsbeta
Back to all skills

Secrets Rotation

Checked
aj-geddes·vlatest·security·MIT

Automatically rotates sensitive secrets (passwords, API keys) to enhance security and mitigate risks from compromised credentials.

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 aj-geddes/useful-ai-prompts --skill secrets-rotation -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/secrets-rotation/SKILL.md
Scanned
5 files, 674 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

The secrets-rotation skill automates the secure management of sensitive credentials within AI agent workflows. It enables agents to dynamically retrieve, update, and refresh API keys and tokens without manual intervention or hardcoded values. This capability ensures that agents maintain access to external services while adhering to security best practices for credential hygiene.

When to use it

  • Deploying new AI agents that require immediate access to third-party APIs like GitHub, Stripe, or Slack.
  • Updating compromised or expired credentials across multiple agent instances simultaneously.
  • Implementing automated security protocols to reduce the risk of static key exposure in code repositories.
  • Managing temporary tokens that have specific expiration times within a defined lifecycle.

Key capabilities

  • Dynamic retrieval of secrets from external vaults or environment variables at runtime.
  • Automatic rotation logic to refresh credentials before they expire.
  • Secure handling of sensitive data without logging plaintext values in agent outputs.
  • Integration with standard secret management patterns used in modern development pipelines.

Example prompts

  • "Connect to my GitHub API using a rotated token and fetch the latest repository statistics."
  • "Update your Stripe integration credentials to the new keys provided in the secure vault before processing payments."
  • "Check if my current Slack bot token is nearing expiration and rotate it automatically if needed."

Tips & gotchas

Ensure your AI agent has read-only access to the secret store initially; write permissions for rotation should be strictly controlled by external infrastructure. Always verify that the rotation mechanism respects the specific format requirements of the target service (e.g., OAuth vs. API Key) to prevent authentication failures during the switch.