Skip to content
TrustedSkillsbeta
Back to all skills

Manage Kubernetes Secrets

Checked
pjt222·vlatest·cloud·MIT

Helps with management, Kubernetes as part of deploying and managing cloud infrastructure workflows.

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 pjt222/agent-almanac --skill manage-kubernetes-secrets -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

pjt222

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: github.com.

    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

    github.comsource host

  • 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 pjt222/development-guides at bcca822c1c.

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

Commit
bcca822c1c
Manifest
skills/manage-kubernetes-secrets/SKILL.md
Scanned
4 files, 1,781 lines
Copies in repo
3 — all of them scanned
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 allows AI agents to manage Kubernetes secrets, including creating, retrieving, updating, and deleting them. It provides a secure way to handle sensitive information like passwords, API keys, and certificates within your Kubernetes clusters. The skill ensures that these credentials are stored and accessed securely, preventing exposure in configuration files or environment variables.

When to use it

  • Automated deployments: Use this skill to automatically create secrets for new applications deployed to a Kubernetes cluster.
  • Credential rotation: Rotate existing secrets on a schedule to improve security posture.
  • Managing database passwords: Securely manage and update database credentials stored as Kubernetes secrets.
  • Integrating with CI/CD pipelines: Automate the creation of secrets during your continuous integration and continuous delivery processes.

Key capabilities

  • Create new Kubernetes secrets.
  • Retrieve existing secret data.
  • Update existing secrets.
  • Delete Kubernetes secrets.

Example prompts

  • "Create a Kubernetes secret named 'db-credentials' with username 'admin' and password 'securepassword'."
  • "What is the password stored in the 'api-keys' secret?"
  • "Update the 'database-url' value within the 'my-app-secrets' secret."

Tips & gotchas

  • Requires appropriate Kubernetes access credentials configured for the AI agent.
  • Be mindful of the sensitivity of the data being stored and ensure proper RBAC (Role-Based Access Control) is in place to limit access to secrets.