Skip to content
TakoAPI
Back to skills

secrets-management

by brandonwise

DevOps & Cloud
482Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, and native platform solutions.

Description

What This Skill Does

Covers how to store, retrieve, and rotate secrets in CI/CD pipelines using HashiCorp Vault, AWS Secrets Manager, and native platform secret stores. Includes patterns for GitHub Actions, GitLab CI, Kubernetes, and Terraform. Also covers secret scanning to catch leaked credentials before they reach git.

Centralizing secrets in a dedicated store with audit logging and automatic rotation reduces the risk of credential leaks compared to scattering values across .env files, CI variables, and config repositories.

When to Use It

  • Pulling database passwords into GitHub Actions without hardcoding them
  • Rotating API keys automatically on a 90-day schedule
  • Syncing Vault secrets into Kubernetes pods via External Secrets Operator
  • Blocking secret commits with a pre-commit TruffleHog hook
  • Managing environment-specific credentials across dev, staging, and production

Example Workflow

INPUT

User asks: How do I pull a Vault database secret into my GitHub Actions deploy job?

AGENT
  1. 1

    Enables the KV-v2 secrets engine in Vault and stores the database credentials at a target path

  2. 2

    Adds the hashicorp/vault-action step to the GitHub Actions workflow, pointing to the Vault URL and token secret

  3. 3

    Maps the Vault secret fields to named environment variables using the secrets mapping syntax

  4. 4

    Confirms the secret is masked in logs so it will not appear in job output

OUTPUT

A working GitHub Actions workflow YAML that fetches DB credentials from Vault at runtime and exposes them as masked environment variables to subsequent steps

Requirements

  • HashiCorp Vault server (self-hosted or HCP Vault) or an AWS, Azure, or GCP account with the relevant secrets service enabled
  • Vault token or cloud IAM credentials added as CI/CD secrets (e.g., VAULT_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)
  • For Kubernetes integration: External Secrets Operator installed in the cluster

Installation

clawhub install brandonwise/secrets-management

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links