setup-env

Generate .env.example, .env.local, and validate-env.sh from architecture blueprints.

2|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill setup-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-env
Source: https://github.com/navraj007in/architecture-cowork-plugin/tree/main/skills/setup-env
Command: npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill setup-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of production-ready environment variable files by extracting required values from your architecture blueprint, enabling quick project setup and secure secret management.

Core Features & Use Cases

  • Environment templates: .env.example and .env.local with all variables, comments, and safe defaults
  • Validation script: validate-env.sh to verify configuration completeness and spot missing keys
  • Guided provisioning: provides links and instructions to obtain API keys and service credentials for integrations

Quick Start

Use the /architect:setup-env command to generate .env.example, .env.local, and validate-env.sh from your architecture blueprint, then customize .env.local with actual keys and run the validation script before starting development.

Frequently Asked Questions about setup-env

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

FAQPage Schema
How do I generate environment variable templates from an architecture blueprint?

To generate environment variable templates, this skill extracts required values from your architecture blueprint and outputs .env.example, .env.local, and a validate-env.sh script for immediate project setup.

What is the best way to manage environment variables across development, staging, and production?

Managing environment variables across workflows requires templates with safe defaults and comments. This skill generates .env files and a validation script to ensure configuration completeness and secure secrets management across environments.

How do I validate missing API keys in my .env file before deployment?

You validate missing API keys by running the generated validate-env.sh script. It verifies configuration completeness, spots missing keys in your .env.local file, and ensures your secrets management setup is ready for deployment.

Can I use this to get links for provisioning API keys and service credentials?

Yes, you can use this for provisioning API keys. It provides guided provisioning by outputting direct links and instructions to obtain necessary API keys and service credentials for your project integrations.

Does this work for developer onboarding in new projects?

Yes, this works for developer onboarding in new projects. It automates environment setup by generating repeatable .env templates and validation scripts, enabling quick, secure configuration for new developers.