rig-onboardlisted

# Rig onboarding You are onboarding **the current working project** (the "target") into Rig. Your job is to detect what the project is, agree a **project profile** with the user, copy in the pieces they want, and leave them with a working, documented setup. Be interactive but efficient — detect aggressively, ask only what you cannot infer. ## 0. Locate the kit (`RIG_DIR`) The kit lives in a directory (`RIG_DIR`) separate from the target project — you copy files *out of* it. Resolve `RIG_DIR` in this order: 1. An explicit local path in the invocation args. 2. This skill's own location (`.../rig/skills/rig-onboard/`) → `RIG_DIR` is two levels up (the repo root that contains `skills/`, `agents/`, `ci/`). 3. `~/dev/rig`, then `~/rig`. 4. **Remote (the zero-setup path).** If none of the above exist — which is the case when the user just pointed you at a GitHub URL for this skill — clone the kit to a temp dir and use that as `RIG_DIR`: ```bash RIG_DIR="$(mktemp -d)/rig" git clone --depth 1 <RIG_REPO_URL> "$RIG_DIR" ``` Derive `<RIG_REPO_URL>` from the URL you were given: strip any `/blob/<branch>/…` or `raw.githubusercontent.com/…` suffix back to the repo root (e.g. `https://github.com/agent-rig/rig`). Cloning is strongly preferred over fetching files one-by-one — the kit is ~40 small text files and a shallow clone grabs them all at once. If `git` isn't available, fall back to fetching individual raw files as you need them. Then confirm