otto-advisorlisted

# Otto Advisor Single agent. Reads the situation you're in. Gives a judgment. You decide what to do - the advisor doesn't drive the work. **User's request:** $ARGUMENTS ## Prerequisites Read the **otto** skill. Call `list_agent_profiles` before choosing the advisor, and read every entry's `roles` and `guidance`. Do not create the advisor until you have inspected the available agent profiles. ## Picking the advisor 1. **User named one** (`--profile "UI Work"`) → select it by name. 2. **Otherwise** choose the agent profile whose `notes` best fit the question: design and approach, audit and review, or research and root-cause analysis. 3. **Contrast helps.** When several fit, prefer a different provider family from your own so the second opinion is genuinely fresh. Pass its name as `create_chat`'s `agentProfile`, as described by the **otto** skill. If none fits, use Otto's provider-discovery fallback and tell the user. ## The briefing The advisor has zero context. Make it self-contained: - The question, sharply. - What you've considered and what you've ruled out. - Relevant files by path (don't paste - let the agent read). - Explicit ask: "give me a recommendation, with reasoning." End with the no-edits suffix: ``` This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code. ``` ## Forwarded skills If `$ARGUMENTS` contains another skill reference - `/unslop`, `/unslop-risk`, `$unslop`, etc. - the user is asking the advisor to run that skill ag