eforge-profile

> **Note:** In Pi, the native `/eforge:profile` command provides a richer interactive experience with TUI selector/panel profile browsing and switching. This skill serves as a fallback for non-interactive contexts and as model-readable documentation. # /eforge:profile List, inspect, and switch named agent runtime profiles stored in `.eforge/profiles/` (project-local scope), `eforge/profiles/` (project scope), or `~/.config/eforge/profiles/` (user scope). The active profile is tracked by a marker file at any level; resolution follows a 6-step precedence chain (see below). ## Workflow ### Step 1: Branch on arguments Inspect `$ARGUMENTS`: - If `$ARGUMENTS` is empty or whitespace, go to Step 2 (**inspect mode**). - Otherwise treat the argument as a profile name and go to Step 3 (**switch mode**). ### Step 2: Inspect mode Call the `eforge_profile` tool with `{ action: "show" }`. Parse the response (shape: `{ active, source, resolved: { harness, profile, metadata } }`) and report: - **Active profile**: `{active}` (or "(none - using team default)" when `active` is null) - **Source**: `{source}` (`local` when the active profile is picked via the `.eforge/.active-profile` marker, `project` when picked via the `eforge/.active-profile` marker, `missing` when the marker points at a profile file that does not exist (stale marker), `none` when no profile is configured at all) - **Resolved harness**: `{resolved.harness}` (e.g. `claude-sdk` or `pi`) - **Metadata** (when present in ...