environment-secrets

Coordinate environment variables and secrets across development and production environments.

Updated Apr 18, 2026

Search Tags:#workflow #devops #security #configuration #environment-variables #secrets-management

Ready to run

npx skills add https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro --skill environment-secrets-mo7amed-mahmoud

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro --skill environment-secrets-mo7amed-mahmoud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate environment variables and secrets to prevent misconfigurations and data leaks.

Core Features & Use Cases

View environment variables and secrets across environments to understand current configuration.
Set non-sensitive environment values in the appropriate scope, and delete obsolete keys to prevent drift.
Request secrets or env vars from users when needed, ensuring sensitive data is never hardcoded.

Quick Start

Configure and manage environment variables and secrets across shared, development, and production environments.

Frequently Asked Questions about environment-secrets

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

FAQPage Schema

How do I manage environment variables and secrets across development and production?▼

You can manage environment variables and secrets across shared, development, and production scopes by applying view, set, and delete operations. This prevents misconfigurations and data leaks by ensuring controlled access and environment scoping.

What is the best way to prevent hardcoded secrets in my workflow?▼

To prevent hardcoded secrets in your workflow, you can use a request flow to prompt users for sensitive data when needed. This ensures sensitive values are never hardcoded and are securely handled during operations.

How does the request flow for sensitive environment variables work?▼

The request flow for sensitive environment variables works by prompting the user to supply secrets on demand via requestEnvVar. This mechanism applies safety checks to avoid exposing secrets during development and production workflows.

Can I delete obsolete environment variables to prevent configuration drift?▼

Yes, you can delete obsolete environment values to prevent configuration drift. Removing outdated keys across shared, development, and production scopes keeps your configuration current and reduces the risk of accidental exposure.

Does this secrets management approach apply to both development and production environments?▼

Yes, this secrets management approach applies to both development and production workflows requiring controlled access. It coordinates environment variables and secrets to prevent misconfigurations and data leaks across different scopes.

How do I view current environment variables and secrets without exposing sensitive data?▼

You can view environment variables and secrets across environments to understand your current configuration. The process implements safety checks to prevent exposing sensitive data while you review the settings.