...
npx skills add https://github.com/subinium/vibesubin --skill manage-secrets-env
Please help me install this Agent Skill. Skill: manage-secrets-env Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/manage-secrets-env Command: npx skills add https://github.com/subinium/vibesubin --skill manage-secrets-env
Opinionated defaults and full lifecycle playbook for secrets and environment variables. Decides where a secret or env-specific value lives (constant, .env, CI secret, env var), scaffolds .env.example and .gitignore, and manages the lifecycle end to end — add, update, rotate, remove, migrate between buckets, audit cross-environment drift, provision new environments. High-stakes companion to project-conventions. Language-agnostic.
Invoke the manage-secrets-env skill to scaffold a baseline environment and enforce end-to-end secret lifecycle across your project.
High-intent search queries and answers about installing and using this skill.
Secrets and environment variables are sorted using a four-bucket decision model: constants, .env files, CI secret stores, and environment variables. This model determines where a value lives based on its sensitivity and target environment, preventing misconfiguration and accidental leakage.
To prevent secret leakage during environment scaffolding, generate baseline .env.example files and enforce strict .gitignore rules. Startup validation then checks that all required environment variables are present and correctly configured before the application fully initializes.
Cross-environment drift is audited by running a dedicated audit workflow that compares secrets and environment variables across development, staging, and production. This ensures consistency and compliance by identifying missing, mismatched, or outdated configurations between environments.
Yes, you can rotate and migrate secrets between local .env files and CI secret stores. The lifecycle management supports add, update, rotate, remove, and migrate workflows, allowing values to move between buckets as security requirements change.
Yes, this secrets lifecycle management approach is language-agnostic. It provides opinionated defaults for managing environment variables and secrets without relying on language-specific libraries, applying consistent rules across any project stack.
chad3814Define global project conventions for structure, documentation, and environment configuration.
vitorsilvaAutomate GitHub Actions workflow creation and deployment pipeline management across environments.
TibsfoxManage environment variables and secrets with startup-time config validation.
iceflowerAutomates secret lifecycle management across Kubernetes, CI/CD pipelines, and multi-cloud environments with rotation and leak detection.
