agentleFS
sonichisonichi/sutando/skills/claude-gemini/SKILL.md

claude-gemini

Skill396 starsChanged 6 months agoMITView on GitHub

Use the local Gemini CLI from Claude Code with the user's existing Gemini authentication or API configuration. Use for large-context repo scans, multimodal analysis, second-opinion planning, or structured Gemini runs in the current workspace.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default to --approval-mode plan for read-only analysis.

    line 24
  2. Distinctive:

    Keep Gemini in the same repo by changing into the target workspace before running it.

    line 26
  3. Very specific:

    Prefer --output-format json or stream-json when another tool will consume the output.

    line 27
  4. Very specific:

    If ARGUMENTS is empty, explain the available modes and suggest --approval-mode plan for analysis.

    line 53
  5. Distinctive:

    If ARGUMENTS is present, run:

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Claude Gemini

Delegate work from Claude Code to the local gemini CLI. This skill uses whatever authentication the Gemini CLI is already configured to use on this machine, including API key or signed-in CLI flows. It does not copy or export secrets.

Usage: /claude-gemini [prompt]

ARGUMENTS: $ARGUMENTS

When to Use

  • "Use Gemini on this repo"
  • Need a large-context scan across many files
  • Need multimodal or cross-module analysis from a second model
  • Need a read-only or JSON-formatted Gemini pass from the current workspace

Guardrails

  • Default to --approval-mode plan for read-only analysis.
  • Switch to --approval-mode auto_edit only when the user wants Gemini to make edits.
  • Keep Gemini in the same repo by changing into the target workspace before running it.
  • Prefer --output-format json or stream-json when another tool will consume the output.

Quick Checks

bash "$SKILL_DIR/scripts/gemini-run.sh" --check

Common Commands

# Read-only analysis
bash "$SKILL_DIR/scripts/gemini-run.sh" -- "Trace how tasks flow from voice input to execution"

# Explicit model selection
bash "$SKILL_DIR/scripts/gemini-run.sh" --model gemini-2.5-pro -- "Review the repo structure and identify weak points"

# Machine-readable output
bash "$SKILL_DIR/scripts/gemini-run.sh" --output-format json -- "Summarize risks in src/startup.sh"

# Allow edits when the user asked for implementation help
bash "$SKILL_DIR/scripts/gemini-run.sh" --approval-mode auto_edit -- "Implement a safer startup preflight for missing services"

If Invoked As A Slash Command

  • If ARGUMENTS is empty, explain the available modes and suggest --approval-mode plan for analysis.
  • If ARGUMENTS is present, run:
bash "$SKILL_DIR/scripts/gemini-run.sh" -- "$ARGUMENTS"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.