environment-secrets

Manage environment variables and request secrets from users on Replit.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/BotchaVarun/EduBot --skill environment-secrets-botchavarun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/BotchaVarun/EduBot/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/BotchaVarun/EduBot --skill environment-secrets-botchavarun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applications need API keys, tokens, and configuration values that must never be hardcoded into source code. This Skill lets an agent inspect, set, and delete environment variables across shared, development, and production scopes, and securely request secrets from the user without ever exposing their values. ## Core Features & Use Cases - View configuration: Check which environment variables and secrets exist, filtered by type, environment, or specific keys. - Set and delete env vars: Manage non-sensitive configuration (ports, feature flags, log levels) scoped to shared, development, or production environments. - Request secrets from users: Pause execution and prompt the user for API keys or tokens via requestEnvVar, so sensitive values are never set directly by the agent. - Use Case: Before enabling a payment feature, check whether STRIPE_SECRET_KEY exists; if missing, request it from the user, then set non-sensitive config like PAYMENTS_ENABLED=true in the shared environment. ## Quick Start Check which environment variables and secrets are currently configured, then request any missing API keys from me.

Frequently Asked Questions about environment-secrets

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

FAQPage Schema
How do I check which environment variables and secrets exist?▼

Use viewEnvVars to list environment variables and secrets, optionally filtering by type (env or secret), environment (shared, development, production), or specific keys. Secret values are never shown, only their existence status.

How do I securely add an API key to my Replit app?▼

Request the API key from the user with requestEnvVar using requestType "secret" and the required keys. The agent pauses until the user provides the value, and secrets can never be set directly by the agent.

What is the difference between shared, development, and production environments?▼

Shared variables are available in both development and production, while development and production variables apply only to their respective environments. A variable in shared cannot also exist in a specific environment; delete it from shared first to move it.

Can the agent view or modify secret values directly?▼

No. The agent can only check whether a secret exists, never read its value, and cannot set or modify secrets programmatically. Secrets must be provided by the user through requestEnvVar or the Replit secrets tab.

Why can't I modify certain environment variables like REPLIT_DOMAINS?▼

Runtime-managed variables such as REPLIT_DOMAINS, REPL_ID, and DATABASE_URL for Helium databases are controlled by the platform and cannot be modified. Attempting to change them is explicitly prohibited.