golem-edit-manifest

Edit Golem Application Manifest files while preserving schema and merge semantics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing a Golem Application Manifest (golem.yaml) is error-prone because many sections must follow a strict schema and cascade/merge rules.

Core Features & Use Cases

  • Explain manifest structure: Covers top-level fields like manifestVersion, includes, componentTemplates, components, agents, environments, httpApi, mcp, bridge, customCommands, clean, secretDefaults, retryPolicyDefaults, and resourceDefaults.
  • Guide cascade and merge behavior: Documents how componentTemplates → components → agents → presets combine properties using merge modes for env, wasiConfig, plugins, files, and build.
  • Support common edit patterns: Shows how to add components, set env vars, install plugins, define environments, configure HTTP/MCP deployments, and add clean paths.

Quick Start

Use the golem-edit-manifest skill to update your golem.yaml by changing the component, agent, environment, and preset sections while preserving the correct merge modes and the existing manifestVersion.

Frequently Asked Questions about golem-edit-manifest

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

FAQPage Schema
How do I safely edit golem.yaml without breaking the schema?

To safely edit golem.yaml, modify components, agents, and environments while preserving the manifestVersion and adhering to documented field scopes and cascade merge modes to maintain correct structure.

How does the cascade merge behavior work for Golem Application Manifest components?

The cascade merge behavior combines properties from componentTemplates to components, agents, and presets using specific merge modes for env, wasiConfig, plugins, files, and build configurations.

Can I configure HTTP and MCP deployments directly inside golem.yaml?

Yes, you can configure HTTP and MCP deployments directly inside golem.yaml by modifying the httpApi and mcp sections while maintaining the required manifest schema structure.

What naming conventions are required for agents and components in golem.yaml?

Agents in golem.yaml must use PascalCase naming conventions, while components must follow a namespace:name format to align with the required manifest schema structure.

Why are my golem.yaml presets overriding agent environment variables unexpectedly?

Golem.yaml presets may override agent environment variables unexpectedly due to incorrect cascade merge modes, requiring you to verify how componentTemplates, components, agents, and presets combine properties.

Does golem.yaml support setting default retry policies and resource quotas?

Yes, golem.yaml supports setting default retry policies and resource quotas by modifying the retryPolicyDefaults and resourceDefaults sections while preserving the correct manifest schema structure.