environment-secrets

Manage environment variables and request secrets from users on Replit.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/AmirEmad11/instabot --skill environment-secrets-amiremad11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/AmirEmad11/instabot/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/AmirEmad11/instabot --skill environment-secrets-amiremad11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring applications requires managing environment variables and API keys, but hardcoding secrets is insecure and tracking which variables exist across development and production environments is error-prone. ## Core Features & Use Cases - View and Inspect Configuration: Check which environment variables and secrets exist, filtered by environment (shared, development, production) or specific keys. - Set and Delete Variables: Programmatically manage non-sensitive configuration values scoped to the correct environment. - Secure Secret Requests: Pause execution and request API keys, tokens, or credentials directly from the user instead of hardcoding them. - Use Case: When building a feature that needs an OpenAI API key, first check if it exists with viewEnvVars, then request it from the user via requestEnvVar if missing, and set related config like MAX_TOKENS as a shared environment variable. ## Quick Start Ask the agent to check whether the OPENAI_API_KEY secret exists and request it from you if it is missing.

Frequently Asked Questions about environment-secrets

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

FAQPage Schema
How do I request an API key from the user in Replit?

Use the requestEnvVar function with requestType set to "secret" and provide the list of secret keys you need. The agent pauses execution until the user provides the values, so secrets are never hardcoded in code.

How do I set environment variables for development and production?

Use setEnvVars with a values dictionary and an environment parameter of "shared", "development", or "production". Variables in "shared" apply to both environments and cannot be overridden per-environment without deleting them first.

Can I view the value of a stored secret?

No, secret values cannot be viewed for security reasons. The viewEnvVars function only returns whether a secret exists, showing keys mapped to boolean existence status rather than actual values.

Why can't I modify a shared environment variable in development?

A variable stored in the shared environment cannot be modified in development or production directly. You must delete it from shared first, then re-add it separately to the development and production environments.

What environment variables cannot be modified?

Runtime-managed variables such as REPLIT_DOMAINS, REPL_ID, and DATABASE_URL for Helium databases cannot be modified. These are controlled by the platform and are excluded from set and delete operations.