richfrem/antigravity-project-setup
plugins/gemini-cli/skills/antigravity-project-setup/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills antigravity-project-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 7:32 AM58.8s4 files scanned
SKILL.md
- name:
- antigravity-project-setup
- plugin:
- gemini-cli
- description:
- >-
- allowed-tools:
- Bash, Read, Write
Google ADK & Antigravity Project Setup
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.
Phase 1: Discovery Interview
Ask the user the following questions. Collect all answers before proceeding. Do not scaffold anything yet.
- Context Persona: What identity and role should the agent assume in
.gemini/GEMINI.md? (e.g., Senior Security Engineer specializing in Rust, Senior Frontend dev). - Current structure: Does
.agents/or.gemini/exist in this project yet? - Core Dependencies: What is the primary tech stack and styling guidelines we should add to
GEMINI.md? - Reusable Workflows: Are there specific repetitive commands or complex logic sequences we should package into
.agents/prompts/? - Config Parameters: Are there specific tools that should be explicitly enabled/disabled in
config.json? Should we pin the model togemini-2.5-pro(alias:pro),gemini-2.5-flash(alias:flash), or leave it atauto?
Phase 2: Plan Recap
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.
Phase 3: Scaffold
Context Files (.gemini/GEMINI.md / .agents/AGENTS.md)
- This is the Master Context.
- Modularize via
@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]
Prompts (.agents/prompts/)
- Reusable workflows triggered via CLI or IDE shortcuts. Keep them contained.
Skills (.agents/skills/)
- Ensure this directory physically exists. Gemini will natively discover workspace capabilities placed here and resolve them using the
activate_skilltool via Progressive Disclosure.
Config (.agents/config.json)
- Write the foundational
config.jsonobject. Set the model to whatever the user requested.
Phase 4: Verification
After writing files:
- Confirm the required files correctly exist within the universal cross-compatible
.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.
Related Skills
richfrem/issue-worktree-agent
testing
VerifiedTrustedCommunity
Skill for creating and managing isolated git worktrees (`.worktrees/issue-NNN`) for issue execution branches. USE ONLY when setting up or cleaning up isolated git worktrees for specific issue execution. DO NOT USE for managing local task files (use `task-agent`) or escalating tasks to issues (use `github-issue-backlog-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/issue-pr-lifecycle-agent
data-ai
VerifiedTrustedCommunity
Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-prioritizer
tools
VerifiedTrustedCommunity
Automatically ranks GitHub issues (P0-P3) based on friction tier, frequency, and blockages, synchronizing priority labels and GitHub Projects v2 custom fields.
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-backlog-agent
testing
VerifiedTrustedCommunity
Bridge skill for escalating ephemeral local task scratchpad items (`tasks/*.md`) into durable, taxonomy-validated, evidence-rich GitHub Issues. USE ONLY when promoting a single-session local task into durable repository backlog. DO NOT USE for managing local kanban boards (use `task-agent` instead) or directly querying/commenting on issues (use `github-issue-agent` instead).
4SKILL.mdUpdated Jul 29, 2026