save-skill

Save this workflow as a skill

The user watched you do something and wants it captured so a future task can repeat it without being re-taught. Your job is to turn the actual work you just did into a durable, reusable skill — and to reuse the skills that already exist instead of piling up near-duplicates.

Do this only when asked (this is the user-triggered counterpart to post-task reflection). Write through the MCP tools below — a skill written with the built-in Write tool is discarded when the task ends.

The two tools

• vibe_seller_list_skills → {slug, name, description, source, updatable} per skill. Call it first, every time.
• vibe_seller_save_skill(slug, skill_md, files?) → creates a new user-space skill, or overwrites an existing updatable one (that is how you extend). files is an optional {path: content} map for bundled references or scripts.

Hard rule: you only ever write user-space skills

source tells you what a skill is:

• builtin — shipped and maintained by the repo. Read-only. You cannot edit it and vibe_seller_save_skill will reject its slug. If a built-in is the closest match, do not try to extend it — create a new user-space skill (pick a distinct slug) that captures the user's specific workflow and, where useful, points at the built-in for the mechanics.
• custom / imported (updatable: true) — user-space. These are the only skills you may overwrite.

Never decide a skill is built-in FROM MEMORY, and never silently skip an update. This is the failure that keeps a follow-up from landing: the user says "update that skill", you recall it as built-in, and you do nothing. Two rules kill it:

1. source comes from vibe_seller_list_skills, not memory — call it again for the update, every time. A skill YOU created earlier this session is custom (user-space, updatable), NOT built-in — your own vibe_seller_save_skill made it.
2. When in doubt, just attempt the save. vibe_seller_save_skill(slug, merged_md) OVERWRITES an updatable skill (that is the extend) and only rejects a genuinely built-in slug — with a message telling you to create a new one. So the server, not your guess, is the authority: try the save; on rejection, create a new user-space skill. Never conclude "it's built-in, nothing to do" and end the turn — that leaves the user's request undone.