secrets-management

Manage CI/CD secrets across Vault, AWS, Azure, and Google secret stores.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mwathiben/PropManager --skill secrets-management-mwathiben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/mwathiben/PropManager/tree/main/.claude/skills/secrets-management
Command: npx skills add https://github.com/mwathiben/PropManager --skill secrets-management-mwathiben

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Secrets management is critical to prevent credentials and API keys from leaking in code, CI logs, or config files, enabling safer automation across pipelines.

Core Features & Use Cases

  • Centralized secret storage across Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.
  • Automatic secret rotation, fine-grained access control, and secure retrieval in CI workflows (GitHub Actions and GitLab CI).
  • Real-world use: store database passwords and API keys, rotate them automatically, and minimize blast radius in deployments.

Quick Start

Configure your CI/CD pipeline to fetch secrets at runtime from your chosen secret store and rotate credentials automatically.

Frequently Asked Questions about secrets-management

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

FAQPage Schema
How do I manage CI/CD secrets securely without embedding credentials in source code?

Secure CI/CD secrets by fetching credentials at runtime from centralized stores like Vault or AWS Secrets Manager, rather than hardcoding API keys or database passwords in source code or config files.

Does this approach support fetching secrets across both GitHub Actions and GitLab CI pipelines?

Yes, secure secret retrieval is supported across both GitHub Actions and GitLab CI pipelines, allowing you to pull database passwords and API keys dynamically during workflow execution.

What's the best way to automatically rotate API keys and database passwords in a deployment pipeline?

The best way to rotate API keys and database passwords is by using centralized secret stores with automatic rotation capabilities, minimizing the blast radius in deployments while maintaining secure CI workflows.

Which cloud secret managers can I integrate for centralized secret storage and access control?

You can integrate HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager for centralized secret storage, automatic rotation, and fine-grained access control in your pipelines.

How does runtime secret retrieval prevent credential leakage in CI logs?

Runtime secret retrieval prevents credential leakage by fetching secrets directly from external vaults during pipeline execution, ensuring sensitive data like TLS certificates and API keys never appear in code, CI logs, or config files.

Why do I need centralized secret storage instead of using native CI/CD environment variables?

Centralized secret storage provides automatic rotation, fine-grained access control, and minimized blast radius across deployments, overcoming the static nature and limited security controls of native CI/CD environment variables.