jelly-dotenv

Environment variables for jelly skills are centralized through a single .env configuration file. jelly-dotenv loads variables from jelly-dotenv/.env first, then falls back to your project root .env, merging settings without overwriting existing values unless explicitly overridden.

jelly-dotenv provides auto-load behavior for both shell sourcing and Node.js require() statements. It handles priority-based loading with fallback logic, supports quoted values and comments, and exports credentials directly to process.env for immediate access.

Yes. jelly-dotenv implements a fallback architecture where skills first check jelly-dotenv/.env for shared configuration, then defer to project-specific .env files, creating a single source of truth for API keys while allowing project-level overrides.

jelly-dotenv includes templates and setup scripts for rapid onboarding. Create a .env file following the provided template, place it in jelly-dotenv/ or your project root, and the Skill automatically loads variables with comment and quote support.

jelly-dotenv uses a defined fallback order: it checks jelly-dotenv/.env first, then project root .env. If variables remain absent after both lookups, they stay undefined; the Skill loads what's available without throwing errors on missing values.

Yes. jelly-dotenv merges settings without overwriting existing variables by default, so your current project .env is respected. You can override specific values when needed by setting them explicitly in jelly-dotenv/.env.