README currently states: "Antigravity and Mistral Vibe targets were removed — unused." Antigravity (Google's IDE, ~/.gemini/) is back in active use and currently has zero skills wired.
Findings from investigating this on flamingo (2026-08-30):
Antigravity discovers skills via ~/.gemini/config/skills.json — a path-entries JSON ({"entries":[{"path":"..."}]}), NOT a symlink farm. One entry can point at the whole checkout dir; Antigravity itself walks it for <name>/SKILL.md. Simpler than the Crush/OpenCode symlink pattern already in install.sh.
Schema and discovery rules are documented inside the app itself: ~/.gemini/<active-install>/builtin/skills/agy-customizations/docs/ (skills.md, json_configs.md, etc). Worth reading directly rather than re-guessing — three near-identical ~/.gemini/{antigravity,antigravity-ide,antigravity-backup}/ dirs exist per host and only the most-recently-modified one is live.
Would need a new ANTIGRAVITY_SKILLS_JSON env-var override (default $HOME/.gemini/config/skills.json) alongside the existing AGENTS_SKILLS_DIR/CRUSH_SKILLS_DIR/OPENCODE_SKILLS_DIR, and a wire_antigravity function that merges (idempotently, via jq) a {path: $SKILLS_CHECKOUT_DIR} entry into .entries, preserving any other entries already there.
Not implemented yet — this repo wasn't touched as part of the Antigravity MCP-wiring work on local-dev (v0.7.0); that work only covers MCP server config, not skills. Filing so the skills-repo maintainer (future me) decides scope/timing rather than it rotting as a comment in an unrelated repo's commit.
README currently states: "Antigravity and Mistral Vibe targets were removed — unused." Antigravity (Google's IDE, `~/.gemini/`) is back in active use and currently has zero skills wired.
Findings from investigating this on flamingo (2026-08-30):
- Antigravity discovers skills via `~/.gemini/config/skills.json` — a path-entries JSON (`{"entries":[{"path":"..."}]}`), NOT a symlink farm. One entry can point at the whole checkout dir; Antigravity itself walks it for `<name>/SKILL.md`. Simpler than the Crush/OpenCode symlink pattern already in install.sh.
- Schema and discovery rules are documented inside the app itself: `~/.gemini/<active-install>/builtin/skills/agy-customizations/docs/` (skills.md, json_configs.md, etc). Worth reading directly rather than re-guessing — three near-identical `~/.gemini/{antigravity,antigravity-ide,antigravity-backup}/` dirs exist per host and only the most-recently-modified one is live.
- Would need a new `ANTIGRAVITY_SKILLS_JSON` env-var override (default `$HOME/.gemini/config/skills.json`) alongside the existing `AGENTS_SKILLS_DIR`/`CRUSH_SKILLS_DIR`/`OPENCODE_SKILLS_DIR`, and a `wire_antigravity` function that merges (idempotently, via jq) a `{path: $SKILLS_CHECKOUT_DIR}` entry into `.entries`, preserving any other entries already there.
- Not implemented yet — this repo wasn't touched as part of the Antigravity MCP-wiring work on local-dev (v0.7.0); that work only covers MCP server config, not skills. Filing so the skills-repo maintainer (future me) decides scope/timing rather than it rotting as a comment in an unrelated repo's commit.
Shipped in e9ad692 / v0.9.0. wire_antigravity() registers $AGENTS_DIR (not the raw checkout) into ~/.gemini/config/skills.json via a jq-gated, existing-entries-preserving merge — same surfaces-filtered set every other harness gets. Tests: 3 new cases in tests/install_test.sh (registers managed dir, idempotent, preserves hand-authored entries), full suite green (12/12 install, no regressions elsewhere).
Shipped in e9ad692 / v0.9.0. `wire_antigravity()` registers `$AGENTS_DIR` (not the raw checkout) into `~/.gemini/config/skills.json` via a jq-gated, existing-entries-preserving merge — same surfaces-filtered set every other harness gets. Tests: 3 new cases in tests/install_test.sh (registers managed dir, idempotent, preserves hand-authored entries), full suite green (12/12 install, no regressions elsewhere).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
README currently states: "Antigravity and Mistral Vibe targets were removed — unused." Antigravity (Google's IDE,
~/.gemini/) is back in active use and currently has zero skills wired.Findings from investigating this on flamingo (2026-08-30):
~/.gemini/config/skills.json— a path-entries JSON ({"entries":[{"path":"..."}]}), NOT a symlink farm. One entry can point at the whole checkout dir; Antigravity itself walks it for<name>/SKILL.md. Simpler than the Crush/OpenCode symlink pattern already in install.sh.~/.gemini/<active-install>/builtin/skills/agy-customizations/docs/(skills.md, json_configs.md, etc). Worth reading directly rather than re-guessing — three near-identical~/.gemini/{antigravity,antigravity-ide,antigravity-backup}/dirs exist per host and only the most-recently-modified one is live.ANTIGRAVITY_SKILLS_JSONenv-var override (default$HOME/.gemini/config/skills.json) alongside the existingAGENTS_SKILLS_DIR/CRUSH_SKILLS_DIR/OPENCODE_SKILLS_DIR, and awire_antigravityfunction that merges (idempotently, via jq) a{path: $SKILLS_CHECKOUT_DIR}entry into.entries, preserving any other entries already there.Shipped in
e9ad692/ v0.9.0.wire_antigravity()registers$AGENTS_DIR(not the raw checkout) into~/.gemini/config/skills.jsonvia a jq-gated, existing-entries-preserving merge — same surfaces-filtered set every other harness gets. Tests: 3 new cases in tests/install_test.sh (registers managed dir, idempotent, preserves hand-authored entries), full suite green (12/12 install, no regressions elsewhere).