gemini-second-opinion

Included with Lifetime

$97 forever

Get Gemini's independent analysis on recent context or specified topic

AI Agents

What this skill does


# Gemini Second Opinion Command

Get Gemini's independent perspective on a topic, plan, or piece of work.

## Usage

```text
/google-ecosystem:gemini-second-opinion [topic]
```

## Arguments

- `$ARGUMENTS` (optional): Topic or context to review. If empty, reviews general context.

## Examples

- `/google-ecosystem:gemini-second-opinion Is this database schema normalized correctly?`
- `/google-ecosystem:gemini-second-opinion Review my approach to error handling in this module`
- `/google-ecosystem:gemini-second-opinion Should I use microservices or monolith for this project?`
- `/google-ecosystem:gemini-second-opinion Validate my security assessment`

## Execution

### Build Review Prompt

```bash
topic="${ARGUMENTS:-the current context}"

prompt="REVIEW MODE (read-only): Provide an independent analysis.

TOPIC: $topic

Please provide:

1. **Your Assessment**: What is your independent view on this?

2. **Potential Issues**: What concerns or risks do you see?

3. **Alternative Approaches**: What other options should be considered?

4. **Recommendations**: What would you suggest?

5. **Confidence Level**: How confident are you in this assessment? (High/Medium/Low)

Be direct and specific. If you disagree with an apparent approach, say so clearly.

DO NOT modify any files. This is analysis only."
```

### Execute Query

```bash
result=$(gemini "$prompt" --output-format json)
```

### Parse Response

```bash
response=$(echo "$result" | jq -r '.response // "No response received"')
tokens=$(echo "$result" | jq '.stats.models | to_entries | map(.value.tokens.total) | add // 0')
model=$(echo "$result" | jq -r '.stats.models | keys[0] // "unknown"')

# Check for errors
error=$(echo "$result" | jq -r '.error.message // empty')
if [ -n "$error" ]; then
  echo "Error: $error"
  exit 1
fi
```

## Output Format

Present Gemini's perspective:

```markdown
# Gemini Second Opinion

**Topic**: {topic}
**Model**: {model}

---

{response}

---
*Independent analysis by Gemini CLI | {tokens} tokens*
```

## Use Cases

### Validate a Plan

Before executing a significant change, get Gemini's take:

```text
/google-ecosystem:gemini-second-opinion I'm planning to refactor auth to use JWT instead of sessions. Good idea?
```

### Cross-Check Analysis

After Claude provides analysis, validate:

```text
/google-ecosystem:gemini-second-opinion Claude identified 3 security issues in auth.ts. Are there others?
```

### Architecture Decision

Get input on technical choices:

```text
/google-ecosystem:gemini-second-opinion Should this use GraphQL or REST?
```

### Code Review Supplement

Add another perspective to code reviews:

```text
/google-ecosystem:gemini-second-opinion Is this error handling approach robust?
```

## Notes

- Uses "REVIEW MODE" prefix to ensure read-only analysis
- Provides structured output with assessment, issues, alternatives
- Includes confidence level for transparency
- Two AI perspectives catch more issues than one

Files: 1

Size: 3.1 KB

Complexity: 10/100

Category: AI Agents

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/google-ecosystem/skills/gemini-second-opinion

Related in AI Agents

skill-development

Included

Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.

AI Agentsscripts

reprompter

Included

Transform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.

AI Agentsscripts

adaptive-compaction

Included

Adaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.

AI Agentsscripts

agent-skill-creator

Included

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.

AI Agentsscripts

llm-wiki

Included

Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.

AI Agentsscripts

skill-master

Included

Agent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.

AI Agentsscripts