multi-tool-model-comparisonlisted

# Skill: Multi-Tool Model Comparison When a developer is evaluating AI coding tools and hasn't committed to one ecosystem, a comparison across Copilot/Codex/Grok is more useful than a deep dive into one. This skill structures that comparison so the result is methodology-grounded and resistant to lineup churn. ## Step 0 — Establish the task shape first The comparison is only as useful as the task description is precise. Before comparing, pin: 1. **Use-case type** — inline completion, supervised chat, or autonomous multi-step run 2. **IDE surface** — VS Code, JetBrains, Neovim, terminal, or CI/cloud 3. **Team / org context** — individual developer, small team, enterprise org with policy controls 4. **Budget sensitivity** — tight per-token ceiling or best-quality-regardless-of-cost These four pins determine which models on each platform are even in scope. Skip the comparison until they are established. ## Step 1 — Map the task to a vendor-neutral tier Use the vendor-neutral task-shape tree (see `../../knowledge/ai-coding-decision-trees.md`) to identify the target tier before touching any vendor lineup: | Tier | Inline/latency | Supervised chat | Autonomous/long | |---|---|---|---| | Fast inline | First choice | Not applicable | Not applicable | | Balanced default | Fallback | First choice | First choice for routine | | Frontier | Not applicable | Hard-reasoning tasks | Always start here | ## Step 2 — Map the tier to each ecosystem's current offering For each of the thr