| name | magpie-setup-status |
| family | setup |
| mode | Meta |
| description | Show how the apache-magpie framework is adopted in the current
repo, then adjust that setup in place. Renders a Markdown
adoption dashboard: install method and pin, drift, the wired
agent targets, the installed skill families, and symlink health.
From the same view the user can add or drop agent targets and
skill families; the actual change runs through the setup skill.
|
| when_to_use | Invoke when the user asks how magpie is set up here, which
agent targets are wired, which skill families are installed, or
whether the snapshot is in sync. Also when the user wants to
change the wiring — add an agent target, enable the security or
pr-management family — and wants to see the current state first.
Phrases the user might say: "magpie status", "how is magpie
adopted", "which agent targets are wired", "show adoption
state", "which families are installed", "add the github target".
|
| capability | ["capability:stats","capability:platform"] |
| license | Apache-2.0 |
setup-status
Render a one-glance picture of how apache-magpie is adopted in
this repo, then let the user reconfigure it without leaving the
view. The dashboard answers the questions an operator actually
asks: which install method and version are pinned, has the
snapshot drifted, which agent targets are wired, which skill
families are installed, and are the symlinks healthy.
This skill is the configuration view of adoption. It is read-
only on its own; every change it offers is carried out by
delegating to /magpie-setup — the one skill
that owns adoption mutation. For a deep integrity / health
check (lock parsing, per-check ✓/✗ matrix, permission-hygiene
audit, ASF comdev MCP prerequisites, stale-worktree sweep), use
/magpie-setup verify; this skill links to
it rather than duplicating its checks.
Adopter overrides
Before running the default behaviour documented below, this skill
consults (in order, first hit wins):
.apache-magpie-local/setup-status.md — personal, gitignored..apache-magpie-overrides/setup-status.md — committed,
project-wide.
Both files are applied if present. See
docs/setup/agentic-overrides.md
for the full lookup contract.
Hard rule: agents NEVER modify the snapshot under
<adopter-repo>/.apache-magpie/. Local modifications go in the
override file. Framework changes go via PR to
apache/magpie.
Snapshot drift
Also at the top of every run, this skill compares the gitignored
.apache-magpie.local.lock (per-machine fetch) against the
committed .apache-magpie.lock (the project pin). On mismatch the
skill surfaces the gap and proposes
/magpie-setup upgrade. The proposal is
non-blocking; surfacing the drift is itself part of this skill's
dashboard, so the comparison feeds Step 1
rather than gating the run.
Inputs
Skill directives (how the user invokes the skill):
| Input | Effect |
|---|
| (none) | Render the dashboard, then offer adjustments interactively. |
--no-adjust |
