Consult Skill

consult is an Agent Skills-compatible skill for asking another coding agent for an independent, advisory consultation with mutation-restricted defaults: review, brainstorming pass, debugging partner, or second opinion. A host agent can use it to involve installed backends including Gemini, OpenCode, Claude, Codex, Pi, and Qoder without making the user think about the underlying command wrapper.

The canonical skill lives at:

.agents/skills/consult

See .agents/skills/consult/SKILL.md for usage and safety guidance, and .agents/skills/consult/INSTALL.md for agent installation options.

How To Use It

Ask your coding agent for the consultation you want in normal language:

Ask Gemini to review this change critically and return only actionable risks.

Consult Pi on the API design. Be thorough, but avoid overengineering.

Have Gemini and Pi discuss this architecture for two rounds, then synthesize the tradeoffs.

Ask OpenCode for debugging hypotheses and rank the next checks by expected signal.

The host agent handles backend selection, prompt framing, session continuity, and claim verification. For multi-agent discussion, it can orchestrate rounds by consulting one backend, feeding the result to another, and then summarizing what survived local verification.

Direct Wrapper Usage

The shell wrapper is useful for maintainers, debugging, or manual use.

List available backends:

.agents/skills/consult/scripts/consult.sh --list

Run a consultation:

.agents/skills/consult/scripts/consult.sh --to gemini "Review this change for risks."

Use --prompt when it is clearer for scripts or when the prompt begins with -:

.agents/skills/consult/scripts/consult.sh --to gemini --prompt "Review this change for risks."

Preview the exact backend command:

.agents/skills/consult/scripts/consult.sh --to pi --dry-run "Check the API design."

Run deterministic wrapper checks:

.agents/skills/consult/tests/wrapper.sh

Notes

• Backend CLIs must be installed and authenticated separately.
• Consultations are advisory; verify claims locally before acting on them.
• The strongest read-only guarantee is the Codex backend's OS sandbox. Other backends use approval, plan, or tool allowlist controls as documented in the skill references.
• --json output shape is backend-specific; Gemini, Claude, Qoder, and OpenCode use their CLI formats, Codex emits JSONL events, and Pi intentionally rejects consult --json.
• The qoder backend is often the same product as the host agent. A Qoder consultation starts a fresh session, so it is an independent answer, but it shares your account, models, and skills rather than being a different vendor.
• The project is licensed under Apache-2.0. See LICENSE and NOTICE.