golem-add-env-vars

Name: golem-add-env-vars
Availability: InStock
Author: Soham

Define environment variables for Golem agents with cascade precedence across manifest levels.

Updated May 17, 2026

Search Tags:#yaml #configuration management #environment variables #golem #agent presets #jinja templating #cli overrides

Ready to run

npx skills add https://github.com/Rust-soham/golem-claw --skill golem-add-env-vars-rust-soham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: golem-add-env-vars
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-add-env-vars
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-add-env-vars-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of configuring environment variables for Golem agents across many manifest layers without manually duplicating values or losing track of precedence.

Core Features & Use Cases

Cascade configuration: Define env values at component templates, components, agent types, and presets so more specific settings override/merge general ones.
Merge modes: Use envMergeMode (upsert, replace, remove) to control how child env maps combine with parent values.
Template substitution: Resolve {{ VAR_NAME }} expressions from the host environment during deploy for secure, environment-specific configuration.
Instance-level overrides via CLI: Pass --env KEY=VALUE to configure only a specific agent instance without changing the manifest.

Quick Start

Update your golem.yaml by adding env variables under the desired level (component template, component, agent type, or preset) and reference host values using {{ VAR_NAME }} when needed.

Frequently Asked Questions about golem-add-env-vars

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

FAQPage Schema

How do I configure environment variables for Golem agents across multiple manifest levels?▼

Environment variables for Golem agents are configured using a deterministic cascade precedence across component templates, components, agent types, and presets. More specific settings automatically override or merge with general ones, eliminating manual value duplication.

How does template substitution work for environment variables in YAML configuration?▼

Template substitution resolves strict Jinja-style {{ VAR_NAME }} expressions from the host environment during deployment. This provides secure, environment-specific configuration by injecting host values directly into your manifest at deploy time.

Can I override environment variables for a specific agent instance without modifying the manifest?▼

Yes, you can pass instance-level environment variable overrides via the CLI using the --env KEY=VALUE flag. This configures a specific agent instance without permanently changing the underlying manifest layers.

What are the requirements for discovering environment variable settings in a Golem manifest?▼

The manifest requires YAML frontmatter discovery fields to properly identify and apply environment variable configurations. These fields enable the system to locate and process env maps within the defined cascade levels.

What is the best way to manage environment-specific configuration across Golem agent presets?▼

The best way is defining env values at the preset level combined with deploy-time template substitution. This approach uses deterministic cascade precedence and envMergeMode semantics to ensure correct configuration overrides without duplication.