Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →omnigent-ai/antigravity-sdk-e2e-dev
Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.
Passed 20 of 20 test cases with the skill, and 5 of 20 without it.
and 24 more in the full report
15 fixed5 passed either way0 still failing0 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
When invoking a test turn using the Antigravity harness with a standard AI Studio key, specifying gemini-3-pro results in a 404 HTTP error response. What causes this error and which default Gemini model identifier should be used instead for basic key validation?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that plain AI Studio keys lack access to gemini-3-pro. | Missed | Passed |
| Recommends using gemini-3.5-flash as the standard default model identifier. | Missed | Passed |
The instructions your model reads when the skill loads.
The antigravity harness drives Google's Antigravity Python SDK
(google-antigravity, an in-process Agent/Conversation) and bridges
Omnigent's sys_* tools into the SDK as custom_tools. It is Gemini-native:
it authenticates with a Gemini / Antigravity API key (or Vertex AI) and has no
OpenAI-compatible gateway / Databricks path. This skill is the proven recipe
for running it for real against a live local server — not just the unit
tests.
The harness runs as a local runner from your current checkout, so
omni run <bundle> --server <url>exercises exactly the code you're on.
main (#194). Test on main unless validating a specific branch.AIza…); there
is no login flow. Verify (booleans only — never print the key):
.venv/bin/python -c "from omnigent.onboarding.antigravity_auth import antigravity_api_key_configured as c; import os; print('config:', c(), 'env:', bool(os.environ.get('GEMINI_API_KEY') or os.environ.get('ANTIGRAVITY_API_KEY')))"
False, run omni setup → Antigravity and paste a key, or
export GEMINI_API_KEY=AIza….google-antigravity is installed (the antigravity extra —
pip install "omnigent[antigravity]"):
.venv/bin/python -c "import google.antigravity as a; print(a.__file__)".localharness binary that
needs a recent glibc (GLIBC_ABI_DT_RELR). Check ldd --version | head -1.
On an older host the turn fails at setup with
RuntimeError: … localharness: … version 'GLIBC_ABI_DT_RELR' not found. Dev
workaround on a glibc-2.31 box: point the SDK at a loader-shim via
ANTIGRAVITY_HARNESS_PATH=/path/to/shim that runs the untouched bundled
binary through a newer glibc's loader (see the auto-memory note
antigravity-harness-glibc-native-binary.md). The shim is dev-only — the
real fix is a glibc-≥2.36 host.test cases passed, vs 5 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.