One-click install
npx skills add https://github.com/eforge-build/eforge --skill eforge-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eforge-init
Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-init
Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize eforge in the current project with an interactive setup flow to create and activate a tailored agent-runtime profile and configure team-wide settings.

Core Features & Use Cases

  • Interactive two-track setup (Quick or Mix-and-match) to assemble a named agent runtime profile under eforge/profiles and write eforge/config.yaml.
  • Reads project context (package.json, lockfiles) to suggest appropriate postMergeCommands and validation steps.
  • Supports a dedicated migration path (--migrate) to extract legacy fields into a named profile and clean config.yaml.
  • Automatically activates the new profile and exposes commands to manage profiles and configuration.

Quick Start

Run the eforge init command in your project to start the guided setup flow.

Frequently Asked Questions about eforge-init

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

FAQPage Schema
How do I set up an agent runtime profile in my project?

Guided project setup assembles a named agent runtime profile by reading package manifests to suggest validation steps, writing eforge/config.yaml, and storing profiles under eforge/profiles/.

How does interactive project initialization detect build commands?

Interactive project initialization detects build commands by reading package manifests like package.json and lockfiles within your project to suggest appropriate postMergeCommands and validation steps.

Can I migrate legacy configuration fields into a named profile?

Yes, you can migrate legacy configuration fields into a named profile using the dedicated migration path, which extracts legacy fields from config.yaml and cleans the file automatically.

Does the eforge setup require manual configuration of post-merge validation?

No, the setup does not require manual configuration of post-merge validation because it reads project context to suggest appropriate postMergeCommands and validation steps automatically.

What is the difference between Quick and Mix-and-match setup modes?

Quick and Mix-and-match setup modes both assemble a named agent runtime profile, but Mix-and-match provides deeper interactive configuration compared to the faster Quick track.