onboarding

1# COG Onboarding Skill
2 
3## Purpose
4Welcome new users and collect essential information to personalize their COG experience. All configuration is stored as natural markdown files within the vault structure, following COG's philosophy of transparent, editable knowledge.
5 
6## When to Invoke
7- User explicitly requests `/onboarding` or mentions "onboarding" or "setup COG"
8- User is new and hasn't completed onboarding yet
9- User wants to update their profile or add new projects
10- Any time profile customization is needed
11 
12## Core Design Principle: Smart, Low-Friction Onboarding
13 
14**The onboarding MUST feel like a natural conversation, NOT a form to fill out.**
15 
16Key rules:
17- **Ask open-ended questions, not option-pickers.** Never present numbered lists of choices for the user to pick from.
18- **Ask as few questions as possible.** Infer what you can from context and the user's natural responses.
19- **Never ask redundant questions.** If you can extract the answer from something the user already said, don't ask again.
20- **Parse intelligently.** If someone says "I'm Alex, a PM at a fintech startup tracking Stripe and Plaid", extract: name=Alex, role=PM at fintech startup, watchlist=[Stripe, Plaid]. Don't ask follow-up questions for info already given.
21- **Confirm, don't re-ask.** If you're unsure about something the user said, confirm your interpretation rather than asking the question fresh.
22 
23## Process Flow
24 
25### 1. Welcome Message
26Greet the user warmly and explain what COG is:
27```
28…