secrets-management

Centralize, rotate, and audit secrets in CI/CD pipelines.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill secrets-management-sumeet138
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/cicd-automation/skills/secrets-management
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill secrets-management-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secure secrets management in CI/CD pipelines to prevent exposure of credentials and enable automated rotation across platforms.

Core Features & Use Cases

  • Centralized secrets management across Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.
  • Automatic rotation, fine-grained access control, and audit logging to ensure compliance.
  • Seamless integration with GitHub Actions, GitLab CI, and other runners to inject credentials at runtime.

Quick Start

Configure your CI workflow to fetch credentials from Vault, AWS Secrets Manager, or GitHub secrets and inject them into your deployment steps.

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 securely in CI/CD pipelines across different platforms?

Secure secrets management in CI/CD pipelines centralizes credentials using Vault, AWS Secrets Manager, Azure Key Vault, or Google Secret Manager to prevent exposure and enable automated rotation across platforms.

Can I integrate AWS Secrets Manager and Vault with GitHub Actions?

Yes, you can integrate AWS Secrets Manager and Vault with GitHub Actions. The system fetches credentials at runtime and injects them directly into your deployment steps for seamless repository workflow integration.

How does automated credential rotation work for CI/CD secrets?

Automated credential rotation for CI/CD secrets works by centralizing lifecycle management, enabling dynamic secrets, and automatically updating credentials without manual intervention to ensure compliance and continuous security.

What is the best way to audit and control access to credentials in GitLab CI?

The best way to audit credentials in GitLab CI is using centralized secrets management with fine-grained access control and audit logging, ensuring compliance while injecting credentials securely at runtime.

Does this approach support dynamic secrets for Azure Key Vault and Google Secret Manager?

Yes, the approach supports dynamic secrets for Azure Key Vault and Google Secret Manager, enabling centralized lifecycle management, fine-grained access control, and audit logging across your CI/CD workflows.