Second opinion from a named provider
Prefer the MCP tool when it already covers the provider
If consult_advisor is registered and its configured provider is the one
being asked for, use it instead. It logs the consult and scrubs the
subprocess environment; this skill does neither. Come here when the user
names a provider or model the server is not configured for.
Package the consult
Build ONE focused prompt. The advisor is stateless — it sees nothing but what you send. Include:
- The question (one decision or problem, not the whole task)
- Minimal context: options on the table, constraints, what was already tried
- This output contract, verbatim: "Reply with: Recommendation (one clear choice), Reasoning (2-4 load-bearing points), Risks (what could make this wrong). Do not write code."
Run it
Pick the CLI for the provider you want. Run via Bash, passing the packaged prompt as one quoted argument:
- Anthropic (bills Claude subscription):
claude -p "<packaged prompt>" --model <model> - Google (gemini CLI, free personal tier or its own billing):
gemini -p "<packaged prompt>" - OpenAI (only if
codexis installed; bills ChatGPT subscription):codex exec "<packaged prompt>"
Unlike the MCP path, this inherits the session's environment. claude -p
run this way sees the parent session's CLAUDE* variables and may behave
as a nested session; prefer consult_advisor for Anthropic consults.
If the chosen CLI is missing or errors on auth, report that and fall back to the advisor subagent — do not silently skip the consult.
Apply the advice
Weigh the recommendation against repo reality (the advisor can't read this project). State in your reply that you consulted, which provider/model answered, and that this consult is not in the log.