gemini-extension-development
Expert guide for building and managing Gemini CLI Extensions. Covers extension anatomy, GEMINI.md context, commands, MCP integration, and publishing. Use when creating Gemini extensions, linking local extensions, packaging MCP servers, or installing extensions from GitHub. Delegates to gemini-cli-docs.
What this skill does
# Gemini Extension Development ## Documentation Delegation > **Documentation Source:** For authoritative extension syntax and current features, query `gemini-cli-docs` skill. > This skill provides development guidance; `gemini-cli-docs` provides official Gemini CLI documentation. ## Overview Expert skill for creating, testing, and distributing Gemini CLI Extensions. Extensions are the primary plugin mechanism for Gemini. ## When to Use This Skill **Keywords:** gemini extension, create extension, gemini extensions link, extension gallery, context files, extension commands, extension releasing, uninstall extension **Use this skill when:** - Creating a new extension (`gemini extensions create`) - Linking a local extension for development (`gemini extensions link`) - Packaging MCP servers into extensions - Adding custom slash commands (`.toml`) to extensions - Installing extensions from GitHub or local paths - Releasing extensions via Git or GitHub Releases ## Extension Anatomy An extension can contain: 1. **`extension.yaml`:** Manifest file. 2. **`GEMINI.md`:** Context "playbook" for the model. 3. **`package.json`:** Dependencies (if using Node.js/TypeScript). **Note:** Use the Unified Google Gen AI SDK (e.g., `google-genai`) as `google-generativeai` is deprecated. 4. **MCP Servers:** Embedded tools. 5. **Commands:** `*.toml` files defining custom slash commands. 6. **Tool Restrictions:** `excludeTools` configuration. ## Development Workflow 1. **Create:** `gemini extensions create my-extension` 2. **Link:** `cd my-extension && gemini extensions link .` (Enables hot-reloading) 3. **Test:** Run `gemini` and use the new capabilities. 4. **Publish:** Push to GitHub (installable via URL). ## Keyword Registry (Delegates to gemini-cli-docs) | Topic | Query Keywords | | :--- | :--- | | **Creation** | `create extension`, `extension template` | | **Manifest** | `extension.yaml schema`, `extension manifest` | | **Commands** | `extension slash commands`, `toml commands` | | **Linking** | `gemini extensions link`, `local extension dev` | | **Releasing** | `extension releasing git`, `github release extension` | | **Management** | `uninstall extension`, `update extension` | ## Quick Decision Tree **What do you want to do?** 1. **Start a New Extension** -> Query `gemini-cli-docs`: "create extension boilerplate" 2. **Test Locally** -> Query `gemini-cli-docs`: "link local extension" 3. **Add a Command** -> Query `gemini-cli-docs`: "define command in extension" 4. **Bundle an MCP Server** -> Query `gemini-cli-docs`: "extension mcp server" 5. **Install an Extension** -> Query `gemini-cli-docs`: "install extension from url" 6. **Release an Extension** -> Query `gemini-cli-docs`: "extension releasing git vs github" ## Test Scenarios ### Scenario 1: Create Extension **Query**: "How do I create a new Gemini CLI extension?" **Expected Behavior**: - Skill activates on "create extension" - Delegates to gemini-cli-docs for template command **Success Criteria**: User receives `gemini extensions create` syntax ### Scenario 2: Link for Development **Query**: "How do I test my Gemini extension locally?" **Expected Behavior**: - Skill activates on "test extension" or "link extension" - Provides `gemini extensions link .` workflow **Success Criteria**: User receives local development workflow ### Scenario 3: Release Extension **Query**: "How do I publish my Gemini extension?" **Expected Behavior**: - Skill activates on "release extension" or "publish" - Delegates to docs for Git/GitHub release options **Success Criteria**: User receives release workflow options ## References **Official Documentation:** Query `gemini-cli-docs` for: - "extensions" - "extension development" ## Version History - v1.1.0 (2025-12-01): Added Test Scenarios section - v1.0.0 (2025-11-25): Initial release
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.