Agent skill · security · rknall
GitLab Stack Secrets Manager
Manages Docker secrets for GitLab stack projects, ensuring secrets are never in .env or docker-compose.yml, properly stored in ./secrets directory, and securely integrated with Docker secrets. Use when users need to create secrets, migrate from environment variables, validate secret configuration, audit secret usage, or ensure secrets are never committed to git.
Why this skill is useful
Provides specific commands and workflows for managing Docker secrets in GitLab stack projects that the AI wouldn't reliably generate on its own.
What it needs
Requires docker installed locally. About 9k tokens when loaded. Last updated 2025-10-20. 58 stars on the source repository.
What this skill does
GitLab Stack Secrets Manager This skill manages secrets for GitLab stack projects, ensuring secrets are stored securely, never exposed in configuration files, and properly integrated with Docker secrets. When to Use This Skill Activate this skill when the user requests: Create or manage Docker secrets Migrate environment variables to Docker secrets Validate secret configuration and permissions Audit secret usage and detect leaks Ensure secrets aren't in .env or docker-compose.yml Check if secrets are exposed in git Generate secure random secrets Rotate existing secrets Fix secret-related security issues Core Security Principles CRITICAL RULES - Never violated: 1. No Secrets in .env: Secrets MUST NEVER be in .env file 2. No Secrets in docker-compose.yml: No plaintext secrets in environment variables 3. ./secrets Directory: All secrets in ./secrets with 700 permissions 4. Secret Files: Individual files with 600 permissions 5. Git Protection: ./secrets/ in .gitignore, never committed 6. Proper Ownership: All files owned by Docker user (not root) 7. Docker Secrets Only: Use Docker secrets mechanism exclusively Secret Management Workflow Phase 1: Understanding User Intent Step 1: Determine the Operation Ask yourself what the user wants to do: Create new secrets? Migrate existing environment variables to secrets? Validate current secret configuration? Audit secrets for leaks or issues? Update or rotate existing secrets? Remove secrets? Step 2: Gather Context 1. Check current project state: Does ./secrets directory exist? Does docker-compose.yml exist? Does .env file exist? Is this part of stack-validator findings? 2. Review docker-compose.yml: Any secrets already defined? Any environment variables that look like secrets? Which services need secrets? 3. Scan for security issues: Secrets in .env? Secrets in docker-compose.yml environment variables? Secrets tracked in git? Phase 2: Secret Creation When: User wants to create new secrets Step 1: Validate Prerequisites 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rknall/secrets-manager