Install the skill above, then run this in your AI tool:
/secrets-management <your description>
About
Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.
Source
What gets added to your project
Preview every file this package writes on install before you run the command above.
Summary
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
Skill instructions
Secrets Management
Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.
Purpose
Implement secure secrets management in CI/CD pipelines without hardcoding sensitive information.
When to Use
Store API keys and credentials
Manage database passwords
Handle TLS certificates
Rotate secrets automatically
Implement least-privilege access
Secrets Management Tools
HashiCorp Vault
Centralized secrets management
Dynamic secrets generation
Secret rotation
Audit logging
Fine-grained access control
AWS Secrets Manager
AWS-native solution
Automatic rotation
Integration with RDS
CloudFormation support
Azure Key Vault
Azure-native solution
HSM-backed keys
Certificate management
RBAC integration
Google Secret Manager
GCP-native solution
Versioning
IAM integration
HashiCorp Vault Integration
Setup Vault
bash
# Start Vault dev server
vault server -dev
# Set environmentexport VAULT_ADDR='http://127.0.0.1:8200'export VAULT_TOKEN='root'# Enable secrets engine
vault secrets enable -path=secret kv-v2
# Store secret
vault kv put secret/database/config username=admin password=secret
GitHub Actions with Vault
yaml
name:DeploywithVaultSecretson: [push]
jobs:deploy:runs-on:ubuntu-lateststeps:-uses:actions/checkout@v4-name:ImportSecretsfromVaultuses:hashicorp/vault-action@v2with:url:https://vault.example.com:8200token:${{secrets.VAULT_TOKEN}}secrets:|
secret/data/database username | DB_USERNAME ;
secret/data/database password | DB_PASSWORD ;
secret/data/api key | API_KEY
-name:Usesecretsrun:|
echo "Connecting to database as $DB_USERNAME"
# Use $DB_PASSWORD, $API_KEY
GitLab CI with Vault
yaml
deploy:image:vault:1.17before_script:-exportVAULT_ADDR=https://vault.example.com:8200-exportVAULT_TOKEN=$VAULT_TOKEN-apkaddcurljqscript:-|
DB_PASSWORD=$(vault kv get -field=password secret/database/config)
API_KEY=$(vault kv get -field=key secret/api/credentials)
echo "Deploying with secrets..."
# Use $DB_PASSWORD, $API_KEY
-name:UseGitHubsecretenv:API_KEY:${{secrets.API_KEY}}DATABASE_URL:${{secrets.DATABASE_URL}}run:|
# Secrets are injected as env vars — never print them to logs
./deploy.sh
Environment Secrets
yaml
deploy:runs-on:ubuntu-latestenvironment:productionsteps:-name:Deployenv:PROD_API_KEY:${{secrets.PROD_API_KEY}}run:|
# Secret injected as env var — never print to logs
./deploy.sh
GitLab CI/CD Variables
Project Variables
yaml
deploy:script:-echo"Deploying with $API_KEY"-echo"Database: $DATABASE_URL"
Add this badge to a GitHub README so readers can open the package page and install the same version.
[](https://www.aipm-registry.com/skills/wshobson/secrets-management/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)
This imported publisher has not claimed its AIPM account. A connected account confirms account control, but it does not guarantee that a package is safe.
AI assistant context
What this skill is for
@wshobson/secrets-management@1.0.0 is an AIPM skill package for All tools. Use it when a project needs the reusable AI behavior described as: Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
Run aipm add @wshobson/secrets-management@1.0.0 in a project that has AIPM initialized.
Supported tools
@wshobson/secrets-management@1.0.0 supports All tools.
Before installing
AIPM skills can add files to your project. Review the package name, target, description, license, and publisher before installing. Use a clean branch when trying a new skill.