skillifylisted

## When to invoke Use right after a browse/scrape flow worked and the user wants it reusable — "skillify this", "make this a skill", "save this flow". It writes a new skill in the local repo so future invocations just run `/the-new-name`. # /skillify — Codify a flow into a skill {{include lib/snippets/working-protocols.md}} ### 1. Capture the flow **Provenance guard (STOP if it fails).** /skillify only codifies a flow that actually ran in this session. Walk back **at most ten agent turns** and look for a browse/scrape flow that finished, produced output the user did not reject, and that you can still quote step by step. Beyond that bound you are working from recall rather than evidence, and recall invents selectors that were never there. If nothing qualifies, refuse: "skillify codifies a flow that already worked; I don't see one in this session. Run the browse/scrape steps first, confirm they work, then skillify them." Do not fabricate steps. Two recent flows still do not qualify: - **Output an installed skill already produced.** `/scrape` checks for a matching skill before it prototypes anything; codifying what that match returned would install a second skill for a target that already has one. Name the skill that covers it and stop. - **A flow that only half-worked** — a `_missing` list, an empty field, a selector you had to guess at. Fix the flow, re-run it, then skillify the run that worked. If a single candidate is borderline, name it and confirm before co