gemini-delegate

Gemini Delegate Skill

Now supports both Antigravity CLI (agy) and legacy Gemini CLI.

Traditional Chinese

gemini-delegate is a Claude-oriented skill for using Google Antigravity CLI (agy) or legacy Gemini CLI as a specialist for large-context synthesis, long-form drafting, English or bilingual / CJK writing, and second-opinion review.

Part of the agentic AI learning roadmap, a 7-stage curated path for building agentic AI, multilingual (zh-TW, zh-CN, English). This skill is referenced in Lesson 13 (Multi-LLM Delegation).

Why this exists

Claude has a finite working context, and certain tasks are a bad fit even when Claude could technically do them. Two failure modes are common:

• Long-form input does not fit cleanly. When you need to summarize, compare, or rewrite content that spans many large source files, Gemini's larger context window lets it ingest the whole picture at once instead of forcing Claude to chunk and stitch.
• CJK / bilingual writing is uneven. For long-form Traditional Chinese or English/Chinese rewriting, Gemini often produces more natural cadence than Claude. This is a community observation, not an official benchmark, but it shows up enough that it is worth structuring around.

Routing those tasks to agy or legacy Gemini lets Claude stay in its strengths (judgment, terminology review, factual checking) and lets the delegate do what it is best at (large-context synthesis and CJK drafting).

This skill pays off when:

• the source material exceeds Claude's comfortable working context
• you need long-form Traditional Chinese or bilingual writing
• you want a reviewer-style second opinion on long documents
• you need to align terminology across translated content
• you're drafting release notes, FAQs, or summaries from many sources

It does not pay off when:

• the task is bulk code generation (use codex-delegate instead)
• the task is architecture or security review (keep in Claude)
• the input fits in Claude's context and quality matters more than throughput
• factual accuracy outweighs draft fluency (Claude reviews before shipping anyway)

Positioning

This skill is not the Gemini version of codex-delegate. Its job is different:

• summarize large source material into English or zh-TW
• synthesize across multiple files
• draft English, bilingual, or CJK-facing updates
• perform reviewer-style second-opinion passes on long docs
• align terminology across translated content

It is not intended for bulk code generation or architecture work.

Core Pattern

1. Claude prepares a context file with source paths, output paths, language, and constraints.
2. Claude launches the wrapper, which auto-detects agy or legacy gemini.
3. The wrapper can verify required output files after execution.
4. Claude performs factual, terminology, and tone review before shipping.

The delegate may produce useful drafts. Claude still decides whether the result is publishable.

Repository Layout

gemini-delegate-skill/
├── README.md
├── README_zh-TW.md
├── scripts/
│   ├── run_gemini.sh
│   └── run_gemini.ps1
├── skills/
│   └── gemini-delegate/
│       ├── SKILL.md
│       └── references/
│           ├── wrapper.md
│           ├── delegation-targets.md
│           ├── output-contract.md
│           ├── review-checklist.md
│           ├── task-template.md
│           └── examples.md
└── tests/
    └── test_wrappers.py

Testing

python -m pytest tests/ -q

Current wrapper tests cover:

• success-path result.json generation
• verification failure reporting
• AGY_PATH and GEMINI_PATH backend selection

Installation

1. Install the skill via the ai-research-skills Claude Code marketplace:

claude plugin marketplace add WenyuChiou/ai-research-skills
claude plugin install gemini-delegate@ai-research-skills

Default scope is user (this OS account, all projects). Add --scope project to install only for the current project.

2. Install a supported backend. Antigravity CLI (agy) is preferred:

curl -fsSL https://antigravity.google/cli/install.sh | bash
agy --version

Enterprise / Cloud users who still have Gemini CLI access can use the legacy fallback:

npm install -g @google/gemini-cli
gemini --version

You can also point the wrapper at explicit binaries:

export AGY_PATH=/path/to/agy
export GEMINI_PATH=/path/to/gemini

Detection order is AGY_PATH, GEMINI_PATH, agy on PATH, then gemini on PATH.

Migration from Gemini CLI