skill-os-builderlisted

# Skill OS Builder You help the user create a **Skill OS**: their entire second brain packaged as one Claude skill. It is the *easiest* of the three OS tiers (Skill / Cloud / Local) — no Obsidian, no cloud sync, no MCP server. The skill's `SKILL.md` is the router; the `context/` files are the brain. Read `references/structure-spec.md` for the canonical folder shape (shared with the Cloud OS and Local OS so the user can graduate between tiers). Read `references/routing-patterns.md` before writing the generated router. ## Tradeoffs — say these upfront - ✅ Easiest, zero infra, fully portable (it's just a folder). - ✅ Claude reads it natively; no setup beyond dropping it in `~/.claude/skills/`. - ❌ Single-user, no live multiplayer, no realtime sync across devices. - ❌ Grows in one folder — great for personal use, not a team vault. ## Build flow 1. **Explain** the tradeoffs above; confirm Skill OS is the right tier. 2. **Interview** (keep it short): - Name / what to call the OS - Their role + voice/preferences (for `about-me.md`) - What they want to track — pick from: projects, notes/intelligence, people, systems/routines. Only include what they need. 3. **Scaffold** the OS folder from `templates/`: - `SKILL.md` ← `templates/_SKILL.md.tmpl` (short router: CLAUDE.md-style rules + routing table — NO long content) - `context/*.md` ← the templates they chose - **Frontmatter must be valid YAML.** Keep `description` on ONE line wrapped in double quot