magpie-optimize-skill

<!-- 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> → adopting project's `.apache-magpie/` directory <tracker> → value of `tracker_repo:` in <project-config>/project.md <upstream> → value of `upstream_repo:` in <project-config>/project.md <framework> → `.apache-magpie/apache-magpie` in adopters; `.` in the framework standalone --> # optimize-skill Take one existing framework skill — or a maintainer-supplied set of them — and make it leaner without changing what it does. The skill diagnoses a target against the optimization catalogue distilled from the recent security-suite refactors, proposes the applicable passes, and applies them one at a time as **behavior-preserving** edits the maintainer confirms. The skill validator (and, for tracker-touching skills, the placeholder linter) is the deterministic gate: it is green before the first pass and green again after the last. This skill operates only on **framework-internal files** — `SKILL.md` bodies, their sibling docs, `<project-config>` manifests, tool adapters in this repo. It reads no external or attacker-controlled content, so the prompt-injection-defence callout does not apply. It is the refactoring counterpart to [`write-skill`](../write-skill/SKILL.md): `write-skill` authors a net-new skill; `optimize-skill` re...