gemini-config-management
Expert guide for configuring Google Gemini CLI. Covers global vs project settings.json, Trusted Folders, Policy Engine, and environment variables. Use when configuring Gemini settings, managing trusted folders, setting up security policies, or troubleshooting configuration precedence. Delegates to gemini-cli-docs for official references.
What this skill does
# Gemini Configuration Management ## ๐จ MANDATORY: Invoke gemini-cli-docs First > **STOP - Before providing ANY response about Gemini configuration:** > > 1. **INVOKE** `gemini-cli-docs` skill > 2. **QUERY** for the specific configuration topic (e.g., "trusted folders", "settings.json schema") > 3. **BASE** all responses EXCLUSIVELY on official documentation loaded > > **Skipping this step results in outdated or incorrect information.** ## Overview Expert skill for managing Google Gemini CLI configuration. It handles the hierarchy of settings, security policies, and environment overrides. ## When to Use This Skill **Keywords:** gemini config, settings.json, .gemini folder, trusted folders, folder trust, security policy, environment variables, scope, global settings, project settings, telemetry, ui configuration **Use this skill when:** - Configuring `settings.json` (Global `~/.gemini/settings.json` or Project `.gemini/settings.json`) - Managing **Trusted Folders** (`security.folderTrust.enabled`) - Setting up **Policy Engine** rules - Configuring **UI & Telemetry** (mouse support, sticky headers, disable telemetry) - Troubleshooting configuration precedence (User > Project > Default) - Configuring proxy settings or network behaviors ## Configuration Scopes Gemini CLI uses a cascading configuration system: 1. **Global Scope:** `~/.gemini/settings.json` (User-wide defaults) 2. **Project Scope:** `.gemini/settings.json` (Per-project overrides) 3. **Environment Variables:** `GEMINI_*` (Runtime overrides) ## Trusted Folders Security The **Trusted Folders** feature is a critical security boundary. - **Enabled via:** `"security.folderTrust.enabled": true` in `settings.json`. - **States:** - **Trusted:** Full access (MCP, extensions, shell execution). - **Untrusted:** Restricted "Safe Mode" (No shell, no MCP, read-only). - **Storage:** Decisions saved in `~/.gemini/trustedFolders.json`. ## Keyword Registry (Delegates to gemini-cli-docs) | Topic | Query Keywords | | :--- | :--- | | **Settings Schema** | `settings.json schema`, `configuration options` | | **Trusted Folders** | `trusted folders`, `folder trust`, `safe mode` | | **Policy Engine** | `policy engine`, `execution policies`, `allow list` | | **Network** | `proxy settings`, `network configuration`, `timeout` | | **UI & Telemetry** | `telemetry configuration`, `mouse support`, `sticky headers` | ## Quick Decision Tree **What do you want to do?** 1. **Enable Trusted Folders** -> Query `gemini-cli-docs`: "enable trusted folders settings" 2. **Edit Global Settings** -> Query `gemini-cli-docs`: "global settings.json location" 3. **Override for Project** -> Query `gemini-cli-docs`: "project specific settings .gemini" 4. **Configure UI/Telemetry** -> Query `gemini-cli-docs`: "telemetry configuration settings" 5. **Debug Config** -> Query `gemini-cli-docs`: "debug configuration loading" ## Troubleshooting **Issue:** "My settings aren't applying." **Check:** Is the folder trusted? If Untrusted, project settings are IGNORED. **Action:** Run `/permissions` to check trust status. ## Test Scenarios ### Scenario 1: Global Settings **Query**: "Where is the Gemini CLI global settings file?" **Expected Behavior**: - Skill activates on "settings.json" or "global settings" - Provides `~/.gemini/settings.json` path **Success Criteria**: User receives correct path and configuration options ### Scenario 2: Trusted Folders **Query**: "How do I enable trusted folders in Gemini CLI?" **Expected Behavior**: - Skill activates on "trusted folders" - Delegates to gemini-cli-docs for security settings **Success Criteria**: User receives security.folderTrust configuration ### Scenario 3: Configuration Debugging **Query**: "My Gemini settings aren't applying, how do I debug?" **Expected Behavior**: - Skill activates on "settings not applying" - Checks trust status recommendation **Success Criteria**: User receives troubleshooting steps including /permissions check ## References **Official Documentation:** Query `gemini-cli-docs` for: - "configuration" - "trusted folders" - "policy engine" ## 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.