tool-selection-framework
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. Use this skill when starting projects with unclear tool requirements, optimizing context-constrained workflows, or designing multi-phase strategies that leverage multiple tools' strengths. This skill helps match tool capabilities to task characteristics, preventing wasted context and ensuring optimal resource allocation.
npx skills add majiayu000/claude-skill-registry --skill tool-selection-framework-92bilal26-taskpilotai-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Designs 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. It helps match tool capabilities to task characteristics, design multi-phase workflows, optimize context utilization, balance cost and performance, and avoid wasted context.
How it works
- Provides an analysis framework with questions that evaluate: codebase size, task type (exploration, focused implementation, hybrid), reasoning depth, context budget, time sensitivity, and expertise level.
- States recommended tool(s) per scenario, including multi-phase workflows (Gemini exploration followed by Claude Code implementation) when codebases exceed Claude Code capacity.
- Defines a decision algorithm and multi-phase workflow to execute in two phases:
- Phase 1: Gemini Exploration (load large codebase, explore architecture, generate a summary document, create a checkpoint).
- Phase 2: Claude Code Implementation (load Phase 1 summary, load current context, implement feature with deep reasoning, validate).
- Includes a Tool Capability Matrix comparing Claude Code and Gemini CLI across context, use cases, reasoning, cost, latency, ideal codebase size, task complexity, and specialization.
When to use it
Use this skill when starting a project with uncertain tool requirements, or when codebase size and task complexity suggest a multi-tool, phased approach (exploration first, then implementation).
What it can touch
- Tools: Claude Code, Gemini CLI
- Context loading and phase sequencing: Phase 1 (Gemini Exploration), Phase 2 (Claude Code Implementation)
- Outputs: architecture summaries, checkpoints, and implementation tasks
Caveats
- The framework relies on explicit guidance within the tool-usage questions and does not infer outcomes beyond stated recommendations.
- Licensing and dependencies: requires constitution:v6.0.1.
- Context windows and costs are bound to the described tool capabilities; future tool changes may affect recommendations.
# 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) - Task requires broad exploration (large codebase analysis, pattern discovery) - Task requires deep reasoning (architectural decisions, security analysis) - Multi-phase workflow needed (exploration → implementation) - Optimizing cost/performance balance for long-term project - Team asks "Should we use Claude Code or Gemini CLI for this?" - Students learning contex
- Purpose
- When to Activate
- Persona
- Questions (Analysis Framework)
- Question 1: Codebase Size Assessment
- Question 2: Task Type Evaluation
- Question 3: Reasoning Depth Requirements
- Question 4: Context Budget Constraints
- Question 5: Time Sensitivity
- Question 6: Expertise Level
- Principles
- Principle 1: Right Tool for the Job
- Principle 2: Specialization Value
- Principle 3: Multi-Phase Approach
Count lines of code (excluding comments, blank lines) cloc . --exclude-dir=node_modules,venv
What does the tool-selection-framework skill do?
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. Use this skill when starting projects with unclear tool requirements, optimizing context-constrained workflows, or designing multi-phase strategies that leverage multiple tools' strengths. This skill helps match tool capabilities to task characteristics, preventing wasted context and ensuring optimal resource allocation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tool-selection-framework-92bilal26-taskpilotai-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.