gemini-writer
Delegate large-context writing tasks to Gemini's 1M token window. Send an entire manuscript + detailed instructions in a single pass. Use for book rewrites, structural refactoring, redundancy analysis, and any writing task where the AI needs to see everything at once.
What this skill does
# Gemini Writer
Leverage Gemini 2.5 Pro's 1M token context window for writing tasks that exceed what Claude can hold in a single context. The key advantage: Gemini can read the ENTIRE manuscript plus all annotations, voice guides, and editorial instructions in a single pass, then produce a rewritten chapter that accounts for everything at once.
## When to Use
- **Book manuscript rewrites** — when the author has annotations across multiple chapters and cross-chapter issues need to be resolved simultaneously
- **Structural refactoring** — moving sections between chapters, resolving redundancy, reordering content
- **Voice-consistent rewrites** — when you have a voice guide + source material + current draft and need a revision that respects all three
- **Batch processing** — rewriting multiple chapters one at a time, but with full manuscript context for each
## When NOT to Use
- Quick edits to a single paragraph (just use Claude directly)
- Tasks requiring web search or real-time information (use deep-research instead)
- Tasks where the total context is under 100K tokens (Claude handles this fine)
## Architecture
The script sends content to Gemini's `generateContent` API (not the Interactions/research API). Two modes:
### Single-Pass Mode
Send everything, get one big output. Best for analysis tasks (redundancy audit, structural plan).
### Batch Mode (Recommended for Rewrites)
Send full manuscript as context, but process ONE chapter at a time. This means:
- Gemini sees everything (all chapters, all annotations, all instructions)
- But it only outputs one chapter per call
- This keeps output quality high (no truncation) while maintaining full cross-chapter awareness
## Workflow
### 1. Prepare the Prompt File
Create a markdown file with detailed instructions. Two levels:
**System instruction** (optional, `--system`): Voice guide, style rules, constraints that apply to every chapter.
**Prompt** (`--prompt`): Specific task instructions — what to fix, what to preserve, what to move, what annotations mean.
### 2. Dry Run
Always start with a dry run to verify token counts:
```bash
python3 .claude/skills/gemini-writer/scripts/gemini-writer.py \
--prompt prompt.md \
--context manuscript/revised/ \
--dry-run
```
### 3. Execute
**Batch mode (one chapter at a time):**
```bash
python3 .claude/skills/gemini-writer/scripts/gemini-writer.py \
--prompt prompt.md \
--system voice-guide.md \
--context manuscript/revised/ \
--output manuscript/v3/ \
--batch
```
**Single chapter:**
```bash
python3 .claude/skills/gemini-writer/scripts/gemini-writer.py \
--prompt prompt.md \
--context manuscript/revised/ \
--output manuscript/v3/ \
--batch --chapter 01-introduction.md
```
### 4. Review
Compare outputs against originals. Gemini's rewrites should be treated as strong first drafts that need human editorial review.
## Prompt Engineering Tips
1. **Be explicit about annotations.** Tell Gemini exactly what `{}` means: "Text in curly braces `{}` are the author's editorial comments. Execute these instructions, don't reproduce them."
2. **Give voice samples.** Include 2-3 paragraphs of the author's best writing and say "match this voice."
3. **Specify what to preserve.** Gemini will rewrite aggressively unless you tell it what's working. Say "The following sections are strong and should be preserved with minimal changes: [list]."
4. **Use the system instruction for invariants.** Voice guide, source material rules, theological constraints — anything that applies to every chapter goes in `--system`.
5. **Order matters.** Put the most important instructions first in the prompt. Gemini, like all LLMs, attends more to the beginning.
## Cost & Performance
- **Model:** `gemini-3-pro-preview` (falls back to `gemini-2.5-pro-preview-06-05`)
- **Input cost:** ~$1.25/1M input tokens, ~$10/1M output tokens (as of Feb 2026)
- **Typical manuscript rewrite:** 6 chapters × ~15K tokens each = ~90K input + ~60K output ≈ $0.75
- **Time:** 30-120 seconds per chapter depending on length
- **Max output:** 65,536 tokens per call (~50K words — more than enough for a chapter)
## Script Location
`.claude/skills/gemini-writer/scripts/gemini-writer.py`
Requires: `GEMINI_API_KEY` env var (set in `~/.zshrc`), `httpx` (auto-installed on first run)
Related in AI Agents
skill-development
IncludedComprehensive 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.
reprompter
IncludedTransform 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.
adaptive-compaction
IncludedAdaptive 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.
agent-skill-creator
IncludedCreate 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.
llm-wiki
IncludedUse 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.
skill-master
IncludedAgent 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.