Gemini CLI delegation workflow implementing delegation-core for Google's Gemini models.
This skill implements conjure:delegation-core for the Gemini CLI.
It provides Gemini-specific authentication, quota management,
and command construction.
For shared delegation patterns, see Skill(conjure:delegation-core).
Skill(conjure:delegation-core) determines Gemini is suitablegemini CLI is installed and authenticatedconjure:delegation-core)conjure:qwen-delegation)Installation:
# Verify installation
gemini --version
# Check authentication
gemini auth status
# Login if needed
gemini auth login
# Or set API key
export GEMINI_API_KEY="your-key"
Verification: Run the command with --help flag to verify availability.
# File analysis
gemini -p "@path/to/file Analyze this code"
# Multiple files
gemini -p "@src/**/*.py Summarize these files"
# With specific model
gemini --model gemini-3-pro -p "..."
# JSON output
gemini --output-format json -p "..."
gemini -p "..." > delegations/gemini/$(date +%Y%m%d_%H%M%S).md
For Gemini-specific models, CLI options, cost reference,
and troubleshooting, see modules/gemini-specifics.md.
gemini --version exits 0 before any task is delegated, and a missing
installation is reported and stops execution.GEMINI_API_KEY and from the delegation's
own exit code, never from gemini auth status. That command exits 0 while
printing Error authenticating: ProjectIdRequiredError over a credential
that cannot be used, so its status is not evidence. delegation-core's
shared module states the rule: authentication is never decided by running a
provider's own CLI.delegations/gemini/YYYYMMDD_HHMMSS.md (timestamp format matching the Quick Start example),
and that file exists on disk after the delegation completes.conjure:delegation-core selected a different provider (Qwen or local), this skill
is not invoked; Gemini delegation only runs when delegation-core explicitly routes to Gemini.