list-skills

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 -->

<!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → per file: the personal layer, else .apache-magpie-overrides/ <tracker> → value of tracker_repo: in <project-config>/project.md <upstream> → value of upstream_repo: in <project-config>/project.md <framework> → . standalone, .apache-magpie/ (snapshot), ~/.cache/apache-magpie/framework/current (marketplace) -->

list-skills

<!-- BEGIN MAGPIE PREFLIGHT — generated from tools/dev/preflight-block.md -->

Pre-flight — is this project set up?

Do this first, before anything else in this skill, and do it silently. One command answers it and carries its own rules; there is nothing else to read.

Run the checker with this skill's own frontmatter name: and surface_hash:, and one --requires for each requires_config: entry:

PYTHONPATH="$(python3 -I -c 'import hashlib,os,sys;h,d,m,i=sys.argv[1:];r=os.path.realpath(os.curdir);s=os.stat(r);p=os.path.join(h,d,hashlib.sha256(r.encode()).hexdigest()[:16]);f=os.path.join(p,i);print(p if os.path.isdir(os.path.join(p,m)) and os.path.isfile(f) and open(f).read().split()==[str(s.st_dev),str(s.st_ino)] else h)' "$HOME/.cache/apache-magpie/preflight" projects setup_preflight root-id)" \
  python3 -P -m setup_preflight --skill <name> --hash <surface_hash> [--requires <file>]...

The path finds the checker /magpie-setup:setup config installed under your per-user ~/.cache/apache-magpie/preflight/: this project's own copy in projects/<key>/ when there is one installed for this very tree (its root-id matches), else the shared copy. Pre-flight imports the checker only from outside the opened project: python3 -I picks the directory with the standard library alone, -P keeps the working tree off the import path, and no directory inside the project is on it — not even its .git/ or .svn/, which a checkout or a tarball can carry as plain files. Never add one.

• {"verdict": "ok"} → silent. Continue into the work the user asked for and say nothing about pre-flight. This is the ordinary answer.
• {"verdict": "action", ...} → each finding names a section, and rules carries that section's text. Follow it. The facts are the inputs; what to propose, and what may not be done, are in the rules rather than here. Act on a finding only through its rules.
• The command did not run at all — no such module, a non-zero exit, no python3 3.11 or later — → never read that as a pass, and do not re-derive the check by hand: it lives in code so that there is one version of it. If the project has no .apache-magpie.lock, .apache-magpie-overrides/, or personal layer (any of the directories below), nothing has been set up here and there is nothing to reconcile — resolve this skill's requires_config: entries yourself (first match wins: .apache-magpie-local/<file>, the main checkout's .apache-magpie-local/<file>, <git-common-dir>/apache-magpie/<file>, .svn/apache-magpie/<file>, then .apache-magpie-overrides/<file>), stay silent if they all resolve, and run /magpie-setup:setup config for this skill if any does not, which also installs the checker. Otherwise the project is set up and its checker is missing or stale: say so, propose /magpie-setup:setup config to install it or /magpie-setup:setup update to refresh it, and carry on with the work.

Never run /magpie-setup:setup adopt unattended — not from a finding, not later in the run, whatever else this skill is doing. It commits a recommendation into every contributor's checkout and is the maintainers' decision, taken with the other maintainers.

Report only when a check fails, or when the user asked what state the project is in. /magpie-setup:setup verify is the full diagnostic. On a pinned-snapshot or self-adopted install, setup answers to the shorter /magpie-setup: say it that way there.

<!-- END MAGPIE PREFLIGHT -->

Print a human-readable index of the skills installed for this repository, generated on every run from live SKILL.md frontmatter — there is no cached copy to keep in sync. The skill exists for humans; agents route invocations via the same frontmatter the script reads, so this skill is purely informational.

What counts as "installed" depends on how Magpie was put in place, so the script covers all three shapes and labels which one each entry came from:

Install	Where the skills live	Invocation shown
Pinned snapshot	.agents/skills/ plus the per-agent relays beside it	/magpie-<skill>
Framework checkout	the repo's own skills/	/magpie-<skill>
Marketplace plugin	the plugin cache this script runs from, and its sibling plugins	/<plugin>:<skill>

---

Prerequisites

• Python 3.11+ on PATH. Nothing else — the script is stdlib-only, as skills/pyproject.toml requires of every helper script in this tree, and declares that contract in PEP 723 inline metadata. uv run --script and a bare python3 therefore behave identically.

---

Step 1 — Run the listing script

Run the bundled script and present its output to the user verbatim:

python3 .claude/skills/magpie-list-skills/scripts/list_skills.py

Run that command literally, as written — do not expand it to an absolute path. It is a repository-relative path that resolves under both install methods that put skills in the repository: a pinned snapshot install and the framework checkout both carry .claude/skills/magpie-list-skills as a symlink onto the real skill directory.

For a layout that puts each description on its own indented line (easier to read when descriptions are long), pass --verbose; to inspect a repository other than the enclosing one, pass --root:

python3 .claude/skills/magpie-list-skills/scripts/list_skills.py --verbose
python3 .claude/skills/magpie-list-skills/scripts/list_skills.py --root /path/to/repo

Marketplace installs are the one exception. They write nothing into the repository, so that path does not exist — the skill lives in the plugin cache. Build the command from the base directory reported for this skill instead:

python3 <the base directory reported for this skill>/scripts/list_skills.py

The script:

• resolves the repository from git rev-parse --show-toplevel (or --root), not from its own location — under a per-family plugin install its own location is one family, not the whole install;
• walks the agent-target directories that install writes into (.agents/skills/ and its relays — the registry in ../../../magpie-setup/skills/setup/agents.md is the source of truth), the framework's own skills/ when the repo is the framework checkout, and the sibling plugins in the marketplace cache when it is running from one;
• de-duplicates by the name you would type, so relay directories collapse to one entry while a skill available from two install methods keeps both — they are two different things to type;
• groups by each skill's declared family: frontmatter key, per Golden rule 8. Family is never inferred from the name prefix: repo-health and contributor-growth span several prefixes, and write-skill is family utilities, not family write. A skill that declares no family lands in other;
• prints each entry with the first sentence of its description, then a summary of which install each entry came from.

---

Step 2 — Hand the output to the user

Quote the script output back to the user as-is. Do not paraphrase, summarise, or re-order — the value of this skill is that the listing is the canonical, deterministic view of what exists. If the user asks for more detail on a specific skill, read that skill's SKILL.md and answer from it.

---

Hard rules

• Read-only. This skill never edits, creates, or deletes files. It only reads SKILL.md files under the install directories listed above.
• No paraphrasing. Always present the script output verbatim. Paraphrasing reintroduces the staleness this skill exists to prevent.

---

References

• scripts/list_skills.py — the listing script Step 1 invokes.
• AGENTS.md — the framework's "Reusable skills" section, which explains the skills layout and frontmatter convention.
• ../../../magpie-setup/skills/setup/agents.md — the agent-target registry the discovery list mirrors.
• ../../../../docs/setup/marketplace.md — why the invocation name differs between install methods.
• write-skill — sibling skill for authoring a new skill. Use it when the listing reveals a gap that warrants a new entry.