skills.rest
eforge-build
eforge-buildOFFICIAL
Explore all skills by this author →
WebsiteGitHub

eforge-config

Configure team-wide eforge settings in eforge/config.yaml with daemon validation.

69|4|Updated Mar 15, 2026
Search Tags:#validation#yaml#config#configure#profile#daemon#eforge
One-click install
npx skills add https://github.com/eforge-build/eforge --skill eforge-config
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eforge-config
Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-config
Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize or edit eforge/config.yaml team-wide settings with daemon-backed validation to ensure consistency across projects.

Core Features & Use Cases

  • Initialize and modify the global team configuration at project root
  • Validate changes via the eforge daemon before applying
  • Guided, interview-style prompts to tailor settings without exposing harness-specific controls

Quick Start

Follow the interactive prompt to initialize or edit eforge/config.yaml for your project.

Frequently Asked Questions about eforge-config

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

FAQPage Schema
How do I initialize team-wide eforge settings from a single config file?▼

To initialize team-wide eforge settings, use the interactive init mode to generate eforge/config.yaml at your project root. The daemon validates the configuration before applying it, ensuring consistency across projects.

What is the best way to edit eforge/config.yaml safely without breaking validation?▼

The best way to edit eforge/config.yaml is through the interactive edit mode, which uses guided prompts and daemon-backed validation. This prevents invalid configurations and enforces no harness-specific top-level keys.

Does eforge config validation support harness-specific top-level keys?▼

No, eforge config validation does not support harness-specific top-level keys. The daemon explicitly rejects them to maintain a clean, team-wide configuration profile tailored to eforge projects.

Can I configure eforge daemon settings without exposing harness-specific controls?▼

Yes, you can configure eforge daemon settings safely using interview-style interactive prompts. This guided approach tailors your profile without exposing or allowing harness-specific controls in the config file.

Why does my eforge config.yaml fail validation when I add custom keys?▼

Your eforge config.yaml fails validation if it contains harness-specific top-level keys or invalid profiles. The eforge_config tool strictly validates the structure and rejects unsupported configurations to ensure team-wide consistency.

Related Skills

Explore More Software Engineering Skills→
eforge-buildeforge-build
69

eforge-init

...

Official
Advanced
mistakeknotmistakeknot
3

config

Enforce project-wide engineering conventions, settings hygiene, and Git workflows.

Community
Basic
eforge-buildeforge-build
69

eforge-build

Enqueue PRD files or inline descriptions for the eforge daemon to build.

Official
Advanced
eforge-buildeforge-build
69

eforge-profile-new

Create named eforge agent runtime profiles via interactive prompts and YAML generation.

Official
Advanced