environment-secrets

View, set, delete, and request environment variables and secrets across environments.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Celia-12/Proyecto-Mern --skill environment-secrets-celia-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/Celia-12/Proyecto-Mern/tree/main/frontend/.local/skills/environment-secrets
Command: npx skills add https://github.com/Celia-12/Proyecto-Mern --skill environment-secrets-celia-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage environment variables and secrets (such as API keys, tokens, and credentials). View, set, delete environment variables and request secrets from users.

The user can also change the values of any environment variables/secrets using the "secrets" tab in the Replit GUI.

Core Features & Use Cases

  • viewEnvVars(type, environment, keys)
  • setEnvVars(values, environment)
  • deleteEnvVars(keys, environment)
  • requestEnvVar(requestType, keys, envVars, userMessage)
  • Environment scoping: shared, development, production; secrets are global

Quick Start

Begin by inspecting current variables with viewEnvVars(), then set non-sensitive values with setEnvVars or request secrets with requestEnvVar as your needs dictate.

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 secrets in Replit?

Manage environment variables and secrets in Replit by viewing, setting, and deleting values across development and production environments. You can also request secret values directly from users or change them via the Replit secrets tab.

Can I set environment variables for specific environments like production?

Yes, you can set environment variables for specific environments using environment scoping. The Skill supports shared, development, and production environments, while secrets remain global across all scopes.

What is the best way to securely request API keys and credentials from users?

Securely request API keys and credentials by using a request function that prompts users for values. This ensures secrets are handled safely without exposing them in logs or runtime-managed variables.

Why should I avoid modifying runtime-managed environment variables?

Avoid modifying runtime-managed environment variables to prevent breaking application logic. The Skill provides safety guidance to protect secrets and ensure only appropriate, non-runtime variables are updated or deleted.

Does this Skill work with environment scoping for both development and production?

Yes, the Skill works with environment scoping for development, production, and shared environments. You can view, set, and delete environment variables per environment, while secrets are managed globally.