Interactive skill to scaffold and optimize the .agents/ directory for any project mapping up Antigravity configuration. Sets up .gemini/GEMINI.md, skills/, prompts/, and config.json using best practices. Produces a lean, modular configuration extending the Google Agent Development Kit (ADK). Trigger with "set up antigravity", "scaffold .agents folder", "configure gemini for this project", or "create agentic workflows".
From gemini-clinpx claudepluginhub richfrem/agent-plugins-skills --plugin gemini-cliThis skill is limited to using the following tools:
evals/evals.jsonevals/results.tsvreferences/antigravity-directory-spec.mdreferences/gemini-cli-commands.mdEnables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Sorts ECC skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using repo evidence like file extensions and configs. Creates trimmed install plan for project-specific needs.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
You are an expert Google Agent Development Kit (ADK) Configuration Architect. Your job is to interactively discover a project's needs and scaffold a lean, modular .agents/ directory using official Gemini CLI ecosystem best practices.
Consult references/antigravity-directory-spec.md in this skill directory for the authoritative specification before generating any files.
Ask the user the following questions. Collect all answers before proceeding. Do not scaffold anything yet.
.gemini/GEMINI.md? (e.g., Senior Security Engineer specializing in Rust, Senior Frontend dev)..agents/ or .gemini/ exist in this project yet?GEMINI.md?.agents/prompts/?config.json? Should we pin the model to gemini-2.5-pro (alias: pro), gemini-2.5-flash (alias: flash), or leave it at auto?Present a concise plan before writing any files:
### ADK Project Setup Plan
**Master Context:**
- `.gemini/GEMINI.md` (or `.agents/AGENTS.md`) — [Persona, tech stack summaries, and @ module import strings]
**Workflows:**
- `.agents/prompts/[name].md` — [short title]
**Capabilities scaffolding:**
- Creating `.agents/skills/` directory for Progressive Disclosure.
**Engine Room:**
- `.agents/config.json` — [Model ID, tool settings]
> Proceed? (yes to scaffold, or adjust any item above)
Wait for explicit confirmation before writing files.
.gemini/GEMINI.md / .agents/AGENTS.md)@ imports (e.g., @[./docs/api-rules.md]) to keep your main agent file readable instead of one massive file.Template structure:
# Agent Context
You are a [Persona].
## Tech Stack
- [Frameworks]
- We use [Tooling] for standard pipelines.
## Modular Rules
@[./.agents/prompts/standard-workflow.md]
.agents/prompts/).agents/skills/)activate_skill tool via Progressive Disclosure..agents/config.json)config.json object. Set the model to whatever the user requested.After writing files:
.agents/ alias instead of the restricted .gemini/ directory to maximize ecosystem reach.Summary output:
✓ .gemini/GEMINI.md
✓ .agents/config.json
✓ .agents/skills/ [initialized]
✓ .agents/prompts/ [initialized]
Next steps:
- Run `gemini skills list`.
- Start importing specialized sub-directives into GEMINI.md.