Route `/gemini ...` requests to the Cursor headless CLI for one-shot autonomous execution. Use when the user explicitly invokes `/gemini` or asks to hand a task off to Cursor agent. Preserves the prompt verbatim, runs in headless print mode, and returns Cursor's output.
Scanned 5/27/2026
Install via CLI
openskills install petekp/claude-code-setup---
name: gemini
description: Route `/gemini ...` requests to the Cursor headless CLI for one-shot autonomous execution. Use when the user explicitly invokes `/gemini` or asks to hand a task off to Cursor agent. Preserves the prompt verbatim, runs in headless print mode, and returns Cursor's output.
---
# Gemini
Use the Cursor headless CLI (`cursor agent --print`) for one-shot autonomous execution.
## Workflow
1. Strip the leading `/gemini` token and preserve everything after it verbatim.
2. If the remaining prompt is empty, ask the user what Cursor should do.
3. Resolve `scripts/run-cursor.sh` relative to this skill directory and pipe the prompt to it on stdin.
4. Share Cursor's output with the user.
5. If Cursor changed files or made a concrete recommendation, summarize the important result in plain language.
## Invocation
Default invocation from the current working directory:
```bash
PROMPT="<everything after /gemini>"
printf '%s' "$PROMPT" | "<skill-dir>/scripts/run-cursor.sh"
```
Useful options:
- `--cd /path/to/project` to run Cursor against a different working directory
- `--mode plan` for read-only planning/analysis (no file edits)
- `--mode ask` for Q&A explanations (read-only)
- `--model <model>` to override the default model (e.g., `gpt-5`, `sonnet-4`, `sonnet-4-thinking`)
## Behavior
The helper script:
- checks that `cursor` is available on `PATH`
- uses `--print --force --trust --output-format text` for clean headless execution
- uses `--workspace` to set the working directory
- captures stdout and stderr separately to a temp directory
- returns only Cursor's text output on success
- fails clearly if Cursor exits non-zero or produces no output
## Notes
- Do not describe this as a background dispatch unless you are actually using a background-capable shell tool.
- If Cursor fails, show the relevant error output instead of silently retrying.
- If `cursor` is missing, tell the user that Cursor CLI is not installed or not on `PATH`.
- Authentication uses the `CURSOR_API_KEY` env var or prior `cursor agent login`.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.