rootnode-profile-builderlisted

Conversational profile builder. Produces validated JSON config files for any rootnode Skill that consumes profile-shaped configuration (handoff trigger check, mode router, critic gate, future Skills). Reads a target JSON Schema (draft-07), conducts a progressive-depth interview using plain-language questions, validates answers, and writes the resulting JSON to a destination path. Schema-agnostic — works with any profile schema conforming to draft-07. Use when a user needs to create, clone, or revise a profile and you do not want them hand-editing JSON. Trigger on: "build me a profile," "create a profile," "I need a profile for X," "set up my profile," "edit my profile," "clone the X profile," "walk me through making a profile." Do NOT use when the user already has a working profile and only wants to invoke the consuming Skill, when the schema cannot be located, or for non-profile JSON config work. Always validate before writing.
drayline/rootnode-skills · ★ 40 · Data & Documents · score 76

Install: claude install-skill drayline/rootnode-skills

# Profile Builder > **Calibration:** Tier 1 (Model-compatible) - runs cleanly on the current dual-primary tier (Opus 5, Sonnet 5) as well as Haiku 4.5 with extended thinking. Structured retrieval, rule evaluation, or template lookup - output shape does not depend on model class. Correct-shape output also on Opus 4.8 (fallback-graceful) and Sonnet 4.6 (legacy-graceful). See repository README for model compatibility. Conversational interview that produces validated JSON profile files for any rootnode Skill. Solves the "users won't hand-edit JSON" problem by walking them through one plain-language question at a time, then writing a validated file. The Skill is **schema-agnostic by design**. It does not encode knowledge of any specific profile schema. It reads the target schema, parses required fields and constraints, generates the interview from the schema, validates answers against the schema, and writes the result. This is what makes the Skill portable across the entire rootnode runtime layer — every Skill that takes profile config uses the same builder, no per-Skill builder forks. ## Important **Progressive depth, not interrogation.** Walk the user through 5-7 substantive questions that determine the profile's shape. Set sensible defaults for everything else. Offer "review and customize defaults" only at the end for users who want it. Never ask 30 questions in sequence — produces bad answers and exhausts users. **Plain language, never machine names.** Translate every en