skills.rest
gopaljilab
gopaljilabCOMMUNITY
Explore all skills by this author →
GitHub

environment-secrets

Manage environment variables and request secrets from users on Replit.

Updated Mar 6, 2026
Search Tags:#security#configuration#secrets management#environment variables#api keys#replit
One-click install
npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill environment-secrets-gopaljilab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/gopaljilab/Gupta-Portfolio/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill environment-secrets-gopaljilab

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 provides a safe way to view, set, and delete environment variables and to request secrets directly from users without exposing sensitive values. ## Core Features & Use Cases - View Configuration: Inspect existing environment variables and check which secrets are configured across shared, development, and production environments. - Set and Delete Variables: Manage non-sensitive configuration values scoped to specific environments. - Request Secrets Securely: Pause execution and prompt the user for API keys or tokens, so sensitive values are never written by the agent. - Use Case: When building a feature that calls the OpenAI API, first check whether OPENAI_API_KEY exists, then request it from the user if missing, and set related config like MAX_TOKENS as a shared environment variable. ## Quick Start Check which environment variables and secrets are currently configured, then request any missing API keys 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 request an API key from a user in Replit?▼

Use the requestEnvVar function with requestType set to "secret" and a list of keys such as OPENAI_API_KEY. Execution pauses until the user provides the values, so secrets are never hardcoded by the agent.

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". Shared variables apply to both environments, while environment-specific ones override per environment.

Can I view the value of a stored secret?▼

No, secret values cannot be viewed, only their existence status. The viewEnvVars function returns which secrets are configured, but never exposes their actual values.

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

A variable stored in the shared environment cannot also exist in development or production. Delete it from shared first, then re-add it separately to the specific environments.

Which 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 itself.

Related Skills

Explore More Software Engineering Skills→
sgcarstrendssgcarstrends
21

env-config

Manage environment variables and secrets across dev, staging, and prod with SST integration.

Official
Intermediate
hajrasarwar11hajrasarwar11

integrations

Discover, authorize, and wire OAuth integrations within Replit environments.

Community
Advanced
M2AI-jpM2AI-jp

deploy-checker

Automate deployment readiness checks for CI/CD and Vercel projects.

Community
Intermediate
wesleyegbertowesleyegberto
3

secrets-management

Manage and rotate credentials in CI/CD pipelines with HashiCorp Vault and cloud secret managers.

Community
Advanced