菜单
Spin up a single agent as an advisor - second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Draek2077/otto-code --skill otto-advisor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Onboard a repository into Otto project knowledge by bootstrapping the `.otto` Markdown store, researching the codebase, documentation, Git history, active initiatives, and external references, and recording evidence-backed draft pages for review. Use when a user asks to onboard, initialize, seed, or build project knowledge for a new or existing repository.
Operate Otto's project knowledge safely: query pages, manage project charters and delivery, evaluate references, update current truth with reasons, append evidence, and review status. Use when an agent needs to read or change durable project knowledge.
Initialize and verify Otto's project knowledge store for a project. Use when a user asks to set up, enable, initialize, or prepare project knowledge before seeding it.
正在显示 SKILL.md
| name | otto-advisor |
| description | Spin up a single agent as an advisor - second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself. |
| user-invocable | true |
| argument-hint | [--profile <name>] <question or topic> |
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
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.
--profile "UI Work") → select it by name.notes best fit the question: design and approach, audit and review, or research and root-cause analysis.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 advisor has zero context. Make it self-contained:
End with the no-edits suffix:
This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.
If $ARGUMENTS contains another skill reference - /unslop, /unslop-risk, $unslop, etc. - the user is asking the advisor to run that skill against the current task. Examples:
/otto-advisor /unslop → advisor runs /unslop on the current diff./otto-advisor /unslop-risk → advisor does an unslop-risk review./otto-advisor $diagnose this build failure → advisor invokes /diagnose.Parse the forwarded skill name out of $ARGUMENTS (/<name> or $<name>). In the briefing, tell the advisor explicitly:
Invoke the `<name>` skill against this task. Load it via the Skill tool before doing anything else.
Pass through any remaining arguments after the skill name as the skill's own input. The advisor - not you - runs the skill; you're still just the orchestrator handing it the work.
Create the advisor agent via Otto with a [Advisor] <topic> title, the briefing as the initial prompt, relationship: { kind: "subagent" }, and workspace: { kind: "current" }. Wait for it to finish. Read its response. Synthesize for the user - the advisor's verdict + your recommendation.
If the user wants ongoing input ("keep this advisor for the next few decisions"), don't archive after the first reply. Send follow-ups when you need another take. Archive when the user says they're done, or when the topic shifts and a fresh context would serve better.