plugins/gemini-bridge/skills/compare/SKILL.md
Uses Gemini 2.5 Pro as an independent technical reviewer to compare two approaches and validate design decisions. Implements the "propose with Claude, validate with Gemini" pattern. Activate when the user asks to "compare these two approaches", "get a second opinion on this design", "validate this architectural decision", "should we use X or Y", or "review these two options independently".
npx skillsauth add talent-factory/claude-plugins compareInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use Gemini 2.5 Pro as an independent reviewer to compare technical approaches. No single model has a monopoly on correctness — different architectures surface different trade-offs.
Either:
gemini_status()
gemini_compare_approaches(
problem=<problem_statement>,
approach_a=<description_or_code_of_approach_a>,
approach_b=<description_or_code_of_approach_b>,
criteria=<optional_evaluation_criteria>
)
Good criteria examples: "performance at scale", "maintainability for a small team",
"migration risk", "alignment with existing patterns in this codebase".
Label Gemini's output clearly:
**Independent review by Gemini 2.5 Pro**
[Gemini's structured comparison]
Then provide Claude's synthesis: which recommendation to follow, and why, taking into account both perspectives and the specific project context.
Two models with different training data and architectures will notice different strengths and failure modes in the same design. A disagreement between Claude and Gemini is a signal to investigate further, not a reason to pick a winner arbitrarily.
documentation
Creates comprehensive handoff documentation before a /compact operation, enabling a new agent with fresh context to seamlessly continue the work. Activate when the user says "prepare a handoff", "document before compact", "context is getting too large", "I need to hand this off", "create a handoff document", "end of session notes", or "document the current state for tomorrow". Supports --output and --linear-issue options.
documentation
Collects completed tasks, GitHub activity, calendar meetings, wiki learnings, and Linear progress for the past week, then writes a structured retrospective to the Obsidian vault. Activate when the user runs "/weekly-review", asks "what did I accomplish this week", "weekly retrospective", "summarise my week", or "prepare weekly review". Works from any directory.
development
Produces a prioritised daily briefing by aggregating tasks from Obsidian TaskNotes, Google Calendar, Gmail, Linear, and GitHub, then writes the result to today's daily note in the Obsidian vault. Activate when the user runs "/today", asks "what's on my plate today", "give me my daily briefing", "what do I need to do today", or "morning briefing". Works from any directory without requiring Obsidian to be running.
tools
Provides a quick status snapshot of all GitHub repositories in a configured organisation — active, dormant, stalled — plus open pull requests and issues. Terminal output only, optimised for speed. Activate when the user runs "/project-pulse", asks "what is the status of my GitHub projects", "show me my repos", "which projects are active", "project overview", "GitHub pulse", or "what is happening in [org]". Works from any directory.