gemini-cli
Use Gemini CLI in non-interactive mode for tasks requiring massive context windows (1M tokens). Best delegated to subagents for iterative analysis and summarization. Invoke when analyzing large codebases, requesting deep analysis, getting second opinions on complex problems, or when Claude's context limits are insufficient. Triggers include phrases like "use gemini", "analyze with gemini", "get second opinion", "deep analysis of codebase", or when processing files exceeding Claude's context capacity. IMPORTANT - Always delegate to a subagent using the Task tool for better iteration and result summarization.
What this skill does
# Gemini CLI Integration Always run through subagents for better iteration and summarization. Make the subagent always ask Gemini to provide evidence, and make the subagent verify the findings before summarizing for the main agent. **NEVER use `--approval-mode yolo` or `--yolo`.** Gemini must not auto-approve destructive actions. ## Quick Reference ```bash # Basic one-shot query (non-interactive mode) gemini "Explain this codebase architecture" # Specify model (by alias or full ID) gemini -m flash "Standard analysis task" gemini -m pro "Deep reasoning task" gemini -m gemini-2.5-flash "Use specific GA model" # Include additional directories in context gemini --include-directories ./libs,./shared "Analyze dependencies" # Multi-line prompt using heredoc gemini <<'__GEMINI_PROMPT__' Analyze this codebase for security vulnerabilities. Focus on: SQL injection, XSS, authentication issues __GEMINI_PROMPT__ # Output formats gemini -o json "query" # structured JSON output gemini -o text "query" # default gemini -o stream-json "query" # real-time JSONL events ``` ## Available Models ### Model Aliases (recommended for `-m` flag) | Alias | Resolves to | Use case | |-------|------------|----------| | `auto` | `gemini-3-pro-preview` | Default, auto-routing | | `pro` | `gemini-3-pro-preview` | Deep reasoning | | `flash` | `gemini-3-flash-preview` | Fast agentic coding | | `flash-lite` | `gemini-2.5-flash-lite` | Lowest latency/cost | ### Full Model IDs **Gemini 3 (Preview):** - `gemini-3-pro-preview` - Most powerful, deep reasoning - `gemini-3-flash-preview` - Best for agentic coding (78% SWE-bench), 1/4 cost of Pro **Gemini 2.5 (GA):** - `gemini-2.5-pro` - Stable, balanced performance - `gemini-2.5-flash` - Stable, fast - `gemini-2.5-flash-lite` - Lowest latency and cost ## Headless Mode Tool Restrictions In non-interactive mode (positional query or `-p` flag), Gemini restricts certain tools by default: | Default | Excluded: shell, edit, write_file, web_fetch | |---------|-----------------------------------------------| | `--approval-mode auto_edit` | Excluded: shell only | Override specific restrictions with `--allowed-tools` when needed: ```bash gemini --allowed-tools ShellTool "Run the test suite and report results" ``` ## Subagent Delegation Pattern **CRITICAL:** Always delegate Gemini tasks to a subagent using the Task tool for multiple retry attempts, better summarization, and error handling. ### Pattern: Using Task Tool with Gemini ``` Task( subagent_type: "general-purpose", description: "Analyze codebase with Gemini", prompt: "Use the gemini-cli skill to analyze /path/to/project. Focus on security vulnerabilities and performance issues. See references/prompt_patterns.md for effective prompts. Ask Gemini to provide evidence for findings. Verify findings before summarizing key points in bullet form." ) ``` ### Pattern: Second Opinion ``` Task( subagent_type: "general-purpose", description: "Get Gemini second opinion", prompt: "Use gemini-cli skill to get Gemini's critique of the analysis. See references/prompt_patterns.md for second opinion prompts. Highlight disagreements or missing considerations." ) ``` ## When to Use Gemini vs Claude | Use Gemini for | Use Claude for | | -------------- | -------------- | | Massive codebase review (>100k tokens) | Quick code questions | | Cross-validating critical analysis | Small file analysis | | Multi-file architecture analysis | Interactive coding assistance | | Tasks exceeding Claude's context | Tasks requiring file edits | | | Tasks requiring follow-up questions | ## Additional Resources - **`references/prompt_patterns.md`** - Effective prompt templates for codebase analysis, security audits, performance analysis, second opinions, and context maximization tips ## Troubleshooting **Model not available:** Gemini 3 models are still in preview. Fall back to Gemini 2.5 models for GA stability. **Slow responses:** Large context takes time. Narrow scope with `--include-directories` or use `flash-lite`. **Tools not running in headless mode:** Default headless excludes write tools. Use `--allowed-tools` to selectively enable specific tools.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.