consultlisted

Bring in another coding agent as an independent second opinion. Use when the user explicitly asks to ask, consult, cross-check, debate with, or get a second opinion from another agent/model, including named backends such as Gemini, OpenCode, Claude, Codex, Pi, or an added backend. Here Pi means the Pi backend, not the number π or Raspberry Pi hardware; and names like GPT, OpenAI, Sonnet, Opus, or Qwen name a model or provider, not a backend (resolve them to a model on a chosen backend). Also use for clearly high-risk independent review where another model is materially needed for safety, security, architecture, or regression risk. Do not trigger for ordinary review, debugging, or brainstorming unless external-agent help is requested. Treat responses as advice and verify claims locally before acting.
mikielek/consult · ★ 1 · AI & Automation · score 68

Install: claude install-skill mikielek/consult

# Consult ## Overview Bring an external coding agent into the current task as an independent reviewer or design partner when the user asks for that outside perspective. Treat any response as **advice**: verify repo-specific claims yourself before changing code or reporting conclusions. ## Pick a backend The user usually names one ("ask Gemini", "cross-check with OpenCode"). Selecting a backend (`--to`) is a trust, auth, and harness choice — not just model routing — so resolve it explicitly: ```bash ${CLAUDE_SKILL_DIR}/scripts/consult.sh --list ``` `${CLAUDE_SKILL_DIR}` is this skill's base directory; Claude Code substitutes it automatically to the loaded instance. Never locate `consult.sh` by searching the filesystem — a personal and a project-scoped install can coexist, and a search (or an unresolved `${CLAUDE_SKILL_DIR}` reaching a shell, which silently expands to empty) can run the wrong or a nonexistent script. On a harness without this substitution, resolve it to the directory of the `SKILL.md` you were just given. `--list` shows available adapters and whether their CLIs are on `PATH`. "Installed" does not imply authenticated; the CLIs reuse the user's existing auth and need network access. **Pi backend intent.** Treat "consult Pi", "ask Pi", "the Pi CLI", "the `pi` backend", and "the Pi coding agent" as a request for the Pi backend (`--to pi`). Do **not** treat the number π ("calculate pi to 10 digits") or Raspberry Pi hardware / GPIO / device setup as the Pi bac