secrets-management

Name: secrets-management
Availability: InStock
Author: Yusuf

Manage secrets in CI/CD pipelines with Vault and cloud secret managers.

1|Updated Feb 19, 2026

Search Tags:#devops #ci/cd #security #secrets management #vault #aws secrets manager

Ready to run

npx skills add https://github.com/yusufcmg/Antigravity-Agents-Workflows --skill secrets-management-yusufcmg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/yusufcmg/Antigravity-Agents-Workflows/tree/main/.agent/skills/devops/secrets-management
Command: npx skills add https://github.com/yusufcmg/Antigravity-Agents-Workflows --skill secrets-management-yusufcmg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill addresses the critical need to manage sensitive credentials and secrets within CI/CD pipelines, preventing hardcoding and enhancing security.

Core Features & Use Cases

Secure Storage: Integrates with tools like HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.
CI/CD Integration: Provides examples for GitHub Actions and GitLab CI to securely fetch and use secrets.
Best Practices: Enforces principles like regular rotation, least-privilege access, and secret scanning.

Quick Start

Use the secrets-management skill to store the API key 'my-api-key' in Vault under the path 'secret/api/credentials'.

Frequently Asked Questions about secrets-management

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

FAQPage Schema

How do I manage secrets in CI/CD pipelines without hardcoding them?▼

Secure secrets management in CI/CD pipelines uses tools like HashiCorp Vault and AWS Secrets Manager to store and retrieve sensitive credentials dynamically. This prevents hardcoding and integrates with GitHub Actions and GitLab CI for seamless secret injection.

What is the best way to integrate AWS Secrets Manager with GitHub Actions?▼

The best way to integrate AWS Secrets Manager with GitHub Actions is using a secrets management skill that securely fetches and injects credentials directly into your automated workflows. This enforces least-privilege access and prevents exposing sensitive data.

Can I use HashiCorp Vault for secret rotation in GitLab CI?▼

Yes, you can use HashiCorp Vault for secret rotation in GitLab CI. The skill implements secure storage, retrieval, and regular rotation of secrets, integrating seamlessly with GitLab CI to enforce best practices for handling sensitive credentials.

Does this secrets management approach support Azure Key Vault and Google Secret Manager?▼

Yes, this secrets management approach supports Azure Key Vault and Google Secret Manager alongside Vault and AWS Secrets Manager. It covers secure storage, retrieval, and rotation across these platforms for automated CI/CD workflows.

When do I need to rotate secrets in automated workflows?▼

You need to rotate secrets in automated workflows to enforce security best practices and limit exposure if credentials are compromised. Regular rotation, least-privilege access, and secret scanning are enforced by the skill managing your CI/CD pipelines.

Why does secret scanning matter for CI/CD pipelines?▼

Secret scanning matters for CI/CD pipelines because it identifies hardcoded sensitive credentials that bypass secure storage. The skill enforces scanning alongside least-privilege access and regular rotation to enhance security in automated workflows.