Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .claude/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add nowork-studio/notfair-plugin --skill gemini -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .agents/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add nowork-studio/notfair-plugin --skill gemini -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .cursor/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add nowork-studio/notfair-plugin --skill gemini -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .gemini/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add nowork-studio/notfair-plugin --skill gemini -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .github/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add nowork-studio/notfair-plugin --skill gemini -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "gemini" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/gemini into .opencode/skills/gemini/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
gemini
GitHub stars
3.9k
Used in
1 other repo
Token cost
~2.7k tokens
SKILL.md length
631 words
Files
2
Skills in repo
48
Repo updated
First seen
Licence
MIT
At a glance
Gets a second opinion from Google's Gemini CLI on code, Google Ads changes and SEO metadata, in review, challenge or consult mode.
Works in 6 steps: Detect Gemini CLI → Detect Mode → Detect Change Type → …
Getting an independent review of Google Ads campaign, bid or budget changes
SKILL.md covers Step 0 — Detect Gemini CLI, Step 1 — Detect Mode, Step 2 — Detect Change Type and Step 3 — Build the Context, plus 2 more sections
Calls git and gemini
What it does
The agent launches the Gemini CLI as an independent reviewer of work Claude has just done, aiming to add Google-ecosystem knowledge that matters for Ads, Search Console and SEO decisions. It handles three kinds of change: code diffs, Google Ads changes such as campaign structure, bids, keywords, ad copy and budgets, and SEO metadata changes such as title tags, meta descriptions, schema markup, robots directives and sitemaps.
Three modes are chosen from your wording. Review is a pass or fail gate, challenge is an adversarial attempt to break the changes, and consult is open Q&A. When the request is ambiguous the agent reviews if there is a diff and consults if there is only a question. The first step checks that the `gemini` command exists and, if it does not, stops with install instructions through npm and a one-time Google sign-in. The excerpt is cut off during change-type detection, and an `evals/evals.json` file is included.
When your agent uses it
Getting an independent review of Google Ads campaign, bid or budget changes
Stress-testing SEO metadata updates before they go live
Asking Gemini a strategy question about keywords or campaign structure
Cross-checking a code diff with a different AI model
Example prompts
“Gemini review the negative keyword changes I just made to the campaign.”
“Ask Gemini whether the new title tags and meta descriptions follow SEO best practices.”
“Have Gemini challenge my bid and budget changes and try to find holes.”
“Get a second opinion from Gemini on this diff before I merge.”
Requirements
Gemini CLI installed with `npm install -g @google/gemini-cli`
A Google account to authenticate the Gemini CLI
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1a53d4e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
gemini
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gemini Cross-Model Second Opinion loads about 2.7k tokens when it runs. Until then it costs about 220 tokens; SKILL.md has 631 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~220
When it runs· the whole SKILL.md, loaded when a task matches
~2.7k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/gemini/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gemini
description
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini on Google Ads strategy, SEO best practices, or implementation questions). Use when the user says "gemini review", "ask gemini", "gemini challenge", "second opinion from gemini", "consult gemini", "stress test with gemini", "what would gemini say", "cross-model review", or "get another opinion". Voice aliases: "gem", "gemini check". Especially useful for Google Ads changes, SEO metadata updates, campaign structure decisions, keyword strategies, and bid/budget changes — Gemini has native Google ecosystem knowledge that complements Claude's analysis.
argument-hint
'review', 'challenge', or 'consult' + optional context
triggers
gemini, gemini review, gemini challenge, gemini consult, ask gemini, second opinion gemini, stress test gemini, gem review, gem consult
Gemini — Cross-Model Second Opinion
You are orchestrating a cross-model review by launching Google's Gemini CLI as
an independent reviewer. Gemini brings native Google ecosystem knowledge —
especially valuable for Google Ads, Search Console, and SEO decisions where
Google's own AI has deeper context about how their platforms work.
Unlike the code-only review pattern, this skill handles three types of
changes:
Code changes — diffs, new files, refactors
Google Ads changes — campaign structure, bid strategies, keyword lists, negative keywords, ad copy, budget allocation
SEO metadata changes — title tags, meta descriptions, schema markup, robots directives, sitemap updates, content rewrites
"consult", "ask", "what does gemini think", "opinion", "advice", "strategy"
If ambiguous: default to review for changes that exist in the diff, or
consult if the user is asking a question with no pending changes.
Step 2 — Detect Change Type
Determine what kind of changes are being reviewed. Check in this order:
2a — Check for Google Ads changes
Look for signs of Ads-related work in the current conversation context:
Recent MCP tool calls to universal mcp__NotFair__google_ads_* tools or a supported dedicated Google Ads namespace
Discussion of campaigns, keywords, bids, budgets, ad copy, negative keywords
Files like .notfair/change-log.json or Ads-related config changes
If found, set CHANGE_TYPE=google-ads.
2b — Check for SEO metadata changes
Look for:
Recent calls to SEO skills (seo-analysis, meta-tags-optimizer, schema-markup-generator)
Discussion of title tags, meta descriptions, schema markup, robots.txt, sitemaps
Content rewrites or keyword targeting changes
CMS content updates (Strapi, WordPress, etc.)
If found, set CHANGE_TYPE=seo.
2c — Check for code changes
bash
git diff --stat HEAD 2>/dev/null || echo "NO_GIT_DIFF"
If there's a diff, set CHANGE_TYPE=code.
2d — Mixed or unclear
If multiple types are present, set CHANGE_TYPE=mixed. If nothing is found and
mode is consult, set CHANGE_TYPE=consult-only.
Step 3 — Build the Context
Assemble the context payload that Gemini will review. Tailor it to the change type.
Show full SKILL.md (258 more words)Show less
For google-ads changes:
Summarize the proposed Ads changes in a structured block:
GOOGLE ADS CHANGE SUMMARY
==========================
Account: [account name/ID if known]
Change type: [campaign creation | bid adjustment | keyword changes | negative keywords | ad copy | budget | targeting | etc.]
BEFORE (current state):
[Describe current campaign/keyword/bid state]
AFTER (proposed changes):
[Describe what will change]
BUSINESS CONTEXT:
[Goal of the change — CPA target, ROAS goal, traffic objective, etc.]
For seo changes:
SEO CHANGE SUMMARY
==================
Site: [URL]
Change type: [title tags | meta descriptions | schema markup | content rewrite | robots.txt | sitemap | etc.]
BEFORE (current state):
[Current metadata/content]
AFTER (proposed changes):
[New metadata/content]
TARGET KEYWORDS:
[Keywords being targeted, if applicable]
SEARCH INTENT:
[Informational / navigational / commercial / transactional]
For code changes:
bash
BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown")
DIFF=$(git diff HEAD 2>/dev/null)
STAT=$(git diff --stat HEAD 2>/dev/null)
Combine the diff stat and full diff into the context.
For mixed changes:
Combine all applicable sections above.
Step 4 — Run Gemini
Build and execute the Gemini CLI command based on mode and change type.
Review Mode
bash
gemini -p "You are a senior reviewer with deep expertise in Google's advertising platform, Google Search, and SEO best practices. You are reviewing proposed changes for correctness, effectiveness, and potential risks.
CHANGE TYPE: ${CHANGE_TYPE}
${CONTEXT}
Evaluate these changes and produce a structured review:
1. VERDICT: PASS or FAIL (use FAIL if any blocking issue exists)
2. BLOCKING ISSUES (if any):
- Issue, why it matters, and how to fix it
3. WARNINGS (non-blocking but worth considering):
- Concern and recommendation
4. STRENGTHS:
- What the changes do well
For Google Ads changes, specifically check:
- Policy compliance (disapprovals, trademark issues, restricted content)
- Budget efficiency (is spend allocated to highest-intent keywords?)
- Keyword conflicts (cannibalization, broad match pitfalls, missing negatives)
- Landing page alignment (do ads match what the page delivers?)
- Bid strategy fit (does the strategy match the campaign goal?)
For SEO changes, specifically check:
- Title tag length (under 60 chars) and keyword placement (front-loaded?)
- Meta description length (under 160 chars) and call-to-action presence
- Schema markup validity and completeness
- Potential keyword cannibalization across pages
- Search intent alignment (does the content match what users expect?)
- E-E-A-T signals (expertise, experience, authoritativeness, trustworthiness)
- Internal linking opportunities missed
For code changes, check:
- Correctness and edge cases
- Security issues
- Performance concerns
- Breaking changes" 2>&1
Capture the output. If the exit code is non-zero, report the error to the user
and suggest checking gemini authentication.
Challenge Mode
bash
gemini -p "You are a seasoned and skeptical growth advisor who has managed eight-figure Google Ads budgets and scaled organic traffic for major brands. You have expert-level knowledge of Google's latest policies — Ads editorial standards, Performance Max behavior, broad match changes, Search quality guidelines, spam policies, Core Web Vitals thresholds, and structured data requirements.
Your role is devil's advocate. The team is proposing changes and they want you to pressure-test them before committing. Do not be agreeable — your value is in catching what optimism misses. Evaluate based on evidence, data, and your experience with how Google's systems actually behave (not how documentation says they should).
CHANGE TYPE: ${CHANGE_TYPE}
${CONTEXT}
For each proposed change:
1. STATE THE ASSUMPTION — What is the team assuming will happen?
2. CHALLENGE IT — Why might that assumption be wrong? Cite specific Google policy, algorithm behavior, or auction mechanics where relevant. Reference real patterns you'd expect to see in the data.
3. WHAT DOES THE DATA SAY? — What metrics or signals should the team check before and after to validate this change? Be specific (e.g. 'compare impression share lost to rank before and 14 days after', not 'monitor performance').
4. VERDICT — For each change: SOUND, RISKY, or RETHINK. One sentence explaining why.
Finally, give an overall honest opinion: is this set of changes worth shipping as-is, or should the team pause and address specific concerns first? Be concise and professional — no filler, no hedging." 2>&1
Consult Mode
bash
gemini -p "You are a Google Ads and SEO expert consultant with deep knowledge of Google's ecosystem — Search algorithms, Ads auction mechanics, Search Console, and web performance. The user wants your independent perspective.
CONTEXT:
${CONTEXT}
USER QUESTION:
${USER_QUESTION}
Provide a clear, opinionated answer. If you disagree with a proposed approach, say so directly and explain why. Draw on Google-specific knowledge — ad auction dynamics, search ranking factors, Quality Score mechanics, Core Web Vitals thresholds, etc." 2>&1
Step 5 — Present Results
5a — Format the Gemini output
Present Gemini's response with a clear header:
Gemini Review (${CHANGE_TYPE} | ${MODE} mode)
[Gemini's formatted output]
5b — Cross-model analysis (if Claude already reviewed)
If Claude has already reviewed the same changes (e.g., via /notfair:seo-analysis
or /notfair:google-ads-audit earlier in the conversation), produce a cross-model
comparison:
Cross-Model Analysis: Claude vs Gemini
Overlapping findings (both flagged):
[Finding 1]
[Finding 2]
Claude-only findings:
[Finding that only Claude caught]
Gemini-only findings:
[Finding that only Gemini caught]
Disagreements (if any):
[Topic]: Claude says X, Gemini says Y
Overlapping findings have higher confidence — they should be addressed first.
Unique findings from either model are worth investigating. Disagreements should
be flagged to the user for a judgment call.
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nowork-studio/notfair-plugin, which our catalogue first saw on October 7, 2026.
Gemini Cross-Model Second Opinion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Gemini Cross-Model Second Opinion compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Gemini Cross-Model Second Opinion this skillnowork-studio/notfair-plugin
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
Direct access to Google's own SEO data via Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, GA4 organic…
Crawls a website with a bundled Python script to find broken internal and outbound links, then reports them by status code with the pages they appear on.
Finds, scores and groups keywords from a seed term or niche for SEO and AI search content strategies, with intent labels, difficulty estimates and topic clusters.
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
Gets a second opinion from Google's Gemini CLI on code, Google Ads changes and SEO metadata, in review, challenge or consult mode. The agent launches the Gemini CLI as an independent reviewer of work Claude has just done, aiming to add Google-ecosystem knowledge that matters for Ads, Search Console and SEO decisions. It handles three kinds of change: code diffs, Google Ads changes such as campaign structure, bids, keywords, ad copy and budgets, and SEO metadata changes such as title tags, meta descriptions, schema markup, robots directives and sitemaps.
When should I use Gemini Cross-Model Second Opinion?
Gemini Cross-Model Second Opinion fits situations like: getting an independent review of Google Ads campaign, bid or budget changes; stress-testing SEO metadata updates before they go live; asking Gemini a strategy question about keywords or campaign structure; cross-checking a code diff with a different AI model.
How do I install Gemini Cross-Model Second Opinion in Claude Code?
Run `npx skills add nowork-studio/notfair-plugin --skill gemini -a claude-code`. Or copy the skill folder (gemini in nowork-studio/notfair-plugin) into .claude/skills/gemini in your project. Claude Code loads it when a task matches its description.
How do I install Gemini Cross-Model Second Opinion in Codex?
Run `npx skills add nowork-studio/notfair-plugin --skill gemini -a codex`. Or copy the skill folder (gemini in nowork-studio/notfair-plugin) into .agents/skills/gemini in your project. Codex loads it when a task matches its description.
Can I use Gemini Cross-Model Second Opinion in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nowork-studio/notfair-plugin --skill gemini -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gemini, .gemini/skills/gemini, .github/skills/gemini and .opencode/skills/gemini in your project.
What does Gemini Cross-Model Second Opinion need to run?
Going by SKILL.md and its folder, Gemini Cross-Model Second Opinion needs the command-line tools its instructions call (git and gemini). Our summary lists: Gemini CLI installed with `npm install -g @google/gemini-cli`; A Google account to authenticate the Gemini CLI.
Does Gemini Cross-Model Second Opinion access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Gemini Cross-Model Second Opinion safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gemini Cross-Model Second Opinion use?
Gemini Cross-Model Second Opinion is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gemini Cross-Model Second Opinion use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gemini Cross-Model Second Opinion?
Skills that share tags, products or a category with Gemini Cross-Model Second Opinion: Blog Google (AgriciDaniel/claude-blog, 2.3k stars), SEO Google (seranking/seo-skills, 160 stars), Openclaw Marketing Skills (LeoYeAI/openclaw-marketing-skills, 1k stars) and Write Provider Skill (superdesigndev/treg, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gemini Cross-Model Second Opinion?
nowork-studio (a GitHub organization) maintains it in nowork-studio/notfair-plugin, which has 3,908 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 1, 2026.
Source: nowork-studio/notfair-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.