Skill

gemini-advisor

Gets Gemini's independent opinion on any file, topic, or discussion. Use when users say "ask gemini", "gemini opinion", or "what does gemini think". Provides a second perspective from a different AI model with Claude's commentary. Requires GEMINI_API_KEY environment variable to be set.

From kw-plugin

Install

Run in your terminal

npx claudepluginhub kwiggen/claude-code-plugin --plugin kw-plugin

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Stars1

Forks1

Last CommitMar 4, 2026

Actions

View Source View Plugin View on GitHub View README

Gemini Advisor Skill

Before Starting

Check Gemini availability — Run test -n "$GEMINI_API_KEY" via Bash to verify the API key is configured. If it fails, inform the user that Gemini API key is not configured and offer to answer the question directly.
Determine context — Figure out what the user wants Gemini's opinion on:
- A specific file → read the file content
- A code question → formulate the question with relevant context
- A discussion/decision → summarize the current discussion state
- A general topic → pass the question directly

Process

Step 1: Prepare the Query

Build a clear, self-contained prompt for Gemini that includes:

The user's question or topic
Relevant context (file contents, discussion summary, code snippets)
Framing: "Provide your independent technical opinion on the following."

Step 2: Send to Gemini

Use Bash to invoke the Gemini API entrypoint:

echo "<context>" | node {pluginDir}/dist/gemini/cli.js --prompt "<question with framing>"

Or without stdin if no file/code context is needed:

node {pluginDir}/dist/gemini/cli.js --prompt "<full question with context>"

The CLI outputs JSON with success, output, model, and optional error fields.

Step 3: Present Results

Output Format

Gemini's Take

[Gemini's full response, formatted cleanly]

Claude's Commentary

[Brief commentary on Gemini's response — agreements, disagreements, additional considerations, or alternative perspectives. Keep this concise — the point is to get a second opinion, not to debate.]

Fallback Behavior

If Gemini API key is not configured or the call fails:

Inform the user: "Gemini API key not configured."
Offer to answer the question directly as Claude.
Do NOT block on Gemini unavailability.

Guidelines

Present Gemini's output faithfully — do not rewrite or censor it.
Claude's commentary should be brief and additive, not defensive.
If the user's question is about a file, always read and pipe the file content.
Keep Gemini prompts self-contained — Gemini has no conversation context.
Do not send sensitive information (secrets, credentials) to Gemini.

When to Use This Skill

Use gemini-advisor for second opinions on any topic, file, or technical question. Use gemini-reviewer (/gemini-review) for structured dual code reviews with formal synthesis and verdict.

CLI Reference

If unsure about Gemini CLI flags, run:

node {pluginDir}/dist/gemini/cli.js --help