Design systematic decision frameworks for selecting appropriate AI tools (Claude Code vs Gemini CLI) based on context requirements, codebase size, reasoning depth needs, and task complexity.
SkillScore95Maintained
Automatic
◆AI Engineer pack
Last verified 8/21/2026
What it changes
Passed 21 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill95%
Checks it passed that the model alone missed
Recommends Claude Code exclusively.
Recommends Claude Code to minimize cost per session.
Recommends Claude Code for superior reasoning depth.
and 17 more in the full report
17 fixed4 passed either way0 still failing1 broke
Pass-rate lift
+73 pp
Tokens
+269%
Agent turns
0%
Response time
-30%
Model gemini-3.6-flashMeasured 8/21/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
When designing a multi-phase workflow where Phase 1 explores a repository with a 2M token tool and Phase 2 implements changes using a 200K token tool, what is the target token count for the generated Phase 1 summary document? Provide your answer under '## Phase 1 Handoff Budget'.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends a summary document target size between 5,000 and 10,000 tokens.
Missed
Passed
case-10 · 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.md625 linessingle file
Tool Selection Framework
Purpose
Enable developers to select the right AI tool for each development task through systematic evaluation of context requirements, codebase characteristics, and task complexity. This skill helps:
Match tool capabilities (context window, reasoning depth, cost) to task requirements
Design multi-phase workflows that leverage tool-specific strengths
Optimize context utilization by choosing appropriate tool for codebase size
Balance cost, performance, and reasoning depth based on project constraints
Avoid wasting context with mismatched tool selection
Create extensible decision frameworks that adapt to new tools
When to Activate
Use this skill when:
Starting new project with uncertain tool requirements
Codebase size approaches/exceeds Claude Code context limits (200K tokens)
Optimizing cost/performance balance for long-term project
Team asks "Should we use Claude Code or Gemini CLI for this?"
Students learning context-aware development tool selection
Persona
"Think like a resource optimization engineer allocating specialized tools to tasks where each tool excels. Your goal is to maximize development productivity by matching tool capabilities—context window size, reasoning depth, cost efficiency—to specific task characteristics such as codebase size, complexity, and phase (exploration vs implementation)."
Questions (Analysis Framework)
Before selecting a tool or designing a multi-tool workflow, analyze through these questions:
Question 1: Codebase Size Assessment
"How many lines of code does this project have?"
Size Categories:
< 50K lines → Claude Code sufficient
Rationale: 200K context window handles full codebase + conversation