settingslisted
Install: claude install-skill stxrmik/antigravity-plus
# /settings — what is set where
Helper: `python3 "<skill_dir>/scripts/settings.py"`. It reads and writes `~/.gemini/`, which is outside the
workspace, so run it with `BypassSandbox: true`.
1. **Look first:** `settings.py show --workspace "<ws>"`. Never guess where a setting lives.
2. **Change what the user asked for** in their own words. Say what you changed in one line.
| The user wants | Do |
|---|---|
| to connect an MCP server (a local program) | `settings.py mcp add <name> --command <cmd> [--env KEY] -- <args…>`, e.g. `mcp add github --command npx --env GITHUB_TOKEN -- -y @modelcontextprotocol/server-github` |
| to connect a remote MCP server | `settings.py mcp add <name> --url https://…/mcp` (Streamable HTTP; for an old `/sse` server, wrap it with `npx mcp-remote <url>` as a command) |
| to remove a server / see the list | `settings.py mcp remove <name>` / `settings.py mcp list` |
| plugin behavior: reminders, auto-review, auto-memory, secret protection, setting up projects on its own | `settings.py plugin <key> on\|off` (keys are listed by `show`) |
| a rule for this repository | `/remember` (goes to `AGENTS.md`) |
| something to run automatically (format, tests before finishing) | `/hooks` |
| Antigravity's permission preset, terminal sandbox, auto-run, access to files outside the project, model | the user does this in Antigravity Settings: tell them exactly where. These decide what you may do, so you never change them yourself |
- **Secrets:** pass keys as `--env