env-editor

Document environment file conventions and variable overrides for the emergent.memory application.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/emergent-company/emergent.memory --skill env-editor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-editor
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/env-editor
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill env-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill clarifies the complex system of environment variable management within the emergent.memory project, preventing common configuration errors and security breaches.

Core Features & Use Cases

  • Defines conventions: Clearly outlines which .env files exist, their purpose, and their Git status.
  • Explains override rules: Details how environment variables are loaded and which files take precedence.
  • Lists key variables: Provides a comprehensive reference for workspace and server-specific environment variables.
  • Use Case: A new developer joins the emergent.memory project and needs to set up their local development environment. This Skill guides them on which variables to set in .env.local for secrets and local overrides, ensuring a smooth setup.

Quick Start

Consult the env-editor skill to understand how to set the POSTGRES_PASSWORD variable for the server.

Frequently Asked Questions about env-editor

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

FAQPage Schema
How do I set environment variables for emergent.memory local development?

To set environment variables for emergent.memory local development, use the `.env.local` file for secrets and local overrides, ensuring configurations do not get committed to Git.

What is the difference between .env and .env.local files?

The `.env` file provides base environment configurations while `.env.local` stores local overrides and secrets, with specific Git tracking rules determining which file takes precedence during loading.

Why are my environment variables not taking effect in Docker?

Environment variables not taking effect in Docker often indicate incorrect override rules or placement; troubleshooting steps include verifying variable references and ensuring the correct `.env` file precedence.

How do I prevent secrets from appearing in Git when using .env files?

To prevent secrets from appearing in Git, place sensitive values in `.env.local` and verify the Git status of environment files, using `.env.example` for tracking non-sensitive configuration templates.

What are the key workspace and server-specific variables needed for emergent.memory?

Key workspace and server-specific variables for emergent.memory include configurations like `POSTGRES_PASSWORD`, which are detailed in a comprehensive variable reference for proper server setup.

When do I need to use an .env.example file for development setup?

You need an `.env.example` file during development setup to provide a tracked template of required environment variables, allowing developers to understand necessary configurations without exposing actual secrets.