← ClaudeAtlas

interviewlisted

Use to build or update the friend's identity + working-style profile. Triggers on the /ren:interview slash command, or delegated to from /ren:install's onboarding flow. Asks ONLY from a capped, skippable question list — every question is optional, the whole interview can be skipped, and every unanswered field gets a sane default. No venture/founder questions in this default path.
hazarsozer/ren-os · ★ 1 · AI & Automation · score 73
Install: claude install-skill hazarsozer/ren-os
# interview Builds or updates the friend's identity page. Asks from `skills.interview.lib.QUESTIONS` — a fixed, capped list (≤ `skills.install.lib.QUESTION_BUDGET`, currently 10) — in order, and stops. Nothing here is a pipeline or a branching questionnaire; it's a flat list, every entry independently skippable, with the whole thing skippable too. ## When to use this skill - Friend invokes `/ren:interview` directly, any time — first run or a re-run to update answers. - `/ren:install`'s onboarding flow delegates to this skill at its interview stage. ## When NOT to use this skill - Friend wants the founder/venture arc — **not offered by this skill.** Say so in one line: "a founder/venture profile is an optional later module, not part of this interview" — and stop there. Do not ask venture questions, do not offer to enable the module from here. - Friend just wants to pin one fact → `/ren:pin`, not a full interview. ## Behavior 1. State up front, plainly: every question below is optional, and the friend can say "skip to coding" (or equivalent) at any point to stop the whole interview — whatever wasn't answered gets a sane default, no exceptions. 2. Ask each entry in `skills.interview.lib.QUESTIONS`, in order, using its `options` (if any) to offer a small closed set — free text otherwise. Never exceed the list; never invent additional questions beyond it. 3. Collect a `dict` of `{key: answer}` for whatever was actually answered (skipped keys simply absent, or `None`). 4. Ca