sc-onboardinglisted

Onboard new SI-Coder users. Scans env for credentials each sc-* domain needs, lists what is set and what is missing, asks the user only for the missing pieces, then writes them to ~/.bashrc. One-shot CLI fallback: bin/onboard.js for non-AI flows.
rahmanef63/si-coder-agent · ★ 9 · AI & Automation · score 79

Install: claude install-skill rahmanef63/si-coder-agent

# /sc-onboarding — Guided credential setup Use this skill when the user is setting up `si-coder-agent` for the first time, or after they install a new `/sc-*` domain skill that needs new credentials. ## Two modes ### Mode A — AI-driven (default, interactive) Triggered when the user runs `/sc-onboarding` from Claude / OpenClaw / Gemini. The AI MUST: 1. **Ask which domains they want.** Present a checklist (core deploy domains shown; see the "Required vars per domain" table below or `skills/sc-onboarding/lib/onboarding-domains.js` `DOMAIN_VARS` for the full list, including the stub domains): - `[ ] github` (always required for any deploy) - `[ ] dokploy` (Dokploy CRUD + deploy targets) - `[ ] convex` (Convex self-hosted) - `[ ] hostinger` (optional DNS automation) - `[ ] vercel` (Vercel online frontend) - `[ ] convex-cloud` (Convex Cloud backend) - `[ ] cf` (Cloudflare, future) · `stripe` · `clerk` · `supabase` · `resend` (stubs) 2. **Run `scripts/scan-env.js --domains <list>`** to detect which required vars are already set in the user's environment (via `process.env` + `~/.bashrc` parse). 3. **For each missing var, prompt the user via `AskUserQuestion`** with the per-var description from `steps/<domain>.md`. NEVER ask for vars that are already set unless the user says "reset" or "rotate". 4. **Write only the new values** to `~/.bashrc` by piping the pairs via **stdin** so the raw secret never lands in argv (`ps aux` / `/proc/<pid>/cmdline` / shel