gemini-when-to-uselisted

# Gemini When To Use This is the master routing skill for the Gemini plugin. Before invoking any other `gemini-*` skill, consult this guide to decide whether a Gemini consult is warranted and which capability to reach for. ## When to invoke this skill - You are uncertain whether the task justifies a Gemini call at all. - The task touches multiple Gemini capabilities and you need to pick the right one. - You want to avoid hallucination on a fact, version number, CVE, or post-training claim. - A user asks "use Gemini" without specifying which capability. ## Cost discipline rules 1. **Do not call Gemini for tasks Claude can handle confidently.** Simple string manipulation, well-known algorithms, boilerplate generation, and in-context refactors do not need a second opinion. 2. **One Gemini call per sub-task.** Do not fan out multiple parallel Gemini calls unless each covers a distinct, independent concern. 3. **Prefer cheaper tools first.** Use `gemini_generate` (chat/reason) before reaching for `gemini_search_grounded` or deep research unless freshness is required. 4. **File analysis is expensive.** Upload files to Gemini only when the file is genuinely too large for Claude's context or is a non-text format (PDF, image, audio, video). ## Anti-hallucination triggers Invoke a Gemini skill whenever the response would otherwise rely on: - A library version, API endpoint, or config key that may have changed since training cutoff. - A CVE, security advisory, or patch status. -