skillify

## 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 ### 1. Capture the flow **Provenance guard (STOP if it fails).** /skillify only codifies a flow that actually ran in this session. If there is no recent, working browse/scrape flow to point at — the user is asking you to invent a skill from scratch — 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. From the session that just worked, pin down: - **Intent + trigger phrases** — what the user will say to invoke it. - **The exact steps** — the `$B` verbs / `chain` that worked, in order, with the selectors and the URL (or URL pattern / parameter) used. - **The output shape** — the JSON or summary the flow produced. If any of these is unclear, ask once with AskUserQuestion. Pick a short kebab-case `name`. ### 2. Locate the repo and write the skill Find the vibestack repo (the `vibe-*` binaries are symlinks into it): ```bash REPO="$(cd "$(dirname "$(readlink "${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-config" 2>/dev/null)")/.." 2>/dev/null && pwd || true)" [ -f "$REPO/install" ] || { echo "REPO_NOT_FOUND"; } ``` If `REPO_NOT_FOUND`, ask the user where they cl...