secrets-management

Implement secure secrets management for CI/CD pipelines using Vault and cloud secret stores.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TechCorp25/kingdom --skill secrets-management-techcorp25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/TechCorp25/kingdom/tree/main/.claude/skills/cicd-automation/skills/secrets-management
Command: npx skills add https://github.com/TechCorp25/kingdom --skill secrets-management-techcorp25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hardcoding credentials in CI/CD pipelines exposes API keys, database passwords, and certificates to leaks, and manual rotation is error-prone. This Skill provides patterns for storing, retrieving, rotating, and scanning secrets securely across pipeline platforms. ## Core Features & Use Cases - Multi-Platform Integration: Configure HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager within GitHub Actions and GitLab CI workflows. - Secret Rotation & Scanning: Automate rotation with AWS Lambda and detect leaked credentials using TruffleHog in pre-commit hooks and CI jobs. - Kubernetes Support: Sync secrets into clusters with the External Secrets Operator backed by Vault. - Use Case: A team needs database credentials injected into a GitHub Actions deploy job without committing them to Git; this Skill shows how to pull them from Vault at runtime with masked output. ## Quick Start Ask the AI to set up a GitHub Actions workflow that retrieves database credentials from HashiCorp Vault instead of storing them in the repository.

Frequently Asked Questions about secrets-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use HashiCorp Vault secrets in GitHub Actions?▼

Use the hashicorp/vault-action step with your Vault URL and token to import secrets as environment variables. Map secret paths like secret/data/database to output variables such as DB_USERNAME and DB_PASSWORD for use in later steps.

How to retrieve AWS Secrets Manager values in a CI pipeline?▼

Configure AWS credentials with aws-actions/configure-aws-credentials, then call aws secretsmanager get-secret-value with the secret ID. Mask the output with ::add-mask:: and write it to $GITHUB_ENV for subsequent steps.

Vault vs AWS Secrets Manager for CI/CD secrets?▼

Vault offers dynamic secrets, fine-grained access control, and works across clouds, while AWS Secrets Manager provides native RDS integration and automatic rotation within AWS. Choose based on your cloud footprint and rotation needs.

Can I sync Vault secrets into Kubernetes automatically?▼

Yes, the External Secrets Operator syncs Vault secrets into Kubernetes Secrets on a refresh interval. Define a SecretStore pointing to your Vault server and an ExternalSecret mapping remote keys to local secret keys.

How do I prevent secrets from being committed to Git?▼

Add a pre-commit hook running TruffleHog against the repository filesystem to block commits containing detected secrets. Also run TruffleHog as a CI stage so leaks are caught even if local hooks are bypassed.