@mthanh/vespercli 1.8.0 → 2.0.0

package/assets/prompts/repo-story-time/repo-story-time.prompt.md

@@ -1,156 +0,0 @@
----
-agent: 'agent'
-description: 'Generate a comprehensive repository summary and narrative story from commit history'
-tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'web/githubRepo', 'execute/getTerminalOutput', 'execute/runInTerminal', 'read/terminalLastCommand', 'read/terminalSelection', 'execute/createAndRunTask', 'execute/runTask', 'read/getTaskOutput', 'search', 'search/searchResults', 'read/terminalLastCommand', 'read/terminalSelection']
----
-
-
-## Role
-
-You're a senior technical analyst and storyteller with expertise in repository archaeology, code pattern analysis, and narrative synthesis. Your mission is to transform raw repository data into compelling technical narratives that reveal the human stories behind the code.
-
-## Task
-
-Transform any repository into a comprehensive analysis with two deliverables:
-
-1. **REPOSITORY_SUMMARY.md** - Technical architecture and purpose overview
-2. **THE_STORY_OF_THIS_REPO.md** - Narrative story from commit history analysis
-
-**CRITICAL**: You must CREATE and WRITE these files with complete markdown content. Do NOT output the markdown content in the chat - use the `editFiles` tool to create the actual files in the repository root directory.
-
-## Methodology
-
-### Phase 1: Repository Exploration
-
-**EXECUTE these commands immediately** to understand the repository structure and purpose:
-
-1. Get repository overview by running:
-   `Get-ChildItem -Recurse -Include "*.md","*.json","*.yaml","*.yml" | Select-Object -First 20 | Select-Object Name, DirectoryName`
-
-2. Understand project structure by running:
-   `Get-ChildItem -Recurse -Directory | Where-Object {$_.Name -notmatch "(node_modules|\.git|bin|obj)"} | Select-Object -First 30 | Format-Table Name, FullName`
-
-After executing these commands, use semantic search to understand key concepts and technologies. Look for:
-- Configuration files (package.json, pom.xml, requirements.txt, etc.)
-- README files and documentation
-- Main source directories
-- Test directories
-- Build/deployment configurations
-
-### Phase 2: Technical Deep Dive
-Create comprehensive technical inventory:
-- **Purpose**: What problem does this repository solve?
-- **Architecture**: How is the code organized?
-- **Technologies**: What languages, frameworks, and tools are used?
-- **Key Components**: What are the main modules/services/features?
-- **Data Flow**: How does information move through the system?
-
-### Phase 3: Commit History Analysis
-
-**EXECUTE these git commands systematically** to understand repository evolution:
-
-**Step 1: Basic Statistics** - Run these commands to get repository metrics:
-- `git rev-list --all --count` (total commit count)
-- `(git log --oneline --since="1 year ago").Count` (commits in last year)
-
-**Step 2: Contributor Analysis** - Run this command:
-- `git shortlog -sn --since="1 year ago" | Select-Object -First 20`
-
-**Step 3: Activity Patterns** - Run this command:
-- `git log --since="1 year ago" --format="%ai" | ForEach-Object { $_.Substring(0,7) } | Group-Object | Sort-Object Count -Descending | Select-Object -First 12`
-
-**Step 4: Change Pattern Analysis** - Run these commands:
-- `git log --since="1 year ago" --oneline --grep="feat|fix|update|add|remove" | Select-Object -First 50`
-- `git log --since="1 year ago" --name-only --oneline | Where-Object { $_ -notmatch "^[a-f0-9]" } | Group-Object | Sort-Object Count -Descending | Select-Object -First 20`
-
-**Step 5: Collaboration Patterns** - Run this command:
-- `git log --since="1 year ago" --merges --oneline | Select-Object -First 20`
-
-**Step 6: Seasonal Analysis** - Run this command:
-- `git log --since="1 year ago" --format="%ai" | ForEach-Object { $_.Substring(5,2) } | Group-Object | Sort-Object Name`
-
-**Important**: Execute each command and analyze the output before proceeding to the next step.
-**Important**: Use your best judgment to execute additional commands not listed above based on the output of previous commands or the repository's specific content.
-
-### Phase 4: Pattern Recognition
-Look for these narrative elements:
-- **Characters**: Who are the main contributors? What are their specialties?
-- **Seasons**: Are there patterns by month/quarter? Holiday effects?
-- **Themes**: What types of changes dominate? (features, fixes, refactoring)
-- **Conflicts**: Are there areas of frequent change or contention?
-- **Evolution**: How has the repository grown and changed over time?
-
-## Output Format
-
-### REPOSITORY_SUMMARY.md Structure
-```markdown
-# Repository Analysis: [Repo Name]
-
-## Overview
-Brief description of what this repository does and why it exists.
-
-## Architecture
-High-level technical architecture and organization.
-
-## Key Components
-- **Component 1**: Description and purpose
-- **Component 2**: Description and purpose
-[Continue for all major components]
-
-## Technologies Used
-List of programming languages, frameworks, tools, and platforms.
-
-## Data Flow
-How information moves through the system.
-
-## Team and Ownership
-Who maintains different parts of the codebase.
-```
-
-### THE_STORY_OF_THIS_REPO.md Structure
-```markdown
-# The Story of [Repo Name]
-
-## The Chronicles: A Year in Numbers
-Statistical overview of the past year's activity.
-
-## Cast of Characters
-Profiles of main contributors with their specialties and impact.
-
-## Seasonal Patterns
-Monthly/quarterly analysis of development activity.
-
-## The Great Themes
-Major categories of work and their significance.
-
-## Plot Twists and Turning Points
-Notable events, major changes, or interesting patterns.
-
-## The Current Chapter
-Where the repository stands today and future implications.
-```
-
-## Key Instructions
-
-1. **Be Specific**: Use actual file names, commit messages, and contributor names
-2. **Find Stories**: Look for interesting patterns, not just statistics
-3. **Context Matters**: Explain why patterns exist (holidays, releases, incidents)
-4. **Human Element**: Focus on the people and teams behind the code
-5. **Technical Depth**: Balance narrative with technical accuracy
-6. **Evidence-Based**: Support observations with actual git data
-
-## Success Criteria
-
-- Both markdown files are **ACTUALLY CREATED** with complete, comprehensive content using the `editFiles` tool
-- **NO markdown content should be output to chat** - all content must be written directly to the files
-- Technical summary accurately represents repository architecture
-- Narrative story reveals human patterns and interesting insights
-- Git commands provide concrete evidence for all claims
-- Analysis reveals both technical and cultural aspects of development
-- Files are ready to use immediately without any copy/paste from chat dialog
-
-## Critical Final Instructions
-
-**DO NOT** output markdown content in the chat. **DO** use the `editFiles` tool to create both files with complete content. The deliverables are the actual files, not chat output.
-
-Remember: Every repository tells a story. Your job is to uncover that story through systematic analysis and present it in a way that both technical and non-technical audiences can appreciate.

package/assets/skills/.env.example

@@ -1,32 +0,0 @@
-# Claude Code - Project-Level Environment Variables
-# Priority: process.env > .claude/.env > .claude/hooks/.env
-# Copy this file to .env and set your API keys and configuration
-
-# ============================================
-# Claude Code Notification Hooks
-# ============================================
-# Discord Webhook URL (for Discord notifications)
-# Get from: Server Settings → Integrations → Webhooks → New Webhook
-DISCORD_WEBHOOK_URL=
-
-# Telegram Bot Token (for Telegram notifications)
-# Get from: @BotFather in Telegram
-TELEGRAM_BOT_TOKEN=
-
-# Telegram Chat ID (your chat ID or group ID)
-# Get from: https://api.telegram.org/bot<BOT_TOKEN>/getUpdates
-TELEGRAM_CHAT_ID=
-
-# ============================================
-# Google Gemini API Key (for Gemini skills)
-# ============================================
-# Get your key at: https://aistudio.google.com/apikey
-GEMINI_API_KEY=your-gemini-api-key-here
-
-# ==== Vertex AI (Optional) ====
-# Uncomment to use Vertex AI instead of AI Studio
-# GEMINI_USE_VERTEX=true
-# VERTEX_PROJECT_ID=your-gcp-project-id
-# VERTEX_LOCATION=us-central1
-
-# Add other API keys and configuration as needed

package/assets/skills/.mcp.json.example

@@ -1,19 +0,0 @@
-{
-  "mcpServers": {
-    "context7": {
-      "command": "npx",
-      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]
-    },
-    "human-mcp": {
-      "command": "npx",
-      "args": ["@goonnguyen/human-mcp"],
-      "env": {
-        "GOOGLE_GEMINI_API_KEY": "your_gemini_api_key_here"
-      }
-    },
-    "chrome-devtools": {
-      "command": "npx",
-      "args": ["-y", "chrome-devtools-mcp@latest"]
-    }
-  }
-}

package/assets/skills/README.md

@@ -1,111 +0,0 @@
-# Skills
-Skills are folders of instructions, scripts, and resources that Claude loads dynamically to improve performance on specialized tasks. Skills teach Claude how to complete specific tasks in a repeatable way, whether that's creating documents with your company's brand guidelines, analyzing data using your organization's specific workflows, or automating personal tasks.
-
-For more information, check out:
-- [What are skills?](https://support.claude.com/en/articles/12512176-what-are-skills)
-- [Using skills in Claude](https://support.claude.com/en/articles/12512180-using-skills-in-claude)
-- [How to create custom skills](https://support.claude.com/en/articles/12512198-creating-custom-skills)
-- [Equipping agents for the real world with Agent Skills](https://anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills)
-
-# About This Repository
-
-This repository contains example skills that demonstrate what's possible with Claude's skills system. These examples range from creative applications (art, music, design) to technical tasks (testing web apps, MCP server generation) to enterprise workflows (communications, branding, etc.).
-
-Each skill is self-contained in its own directory with a `SKILL.md` file containing the instructions and metadata that Claude uses. Browse through these examples to get inspiration for your own skills or to understand different patterns and approaches.
-
-The example skills in this repo are open source (Apache 2.0). We've also included the document creation & editing skills that power [Claude's document capabilities](https://www.anthropic.com/news/create-files) under the hood in the [`document-skills/`](./document-skills/) folder. These are source-available, not open source, but we wanted to share these with developers as a reference for more complex skills that are actively used in a production AI application.
-
-**Note:** These are reference examples for inspiration and learning. They showcase general-purpose capabilities rather than organization-specific workflows or sensitive content.
-
-## Disclaimer
-
-**These skills are provided for demonstration and educational purposes only.** While some of these capabilities may be available in Claude, the implementations and behaviors you receive from Claude may differ from what is shown in these examples. These examples are meant to illustrate patterns and possibilities. Always test skills thoroughly in your own environment before relying on them for critical tasks.
-
-# Example Skills
-
-This repository includes a diverse collection of example skills demonstrating different capabilities:
-
-## Creative & Design
-- **algorithmic-art** - Create generative art using p5.js with seeded randomness, flow fields, and particle systems
-- **canvas-design** - Design beautiful visual art in .png and .pdf formats using design philosophies
-- **slack-gif-creator** - Create animated GIFs optimized for Slack's size constraints
-
-## Development & Technical
-- **artifacts-builder** - Build complex claude.ai HTML artifacts using React, Tailwind CSS, and shadcn/ui components
-- **mcp-server** - Guide for creating high-quality MCP servers to integrate external APIs and services
-- **webapp-testing** - Test local web applications using Playwright for UI verification and debugging
-
-## Enterprise & Communication
-- **brand-guidelines** - Apply Anthropic's official brand colors and typography to artifacts
-- **internal-comms** - Write internal communications like status reports, newsletters, and FAQs
-- **theme-factory** - Style artifacts with 10 pre-set professional themes or generate custom themes on-the-fly
-
-## Meta Skills
-- **skill-creator** - Guide for creating effective skills that extend Claude's capabilities
-- **template-skill** - A basic template to use as a starting point for new skills
-
-# Document Skills
-
-The `document-skills/` subdirectory contains skills that Anthropic developed to help Claude create various document file formats. These skills demonstrate advanced patterns for working with complex file formats and binary data:
-
-- **docx** - Create, edit, and analyze Word documents with support for tracked changes, comments, formatting preservation, and text extraction
-- **pdf** - Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms
-- **pptx** - Create, edit, and analyze PowerPoint presentations with support for layouts, templates, charts, and automated slide generation
-- **xlsx** - Create, edit, and analyze Excel spreadsheets with support for formulas, formatting, data analysis, and visualization
-
-**Important Disclaimer:** These document skills are point-in-time snapshots and are not actively maintained or updated. Versions of these skills ship pre-included with Claude. They are primarily intended as reference examples to illustrate how Anthropic approaches developing more complex skills that work with binary file formats and document structures.
-
-# Try in Claude Code, Claude.ai, and the API
-
-## Claude Code
-You can register this repository as a Claude Code Plugin marketplace by running the following command in Claude Code:
-```
-/plugin marketplace add anthropics/skills
-```
-
-After installing the plugin, you can use the skill by just mentioning it. For instance, if you install the document-skills plugin from the marketplace, you can ask Claude Code to do something like: "use the pdf skill to extract the form fields from path/to/some-file.pdf"
-
-## Claude.ai
-
-These example skills are all already available to paid plans in Claude.ai. 
-
-To use any skill from this repository or upload custom skills, follow the instructions in [Using skills in Claude](https://support.claude.com/en/articles/12512180-using-skills-in-claude#h_a4222fa77b).
-
-## Claude API
-
-You can use Anthropic's pre-built skills, and upload custom skills, via the Claude API. See the [Skills API Quickstart](https://docs.claude.com/en/api/skills-guide#creating-a-skill) for more.
-
-# Creating a Basic Skill
-
-Skills are simple to create - just a folder with a `SKILL.md` file containing YAML frontmatter and instructions. You can use the **template-skill** in this repository as a starting point:
-
-```markdown
----
-name: my-skill-name
-description: A clear description of what this skill does and when to use it
----
-
-# My Skill Name
-
-[Add your instructions here that Claude will follow when this skill is active]
-
-## Examples
-- Example usage 1
-- Example usage 2
-
-## Guidelines
-- Guideline 1
-- Guideline 2
-```
-
-The frontmatter requires only two fields:
-- `name` - A unique identifier for your skill (lowercase, hyphens for spaces)
-- `description` - A complete description of what the skill does and when to use it
-
-The markdown content below contains the instructions, examples, and guidelines that Claude will follow. For more details, see [How to create custom skills](https://support.claude.com/en/articles/12512198-creating-custom-skills).
-
-# Partner Skills
-
-Skills are a great way to teach Claude how to get better at using specific pieces of software. As we see awesome example skills from partners, we may highlight some of them here:
-
-- **Notion** - [Notion Skills for Claude](https://www.notion.so/notiondevs/Notion-Skills-for-Claude-28da4445d27180c7af1df7d8615723d0)

package/assets/skills/aesthetic/manifest.json

@@ -1,14 +0,0 @@
-{
-  "name": "aesthetic",
-  "version": "1.0.0",
-  "generated": "2026-07-19T18:29:56.191Z",
-  "files": [
-    "SKILL.md",
-    "assets/design-guideline-template.md",
-    "assets/design-story-template.md",
-    "references/design-principles.md",
-    "references/design-resources.md",
-    "references/micro-interactions.md",
-    "references/storytelling-design.md"
-  ]
-}

package/assets/skills/ai-multimodal/SKILL.md

@@ -1,357 +0,0 @@
----
-name: ai-multimodal
-description: Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files (transcription with timestamps, summarization, speech understanding, music/sound analysis up to 9.5 hours), understand images (captioning, object detection, OCR, visual Q&A, segmentation), process videos (scene detection, Q&A, temporal analysis, YouTube URLs, up to 6 hours), extract from documents (PDF tables, forms, charts, diagrams, multi-page), generate images (text-to-image, editing, composition, refinement). Use when working with audio/video files, analyzing images or screenshots, processing PDF documents, extracting structured data from media, creating images from text prompts, or implementing multimodal AI features. Supports multiple models (Gemini 2.5/2.0) with context windows up to 2M tokens.
-license: MIT
-allowed-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
----
-
-# AI Multimodal Processing Skill
-
-Process audio, images, videos, documents, and generate images using Google Gemini's multimodal API. Unified interface for all multimedia content understanding and generation.
-
-## Core Capabilities
-
-### Audio Processing
-- Transcription with timestamps (up to 9.5 hours)
-- Audio summarization and analysis
-- Speech understanding and speaker identification
-- Music and environmental sound analysis
-- Text-to-speech generation with controllable voice
-
-### Image Understanding
-- Image captioning and description
-- Object detection with bounding boxes (2.0+)
-- Pixel-level segmentation (2.5+)
-- Visual question answering
-- Multi-image comparison (up to 3,600 images)
-- OCR and text extraction
-
-### Video Analysis
-- Scene detection and summarization
-- Video Q&A with temporal understanding
-- Transcription with visual descriptions
-- YouTube URL support
-- Long video processing (up to 6 hours)
-- Frame-level analysis
-
-### Document Extraction
-- Native PDF vision processing (up to 1,000 pages)
-- Table and form extraction
-- Chart and diagram analysis
-- Multi-page document understanding
-- Structured data output (JSON schema)
-- Format conversion (PDF to HTML/JSON)
-
-### Image Generation
-- Text-to-image generation
-- Image editing and modification
-- Multi-image composition (up to 3 images)
-- Iterative refinement
-- Multiple aspect ratios (1:1, 16:9, 9:16, 4:3, 3:4)
-- Controllable style and quality
-
-## Capability Matrix
-
-| Task | Audio | Image | Video | Document | Generation |
-|------|:-----:|:-----:|:-----:|:--------:|:----------:|
-| Transcription | ✓ | - | ✓ | - | - |
-| Summarization | ✓ | ✓ | ✓ | ✓ | - |
-| Q&A | ✓ | ✓ | ✓ | ✓ | - |
-| Object Detection | - | ✓ | ✓ | - | - |
-| Text Extraction | - | ✓ | - | ✓ | - |
-| Structured Output | ✓ | ✓ | ✓ | ✓ | - |
-| Creation | TTS | - | - | - | ✓ |
-| Timestamps | ✓ | - | ✓ | - | - |
-| Segmentation | - | ✓ | - | - | - |
-
-## Model Selection Guide
-
-### Gemini 2.5 Series (Recommended)
-- **gemini-2.5-pro**: Highest quality, all features, 1M-2M context
-- **gemini-2.5-flash**: Best balance, all features, 1M-2M context
-- **gemini-2.5-flash-lite**: Lightweight, segmentation support
-- **gemini-2.5-flash-image**: Image generation only
-
-### Gemini 2.0 Series
-- **gemini-2.0-flash**: Fast processing, object detection
-- **gemini-2.0-flash-lite**: Lightweight option
-
-### Feature Requirements
-- **Segmentation**: Requires 2.5+ models
-- **Object Detection**: Requires 2.0+ models
-- **Multi-video**: Requires 2.5+ models
-- **Image Generation**: Requires flash-image model
-
-### Context Windows
-- **2M tokens**: ~6 hours video (low-res) or ~2 hours (default)
-- **1M tokens**: ~3 hours video (low-res) or ~1 hour (default)
-- **Audio**: 32 tokens/second (1 min = 1,920 tokens)
-- **PDF**: 258 tokens/page (fixed)
-- **Image**: 258-1,548 tokens based on size
-
-## Quick Start
-
-### Prerequisites
-
-**API Key Setup**: Supports both Google AI Studio and Vertex AI.
-
-The skill checks for `GEMINI_API_KEY` in this order:
-1. Process environment: `export GEMINI_API_KEY="your-key"`
-2. Project root: `.env`
-3. `.claude/.env`
-4. `.claude/skills/.env`
-5. `.claude/skills/ai-multimodal/.env`
-
-**Get API key**: https://aistudio.google.com/apikey
-
-**For Vertex AI**:
-```bash
-export GEMINI_USE_VERTEX=true
-export VERTEX_PROJECT_ID=your-gcp-project-id
-export VERTEX_LOCATION=us-central1  # Optional
-```
-
-**Install SDK**:
-```bash
-pip install google-genai python-dotenv pillow
-```
-
-### Common Patterns
-
-**Transcribe Audio**:
-```bash
-python scripts/gemini_batch_process.py \
-  --files audio.mp3 \
-  --task transcribe \
-  --model gemini-2.5-flash
-```
-
-**Analyze Image**:
-```bash
-python scripts/gemini_batch_process.py \
-  --files image.jpg \
-  --task analyze \
-  --prompt "Describe this image" \
-  --output docs/assets/<output-name>.md \
-  --model gemini-2.5-flash
-```
-
-**Process Video**:
-```bash
-python scripts/gemini_batch_process.py \
-  --files video.mp4 \
-  --task analyze \
-  --prompt "Summarize key points with timestamps" \
-  --output docs/assets/<output-name>.md \
-  --model gemini-2.5-flash
-```
-
-**Extract from PDF**:
-```bash
-python scripts/gemini_batch_process.py \
-  --files document.pdf \
-  --task extract \
-  --prompt "Extract table data as JSON" \
-  --output docs/assets/<output-name>.md \
-  --format json
-```
-
-**Generate Image**:
-```bash
-python scripts/gemini_batch_process.py \
-  --task generate \
-  --prompt "A futuristic city at sunset" \
-  --output docs/assets/<output-file-name> \
-  --model gemini-2.5-flash-image \
-  --aspect-ratio 16:9
-```
-
-**Optimize Media**:
-```bash
-# Prepare large video for processing
-python scripts/media_optimizer.py \
-  --input large-video.mp4 \
-  --output docs/assets/<output-file-name> \
-  --target-size 100MB
-
-# Batch optimize multiple files
-python scripts/media_optimizer.py \
-  --input-dir ./videos \
-  --output-dir docs/assets/optimized \
-  --quality 85
-```
-
-**Convert Documents to Markdown**:
-```bash
-# Convert to PDF
-python scripts/document_converter.py \
-  --input document.docx \
-  --output docs/assets/document.md
-
-# Extract pages
-python scripts/document_converter.py \
-  --input large.pdf \
-  --output docs/assets/chapter1.md \
-  --pages 1-20
-```
-
-## Supported Formats
-
-### Audio
-- WAV, MP3, AAC, FLAC, OGG Vorbis, AIFF
-- Max 9.5 hours per request
-- Auto-downsampled to 16 Kbps mono
-
-### Images
-- PNG, JPEG, WEBP, HEIC, HEIF
-- Max 3,600 images per request
-- Resolution: ≤384px = 258 tokens, larger = tiled
-
-### Video
-- MP4, MPEG, MOV, AVI, FLV, MPG, WebM, WMV, 3GPP
-- Max 6 hours (low-res) or 2 hours (default)
-- YouTube URLs supported (public only)
-
-### Documents
-- PDF only for vision processing
-- Max 1,000 pages
-- TXT, HTML, Markdown supported (text-only)
-
-### Size Limits
-- **Inline**: <20MB total request
-- **File API**: 2GB per file, 20GB project quota
-- **Retention**: 48 hours auto-delete
-
-## Reference Navigation
-
-For detailed implementation guidance, see:
-
-### Audio Processing
-- `references/audio-processing.md` - Transcription, analysis, TTS
-  - Timestamp handling and segment analysis
-  - Multi-speaker identification
-  - Non-speech audio analysis
-  - Text-to-speech generation
-
-### Image Understanding
-- `references/vision-understanding.md` - Captioning, detection, OCR
-  - Object detection and localization
-  - Pixel-level segmentation
-  - Visual question answering
-  - Multi-image comparison
-
-### Video Analysis
-- `references/video-analysis.md` - Scene detection, temporal understanding
-  - YouTube URL processing
-  - Timestamp-based queries
-  - Video clipping and FPS control
-  - Long video optimization
-
-### Document Extraction
-- `references/document-extraction.md` - PDF processing, structured output
-  - Table and form extraction
-  - Chart and diagram analysis
-  - JSON schema validation
-  - Multi-page handling
-
-### Image Generation
-- `references/image-generation.md` - Text-to-image, editing
-  - Prompt engineering strategies
-  - Image editing and composition
-  - Aspect ratio selection
-  - Safety settings
-
-## Cost Optimization
-
-### Token Costs
-**Input Pricing**:
-- Gemini 2.5 Flash: $1.00/1M input, $0.10/1M output
-- Gemini 2.5 Pro: $3.00/1M input, $12.00/1M output
-- Gemini 1.5 Flash: $0.70/1M input, $0.175/1M output
-
-**Token Rates**:
-- Audio: 32 tokens/second (1 min = 1,920 tokens)
-- Video: ~300 tokens/second (default) or ~100 (low-res)
-- PDF: 258 tokens/page (fixed)
-- Image: 258-1,548 tokens based on size
-
-**TTS Pricing**:
-- Flash TTS: $10/1M tokens
-- Pro TTS: $20/1M tokens
-
-### Best Practices
-1. Use `gemini-2.5-flash` for most tasks (best price/performance)
-2. Use File API for files >20MB or repeated queries
-3. Optimize media before upload (see `media_optimizer.py`)
-4. Process specific segments instead of full videos
-5. Use lower FPS for static content
-6. Implement context caching for repeated queries
-7. Batch process multiple files in parallel
-
-## Rate Limits
-
-**Free Tier**:
-- 10-15 RPM (requests per minute)
-- 1M-4M TPM (tokens per minute)
-- 1,500 RPD (requests per day)
-
-**YouTube Limits**:
-- Free tier: 8 hours/day
-- Paid tier: No length limits
-- Public videos only
-
-**Storage Limits**:
-- 20GB per project
-- 2GB per file
-- 48-hour retention
-
-## Error Handling
-
-Common errors and solutions:
-- **400**: Invalid format/size - validate before upload
-- **401**: Invalid API key - check configuration
-- **403**: Permission denied - verify API key restrictions
-- **404**: File not found - ensure file uploaded and active
-- **429**: Rate limit exceeded - implement exponential backoff
-- **500**: Server error - retry with backoff
-
-## Scripts Overview
-
-All scripts support unified API key detection and error handling:
-
-**gemini_batch_process.py**: Batch process multiple media files
-- Supports all modalities (audio, image, video, PDF)
-- Progress tracking and error recovery
-- Output formats: JSON, Markdown, CSV
-- Rate limiting and retry logic
-- Dry-run mode
-
-**media_optimizer.py**: Prepare media for Gemini API
-- Compress videos/audio for size limits
-- Resize images appropriately
-- Split long videos into chunks
-- Format conversion
-- Quality vs size optimization
-
-**document_converter.py**: Convert documents to PDF
-- Convert DOCX, XLSX, PPTX to PDF
-- Extract page ranges
-- Optimize PDFs for Gemini
-- Extract images from PDFs
-- Batch conversion support
-
-Run any script with `--help` for detailed usage.
-
-## Resources
-
-- [Audio API Docs](https://ai.google.dev/gemini-api/docs/audio)
-- [Image API Docs](https://ai.google.dev/gemini-api/docs/image-understanding)
-- [Video API Docs](https://ai.google.dev/gemini-api/docs/video-understanding)
-- [Document API Docs](https://ai.google.dev/gemini-api/docs/document-processing)
-- [Image Gen Docs](https://ai.google.dev/gemini-api/docs/image-generation)
-- [Get API Key](https://aistudio.google.com/apikey)
-- [Pricing](https://ai.google.dev/pricing)