environment-secrets

Manage environment variables and secrets across shared, development, and production scopes.

20|8|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/1uc4sm4theus/master-zap --skill environment-secrets-1uc4sm4theus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/1uc4sm4theus/master-zap/tree/main/Master-Zap/.local/skills/environment-secrets
Command: npx skills add https://github.com/1uc4sm4theus/master-zap --skill environment-secrets-1uc4sm4theus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing sensitive configuration data and environment variables without hardcoding them, ensuring security and operational flexibility across development and production environments.

Core Features & Use Cases

  • Environment Management: View, set, and delete environment variables across shared, development, and production scopes.
  • Secret Handling: Request and manage sensitive API keys and tokens securely through user prompts rather than direct storage.
  • Use Case: When deploying a new feature that requires an external API key, use this skill to check if the key exists and, if missing, prompt the user to provide it securely before proceeding with the configuration.

Quick Start

Use the environment-secrets skill to request the missing OPENAI_API_KEY from the user and then set the DEBUG environment variable to false in the shared environment.

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 across development and production scopes?

You can manage environment variables by viewing, setting, and deleting them across shared, development, and production scopes to ensure environment-specific application settings are maintained securely.

What is the best way to securely handle API keys and secrets during deployment?

Secure secret handling is achieved by pausing execution to request credentials directly from the user, preventing the need to hardcode sensitive API keys and tokens in your configuration files.

Can I check if a required environment variable exists before running configuration?

Yes, you can view existing environment variables to verify if a required key exists, and if it is missing, securely prompt the user to provide it before proceeding with the setup.

How do I set environment variables for specific scopes like shared or production?

You can set environment variables by targeting specific scopes such as shared, development, or production, ensuring that configuration data is applied only to the appropriate operational environment.

Why should I avoid hardcoding sensitive configuration data in my application?

Avoiding hardcoded configuration data solves the challenge of managing sensitive secrets, ensuring operational flexibility and security across different development and production environments without exposing credentials.