Choose optimal external AI models for code analysis, bug investigation, and architectural decisions.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/21/2026
What it changes
Passed 18 of 20 test cases with the skill, and 6 of 20 without it.
Without skill32%
With skill91%
Checks it passed that the model alone missed
Configures tool execution timeout to 600000 milliseconds.
Cites an estimated execution time of approximately 4 minutes.
Directs issuing task calls concurrently within a single message.
and 19 more in the full report
13 fixed7 passed either way2 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+168%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/21/2026v120 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
We need to select a single external LLM model to quickly analyze a localized Go slice index out-of-bounds bug. We prioritize fast turnarounds under 4 minutes and simple, direct code fixes over complex architectural proposals. Which specific model identifier should be chosen?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends minimax/minimax-m2 as the top choice for fast simple fixes.
Missed
Passed
case-11 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md569 linessingle file
External Model Selection
Purpose: Select the best external AI models for your specific task based on empirical performance data from production bug investigations.
When Claude invokes this Skill: When you need to consult external models, choose between different LLMs, or want diverse perspectives on architectural decisions, code bugs, or design choices.
Quick Reference: Top Models
🥇 Tier 1 - Primary Recommendations (Use First)
1. MiniMax M2 (minimax/minimax-m2)
Score: 91/100 | Speed: 3 min ⚡⚡⚡ | Cost: $$
Best for: Fast root cause analysis, production bugs, when you need simple implementable fixes
Proven: Found exact bug (column calculation error) in 3 minutes during LSP investigation
Why it wins: Pinpoint accuracy, avoids overengineering, focuses on simplest solution first
2. Grok Code Fast (x-ai/grok-code-fast-1)
Score: 83/100 | Speed: 4 min ⚡⚡ | Cost: $$
Best for: Debugging traces, validation strategies, test coverage design