skills.rest
ekremmkasap
ekremmkasapCOMMUNITY
Explore all skills by this author →
GitHub

secrets-management

Manage secure secrets across Vault, AWS, Azure, and Google for CI/CD pipelines.

Updated Mar 18, 2026
Search Tags:#ci/cd#vault#aws-secrets-manager#access-control#secrets-management#rotation
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill secrets-management-ekremmkasap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/cicd-automation/skills/secrets-management
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill secrets-management-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Secure secrets management is critical in modern CI/CD pipelines to prevent leakage of credentials, API keys, and certificates. This skill provides guidelines and tooling references to securely store, rotate, and access secrets across multiple platforms (Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager) without embedding sensitive data in code or configs.

Core Features & Use Cases

  • Centralized secret storage across providers
  • Automated rotation and access control for CI/CD workflows
  • Real-world scenarios: securely inject credentials into actions, pipelines, and infrastructure code

Quick Start

Configure and rotate secrets securely across Vault, AWS Secrets Manager, and native providers for CI/CD pipelines.

Frequently Asked Questions about secrets-management

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

FAQPage Schema
How do I securely manage secrets across multiple CI/CD pipelines like GitHub Actions and GitLab CI?▼

Automated secret rotation in CI/CD involves configuring providers like AWS Secrets Manager or Vault to periodically update credentials without manual intervention. This ensures infrastructure code and pipelines always use fresh, valid credentials while maintaining audit trails.

Does this approach to secrets management work with Terraform workflows and infrastructure code?▼

Secrets management supports Terraform workflows by safely retrieving credentials from centralized providers like Azure Key Vault or Google Secret Manager. This allows infrastructure code to authenticate securely without hardcoding sensitive API keys or certificates.

What's the best way to enforce access control and audit trails for CI/CD secrets?▼

Enforcing access control and audit trails for CI/CD secrets requires applying strict access policies within tools like HashiCorp Vault or AWS Secrets Manager. This restricts credential retrieval to authorized pipelines and logs all access for compliance monitoring.

When do I need centralized secret storage instead of native CI/CD environment variables?▼

Centralized secret storage is needed when managing credentials across multiple platforms, requiring automated rotation and strict access policies. It replaces native CI/CD environment variables to prevent leakage and unify auditing across diverse infrastructure and workflows.

Related Skills

Explore More Software Engineering Skills→
faionfaionfaionfaion
4

faion-devops-engineer

Orchestrate DevOps tasks across infrastructure, containerization, and CI/CD pipelines.

Community
Advanced
4lerman4lerman

secrets-vault-manager

Manages secret lifecycle, rotation, policies, and audit across Vault and cloud secret stores.

Community
Advanced
FrekiManagarmFrekiManagarm

source-command-sparc-devops

Automate DevOps workflows for deployment, provisioning, configuration, monitoring, and cleanup.

Community
Advanced
xlelibertyxleliberty

secrets-vault-manager

Manage HashiCorp Vault clusters and cloud-native secret stores.

Community
Advanced