alexei-led/using-gemini
plugins/dev-tools/skills-pi/using-gemini/SKILL.md
Consult Gemini for second opinions, brainstorming, or web search. Use when user says "ask gemini", "gemini search", "get gemini opinion", or wants a second AI perspective.
$ install --global
skillsauthnpx skillsauth add alexei-led/claude-code-config using-geminiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 11, 2026, 3:44 AM187.8s1 file scanned
SKILL.md
- description:
- Consult Gemini for second opinions, brainstorming, or web search. Use
- disable-model-invocation:
- true
- name:
- using-gemini
- user-invocable:
- true
<!-- generated by scripts/build/generate-skills.py — edits to this file will be overwritten by `make build`. Edit the canonical SKILL.md (or add a SKILL.codex.md / SKILL.pi.md sidecar to diverge). -->
<!-- Pi platform guidance -->
<!-- Use Pi tool names exactly: read, bash, edit, write, ask_user_question, structured_output, todo, Agent, get_subagent_result, steer_subagent, web_search, web_answer, web_research. -->
<!-- Use Agent, get_subagent_result, and steer_subagent for delegated work. -->
<!-- Use ctx7 or npx ctx7@latest through bash when Context7 documentation lookup is required. -->
Gemini CLI Integration
Consult Google Gemini via CLI for second opinions, brainstorming, or web search.
Critical Workflow Rules
- When the user asks to "ask Gemini" or "gemini search", run the
geminiCLI when available; do not only suggest a command. - Scope what is sent. Do not send secrets, credentials, private code, or whole repos unless the user explicitly approves and the context is necessary.
- For second opinions, compare Gemini output against local code, requirements, ADRs, or other existing evidence. Gemini is critique, not authority.
- For web/search use, ask Gemini for recent examples with source URLs, then cross-check against official docs or local project constraints before recommending changes.
- Final synthesis must separate: agreements, disagreements, unsupported claims, and actionable next steps.
- If Gemini is unavailable, report the exact blocker and provide the command that would be run.
Usage
Run Gemini in non-interactive (headless) mode:
# General query
gemini -p "your question here"
# With specific model
gemini -m gemini-2.5-pro -p "your question"
# Pipe context into Gemini
cat file.go | gemini -p "review this code for issues"
When to Use
- Second opinion: Get Gemini's perspective on architecture, design, or code
- Web search: Ask Gemini to search for current information
- Brainstorming: Generate alternative approaches or ideas
- Media analysis: Describe images or analyze file content
Workflow
- Gather only the relevant context from the codebase if needed
- Formulate a clear, scoped prompt
- Run
gemini -p "prompt"for non-interactive response - Verify or cross-check Gemini's claims against local evidence or official sources
- Summarize agreements, disagreements, unsupported claims, and actionable next steps
Tips
- Keep prompts focused and specific for best results
- Pipe file content directly when asking about specific code
- Use
-mflag to select a specific Gemini model if needed
Related Skills
alexei-led/writing-shell
tools
VerifiedTrustedCommunity
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, TypeScript, Go, web code, or infrastructure operations.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/spec-flow
tools
VerifiedTrustedCommunity
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/operating-infra
testing
VerifiedTrustedCommunity
Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health. NOT for deploy/apply/rollback workflows (see deploying-infra). NOT for shell scripts or generic command pipelines (see writing-shell).
33SKILL.mdUpdated Jun 5, 2026
alexei-led/configuring-git-hygiene
development
VerifiedTrustedCommunity
Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating commits (use committing-code), cleaning branches/worktrees (use cleanup-git), or creating worktrees (use using-git-worktrees).
33SKILL.mdUpdated Jun 5, 2026