fork-and-publish-skilllisted

# Fork and publish a skill with qvr qvr lets you take an installed skill, **eject** it into your project to edit directly, then **publish** the result — either back to its origin or to a brand new fork you own — cutting tagged releases as you go. After each publish the lock entry flips back to consume mode, so you can iterate: edit → publish v0.2.0 → edit → publish v0.3.0. This skill drives that loop. ## When to use this - The user wants to tweak a skill's content and keep the change. - They want to publish a skill back upstream, or fork it to a repo they control. - They want to cut tagged releases and iterate version by version. For installing/discovering skills use `onboard-skills`; for verifying provenance of what you publish use `verify-skill-supply-chain`. ## Prerequisites - The skill must be **installed in a project** (not only `--global`). Editing a global skill in place would mutate a copy every project shares, so it's not supported. To change a global skill: `qvr add <skill>` into a project, edit and publish there, then re-add the published version with `--global`. - A clean-ish working state helps; `publish` refuses a dirty eject dir unless you pass `--auto-commit`. ## Workflow ### 1. Eject the skill for editing `qvr edit` promotes the symlinked skill into a real directory under the canonical agent target (the alphabetical-first installed target — e.g. `.claude/skills/<name>/` or `.cursor/rules/<name>/`, depending on what you installed into); any ot