gemini-advisor
Skill1 starsChanged 4 months agoMITView on GitHub
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.
- Reads credentials
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- antipattern-detectorSkill
- architecture-reviewSkill
- assumption-challengerSkill
- cavemanSkill
- clipSkill
- code-reviewerSkill
- diagnoseSkill
- feature-writerSkill
- gemini-reviewerSkill
- grill-meSkill
- image-generatorSkill
- issue-creatorSkill
- paper-bananaSkill
- pr-writerSkill
- publishSkill
- tddSkill
- teach-meSkill
- validatorSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Use Bash to invoke the Gemini API entrypoint:
- Distinctive: line 64
If Gemini API key is not configured or the call fails:
- Distinctive: line 67
Do NOT block on Gemini unavailability.
- Distinctive: line 73
If the user's question is about a file, always read and pipe the file content.
- Distinctive: line 74
Keep Gemini prompts self-contained — Gemini has no conversation context.
- Distinctive: line 75
Do not send sensitive information (secrets, credentials) to Gemini.
- Very specific: line 79
Use gemini-advisor for second opinions on any topic, file, or technical question.
- Distinctive: line 83
If unsure about Gemini CLI flags, run:
≈ “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.
Files
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 --helpDoes 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
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.

