Utilities skill family
September 13, 2026 · View on GitHub
Scope. Works on any project, ASF or not — no Apache-Software-Foundation-specific assumptions baked in.
Framework meta-skills — the tools you use to build and maintain skills themselves, rather than to run a maintainership mode on your project. They sit outside the MISSION mode taxonomy (Agentic Triage, Agentic Mentoring, Agentic Drafting, Agentic Pairing, Agentic Autonomous): nothing here acts on your issues, PRs, or contributor threads. They are for skill authors and framework contributors.
Tip
Why this family
- See what is installed here and what the marketplace has that you have not taken
- Author a new skill against the framework's conventions, including the eval suite that keeps it working
- Report a framework bug from where you hit it, after checking nobody has already filed it
Install & first runs
Install just this family — one plugin, 5 skills. Framework meta-skills: author, restructure, and index your own skills.
Once you have added the marketplace:
/plugin install magpie-utilities@apache-magpie
New to Magpie? The quick start walks the whole path in
one place — install, the first /magpie-setup run, and a recording of it
happening — plus the other agents and the secure-isolation setup to run next.
Before the first run
Nothing here has to be configured. These skills read the file below
when it exists — yours in .apache-magpie-local/ or the project's in
.apache-magpie-overrides/ — and fall back to a documented default when
it does not.
Optional. Each has a documented fallback; absent, the skill still runs.
| File | What it carries | Read by |
|---|---|---|
project.md | Project manifest. Identity, repositories, mailing lists, tools enabled, CVE tooling, GitHub project-board + issue-template field declarations. The single file every skill reads to resolve project-scoped references. | list-skills, optimize-skill, report-framework-issue, skill-reconciler, write-skill |
Works well with
Third-party packages, none of them required: this family works with none of them installed, and Magpie neither bundles nor depends on any. They are named because they are what a maintainer goes looking for next, and because the answer differs by agent.
Superpowers — obra (community)
A skills library and development methodology: brainstorming, plan writing, subagent-driven execution, systematic debugging.
With this family: write-skill and optimize-skill author Magpie skills; Superpowers' brainstorming and plan-writing skills are the discipline for deciding what a skill should do before writing it.
Available on Claude Code, OpenAI Codex CLI, VS Code / GitHub Copilot, Google Gemini CLI, Cursor, OpenCode.
Installing it means first adding a marketplace Magpie does not publish — obra/superpowers-marketplace. The install flow asks before it does, and names whose it is.
Ships a plugin manifest per harness and one shared skills/ tree, the same shape Magpie uses, so it is not a Claude Code-only package.
Install commands per agent are in Companion skill packages.
Try these first
Illustrative shapes, not real transcripts — your output will differ. Nothing below sends, merges, or posts anything without you confirming it.
List everything installed.
/magpie-utilities:list-skills
Author a new skill.
/magpie-utilities:write-skill
Report a framework bug upstream.
/magpie-utilities:report-framework-issue
Skills
| Skill | Purpose | Status |
|---|---|---|
write-skill | Author a new framework skill or update an existing one: frontmatter, placeholder convention, injection defenses, Privacy-LLM gate-check, and validator sign-off. | stable |
optimize-skill | Optimize an existing skill by applying restructuring patterns — split an oversized SKILL.md into linked sibling docs, trim frontmatter, and improve eval alignment. | stable |
list-skills | Print a live index of every skill in this repository, grouped by family, with each skill's name and first-sentence description. | stable |
skill-reconciler | Reconcile a skill's declared state (frontmatter, sibling docs, symlinks) against the framework's conventions and surface discrepancies with proposed fixes. | stable |
When to adopt this family
Adopt utilities if you intend to write or maintain your own skills —
whether contributing them back to Magpie or keeping them in your own project.
If you are only adopting existing skills to run on your project, you do not
need this family; the setup family is your starting
point instead.
Adopter contract
The utilities skills make no state changes to your project's tracker, label
set, or shared infrastructure. list-skills and optimize-skill are
read-only; write-skill only creates or edits skill files under your control,
which you review before committing.
Status
Stable. All four skills are shipped and validate under
skill-and-tool-validate. They are framework-authoring tools, so they evolve
with the framework's own conventions rather than with adopter pilots.
Cross-references
docs/modes.md§ Meta — why these skills sit outside the maintainership-mode taxonomy.docs/spec-driven-development.md— the authoring loopwrite-skillandoptimize-skillsupport.