update-setup

# Update Setup Generate a personalized upgrade skill in Nanobot's agent workspace. Use the absolute `<agent-workspace>/skills/update/SKILL.md` path, where `<agent-workspace>` is shown in the system prompt. Never substitute a project-relative path. If the write is rejected, ask the user to select the agent workspace or enable Full Access before rerunning setup. ## Step 1: Check Existing Use `read_file` to check if `<agent-workspace>/skills/update/SKILL.md` already exists. If it exists, ask the user: "An upgrade skill already exists. Reconfigure?" Wait for the user's reply. If no, stop here. ## Step 2: Current Version and Install Clues Use `exec` to run `nanobot --version`. Tell the user the current version. Then collect install clues with `exec`. These commands are best-effort; if one fails, keep going and show the useful output: ``` command -v nanobot || true python -m pip show nanobot-ai || true pipx list | sed -n '/nanobot-ai/,+3p' || true uv tool list | sed -n '/nanobot-ai/,+3p' || true ``` Summarize what you found in one short paragraph. Use the clues only to suggest a likely install method. Do not treat them as confirmation. ## Step 3: Confirm Required Inputs CRITICAL: Do not write `<agent-workspace>/skills/update/SKILL.md` until the install method is explicitly confirmed by the user. The install method must come from a user answer or confirmation, not from inference alone. If you cannot get a clear answer, stop and ask the user to rerun this setup when they ...