environment-secrets

View, set, and delete environment variables across shared, development, and production environments.

Updated Aug 4, 2025
One-click install
npx skills add https://github.com/nirajrathod19/Inlytix_BI --skill environment-secrets-nirajrathod19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/nirajrathod19/Inlytix_BI/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/nirajrathod19/Inlytix_BI --skill environment-secrets-nirajrathod19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the management of sensitive and non-sensitive configuration data, ensuring secure handling of API keys, tokens, and other critical variables.

Core Features & Use Cases

  • View Variables: Inspect existing environment variables and secrets across different environments (shared, development, production).
  • Set Variables: Define or update non-sensitive environment variables.
  • Request Secrets: Securely prompt users for sensitive information like API keys.
  • Use Case: Before deploying an application, use this skill to check if all necessary API keys are set, and if not, request them from the user.

Quick Start

Request the 'OPENAI_API_KEY' secret from the user.

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 API keys across development and production environments?

Managing environment variables and API keys across development, production, and shared environments involves viewing, setting, and deleting configuration data. You can inspect existing variables and securely request sensitive tokens from users during deployment.

What is the best way to securely collect API keys and tokens from users before deployment?

Securely collecting API keys and tokens requires prompting users directly for sensitive information. This approach prevents hardcoding secrets into configuration files, ensuring sensitive data is retrieved safely and managed across environments.

Can I view and update non-sensitive configuration data for application deployment?

Viewing and updating non-sensitive configuration data is fully supported for application deployment. You can inspect existing environment variables across shared, development, and production environments, and define or update non-sensitive values as needed.

Does this approach separate sensitive secrets from standard environment variables?

This approach separates sensitive secrets from standard environment variables by handling them differently. Non-sensitive variables are set directly, while sensitive secrets like API keys are securely requested from the user through dedicated introspection and collection functions.

How do I check if all necessary API keys are set before deploying an application?

Checking if necessary API keys are set before deployment involves listing existing environment variables. If any required API keys or tokens are missing, you can then securely prompt the user to provide the missing sensitive information.