skills/multi-model-consultation/SKILL.md
Consult AI models (GPT, Gemini, Grok, Opus) for perspectives on questions. Use when user says "ask gpt", "ask gemini", "ask grok", "ask opus", "ask both", "ask all three", "ask all four", "ask gpt and gemini", "consult opus", or wants model opinions on decisions. Spawns ONLY the models explicitly requested.
npx skillsauth add mgajewskik/opencode-config multi-model-consultationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query advisory subagents (GPT, Gemini, Grok, Opus) based on user request. Spawn ONLY the models explicitly mentioned.
| Model | Subagent | Strengths | |-------|----------|-----------| | GPT | @gpt | Strong reasoning, broad knowledge | | Gemini | @gemini | Good at synthesis, multimodal | | Grok | @grok | X/Twitter data, less filtered, contrarian | | Opus | @opus | Deep reasoning, careful tradeoff analysis |
Parse user request and spawn ONLY requested models:
| User Says | Spawn | |-----------|-------| | "ask gpt..." | @gpt only | | "ask gemini..." | @gemini only | | "ask grok..." | @grok only | | "ask opus..." | @opus only | | "ask gpt and gemini..." | @gpt + @gemini | | "ask gpt and grok..." | @gpt + @grok | | "ask gpt and opus..." | @gpt + @opus | | "ask gemini and grok..." | @gemini + @grok | | "ask gemini and opus..." | @gemini + @opus | | "ask grok and opus..." | @grok + @opus | | "ask both" (after mentioning 2) | the 2 mentioned | | "ask all three..." | @gpt + @gemini + @grok (legacy) | | "ask all four..." | @gpt + @gemini + @grok + @opus | | "ask all models..." | @gpt + @gemini + @grok + @opus |
Default behavior: If ambiguous, ask user which model(s) they want. Do NOT default to all models.
Parse user request carefully:
Before spawning subagents:
Spawn ONLY the models user requested, all at once:
# Single model example
Task 1: @gpt - [the question]
# Two models example
Task 1: @gpt - [the question]
Task 2: @gemini - [the question]
# All three example
Task 1: @gpt - [the question]
Task 2: @gemini - [the question]
Task 3: @grok - [the question]
# All four example
Task 1: @gpt - [the question]
Task 2: @gemini - [the question]
Task 3: @grok - [the question]
Task 4: @opus - [the question]
Adapt synthesis to number of models:
Single model:
## My Analysis
[Your assessment]
## [Model]'s Perspective
[Summary of response]
## Synthesis
[Compare your view with model's, final recommendation]
Two models:
## My Analysis
[Your assessment]
## [Model 1]'s Perspective
[Summary]
## [Model 2]'s Perspective
[Summary]
## Synthesis
### Agreement
[Where perspectives align]
### Divergence
[Where they differ]
### Recommendation
[Final recommendation with rationale]
Three models:
## My Analysis
[Your assessment]
## GPT's Perspective
[Summary]
## Gemini's Perspective
[Summary]
## Grok's Perspective
[Summary]
## Synthesis
### Agreement
[Where all align]
### Divergence
[Where they differ and why]
### Recommendation
[Final recommendation, which arguments most compelling]
Four models:
## My Analysis
[Your assessment]
## GPT's Perspective
[Summary]
## Gemini's Perspective
[Summary]
## Grok's Perspective
[Summary]
## Opus's Perspective
[Summary]
## Synthesis
### Agreement
[Where perspectives align]
### Divergence
[Where they differ and why]
### Recommendation
[Final recommendation, which arguments most compelling]
Single model: User: "ask gpt about early bird vs night owl" → Spawn @gpt only, synthesize with your view
Two models: User: "ask gpt and gemini about monorepo vs polyrepo" → Spawn @gpt + @gemini only, synthesize both with your view
All three: User: "ask all three about best testing strategy" → Spawn @gpt + @gemini + @grok, full synthesis
Opus only: User: "ask opus about event sourcing vs CRUD" → Spawn @opus only, synthesize with your view
All four: User: "ask all models about monolith vs microservices" → Spawn @gpt + @gemini + @grok + @opus, full synthesis
documentation
Create senior-level deep research dossiers and roadmap companions. Use when the user asks for a dossier, senior research, deep research, in-depth research, mental models for a topic, senior perspective on a topic, how something actually works, ramp up on a topic, architectural deep dive, tradeoffs, failure modes, or what a senior would notice. Produces current-directory research-* and roadmap-* markdown artifacts, not a tutorial or short summary.
development
Senior-level Knative and OpenShift Serverless guidance for Serving, Eventing, Functions, autoscaling, scale-to-zero, CloudEvents, RabbitMQ/Kafka sources, Lambda migration, Harbor/OCI images, debugging, operations, and production rollout. Use when working with Knative Service, Revision, Route, KPA, activator, queue-proxy, Broker, Trigger, Source, Sink, kn func, OpenShift Serverless, Kourier, eventing-rabbitmq, Knative Kafka, or serverless workloads on Kubernetes/OpenShift.
development
Senior-level RHEL-family Linux operations. Use when running, debugging, hardening, patching, installing, upgrading, or operating Red Hat Enterprise Linux, Rocky Linux, AlmaLinux, CentOS Stream, Fedora-as-upstream, or related enterprise Linux hosts: systemd, RPM/DNF, SELinux, NetworkManager, firewalld, storage, kernel/kdump, FIPS/STIG, Satellite, IdM, Podman, bootc, air-gapped fleets.
development
Senior-level Proxmox VE guidance for VM creation, templates, storage, ZFS, Ceph, networking, clusters, HA, PBS backups, debugging, upgrades, security, and production/homelab operations. Use when working with Proxmox, PVE, Proxmox VE, qm, pct, pvesm, pvecm, pmxcfs, HA manager, Proxmox Backup Server, VM migration, Proxmox incidents, or Ceph/ZFS/Corosync/VLAN bridges in a Proxmox VE context.