environment-secrets

Manage environment variables and secrets in Replit across shared, development, and production environments.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/matheusz-nied/stay-hard-motivation --skill environment-secrets-matheusz-nied
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/matheusz-nied/stay-hard-motivation/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/matheusz-nied/stay-hard-motivation --skill environment-secrets-matheusz-nied

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

  • View, set, and delete environment variables across shared, development, and production contexts.
  • Request secrets securely from users using requestEnvVar to avoid exposing sensitive data.
  • Environment scoping to manage shared, development, and production vars independently.
  • Use cases include auditing configurations, rotating credentials, and onboarding new projects.

Quick Start

Request missing secrets from the user and configure non-sensitive environment variables using setEnvVars.

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 across development and production environments in Replit?

You can manage environment variables by viewing, setting, and deleting secrets across shared, development, and production environments in Replit. This ensures proper environment scoping for auditing configurations and onboarding projects.

What is the best way to request sensitive API keys from users without hardcoding them?

The best way to request sensitive API keys is using the requestEnvVar mechanism. This securely requests secrets directly from users, avoiding direct hardcoding and preventing sensitive data exposure during configuration.

Can I configure non-sensitive environment variables while securely requesting secrets for my application?

Yes, you can configure non-sensitive environment variables using setEnvVars while simultaneously using requestEnvVar to securely obtain sensitive secrets from users. This separation enforces configuration best practices.

Does the Replit secrets tab support changing environment variable values directly?

Yes, the Replit secrets tab supports changing environment variable and secret values directly. You can use the GUI tab to modify values alongside programmatic environment scoping and management operations.

When do I need to rotate credentials and how can environment scoping help?

You need to rotate credentials during security audits or key compromises. Environment scoping helps by allowing you to independently update development and production secrets, ensuring rotated keys do not disrupt unrelated environments.