env-setup

Scan projects for required environment variables and write a validated .env file.

23|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tombensim/pi-wizard --skill env-setup-tombensim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-setup
Source: https://github.com/tombensim/pi-wizard/tree/main/examples/env-setup
Command: npx skills add https://github.com/tombensim/pi-wizard --skill env-setup-tombensim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken deployments and time-consuming setup by helping you detect, collect, validate, and write the correct environment variables and secrets for your project.

Core Features & Use Cases

  • Project scanning for env needs: Finds likely environment variables from .env templates, docker-compose files, and common code references like process.env and import.meta.env.
  • Interactive secure collection: Builds wizard steps dynamically per discovered service group and uses masked password fields for secrets.
  • Validation before writing: Tests database connectivity and performs lightweight API-key checks when possible, then writes a grouped .env file.
  • Safety guardrails: Avoids echoing secret values, preserves existing .env values where applicable, and updates .gitignore to protect secrets.

Quick Start

Run /env-setup in your Pi environment and follow the wizard prompts to scan your project, enter missing secrets, validate connections, and generate a secure .env file.

Frequently Asked Questions about env-setup

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

FAQPage Schema
How do I securely set up environment variables and secrets for a new project?

Secure environment variables setup involves scanning your project for required keys, collecting values via masked inputs, validating database and API connections, and writing a protected .env file. This prevents broken deployments by ensuring correct credentials are gathered safely without exposure.

Can I automatically detect required environment variables from docker-compose and code?

Yes, automatic environment variable detection scans .env templates, docker-compose files, and code references like process.env and import.meta.env. This dynamic scanning identifies required keys across service groups to build a comprehensive configuration profile.

What's the best way to validate database connectivity and API keys before writing a .env file?

The best way to validate database connectivity and API keys is using a validation-first approach that tests connections and performs lightweight checks before writing the .env file. This ensures only working credentials are saved, reducing setup failures.

Does interactive environment configuration mask password inputs to prevent secret exposure?

Yes, interactive environment configuration uses password-masked inputs to prevent secret exposure. The wizard generates steps dynamically per service group and enforces strict non-disclosure of secret values in outputs, keeping credentials hidden.

How do I protect secrets in .env files and update .gitignore automatically?

To protect secrets in .env files, the setup process applies safety guardrails that update .gitignore automatically and preserves existing .env values where applicable. This prevents sensitive credentials from being committed to version control.

When should I use an interactive wizard for dotenv configuration instead of manual entry?

Use an interactive wizard for dotenv configuration during app setup, onboarding, and workflow automation where correct credentials must be gathered without exposing sensitive data. It is especially useful when managing multiple service groups with validation requirements.