golem-profiles-and-environments

Resolve Golem CLI profile, environment, and preset selection rules for deployment configuration.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-profiles-and-environments-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-profiles-and-environments
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-profiles-and-environments
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-profiles-and-environments-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the confusion of how Golem CLI profiles, app environments, and preset configuration interact so you can reliably target the right server and apply the correct environment-specific settings.

Core Features & Use Cases

  • Clarifies configuration layers: explains how CLI Profiles (connection/auth) are resolved and how App Environments (deployment targets) select and merge Component/Agent Presets (configuration overrides).
  • Helps you avoid misconfiguration: documents where fields like server, account, componentPresets, cli, and deployment belong in golem.yaml, and how selection works via default, flags, and fallbacks.
  • Supports practical deployment scenarios: guides choosing between local/cloud/custom servers, managing tokens/OAuth2, and designing presets for local vs cloud behavior (e.g., env vars, build commands, plugins, files, and agent config).

Quick Start

Ask: Explain how to select the correct app environment and presets when deploying my Golem manifest, and what CLI profile settings will be used for server connection and authentication.

Frequently Asked Questions about golem-profiles-and-environments

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

FAQPage Schema
How do Golem CLI profiles interact with app environments for deployment configuration?

Golem CLI profiles handle server connection and authentication, while app environments in golem.yaml select and merge component or agent presets to determine deployment configuration. Profiles resolve connectivity, and environments apply target-specific settings.

How do I select a named environment and override presets when deploying a Golem manifest?

To select a named environment for Golem deployment, use CLI flags to override the default environment specified in golem.yaml. This triggers the selection and merge of component or agent presets, applying the correct configuration overrides for your target.

What is the connection resolution order between environment server settings and CLI profiles in Golem?

Connection resolution in Golem checks environment server settings from golem.yaml first, then falls back to the active CLI profile. This order ensures deployment targets can specify custom servers while profiles provide default connection and authentication details.

Where do fields like server, account, and componentPresets belong in golem.yaml?

In golem.yaml, server and account belong under CLI profile settings for connection, while componentPresets belong under app environments. Deployment fields map configuration overrides that activate based on the selected environment and preset merge semantics.

Can I configure different Golem presets for local versus cloud deployment targets?

Yes, Golem supports designing presets for local versus cloud behavior within app environments. You can configure environment variables, build commands, plugins, and agent config in golem.yaml to apply specific settings based on your selected deployment target.

Why are my Golem deployment presets not applying the correct environment variables?

Golem deployment presets may not apply correctly if environment selection rules clash with CLI flag overrides. Verify your default environment in golem.yaml and check preset merge semantics to ensure component or agent configuration overrides resolve as intended.