agentleFS
1stANUNNAKI1stANUNNAKI/majlis/skills/google-antigravity-sdk/SKILL.md

google-antigravity-sdk

Skill2 starsChanged 3 months agoMITView on GitHub

Design, implement, and debug autonomous AI agents and multi-agent systems using the Google Antigravity (AGY) SDK. ACTIVATE this skill when the user wants to create, configure, or orchestrate Google Antigravity agents.

  • Reads credentials

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

27 rules. About 0 are common, 4 are distinctive, and 23 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 23

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before proceeding with any Google Antigravity tasks, ensure the environment is ready:

    line 15
  2. Distinctive:

    Verify Applicability: If operating in an existing codebase, verify that using this Python SDK is possible and appropriate for the project.

    line 18
  3. Very specific:

    Check Dependencies: Check if google-antigravity is listed in the project's dependencies (e.g., requirements.txt, pyproject.toml).

    line 20
  4. Very specific:

    Install Package: Ensure the google-antigravity Python package is installed.

    line 22
  5. Very specific:

    Authentication Setup: Check for a valid GEMINI_API_KEY environment variable or a .env file (required to access Gemini models).

    line 24
  6. Distinctive:

    If credentials are missing, you MUST actively help the user get set up with an API key by providing the following link:

    line 26
  7. Very specific:

    Default to Google AI Studio: https://aistudio.google.com/app/api-keys

    line 28
  8. Distinctive:

    Use the following information to dig deeper into specific topics based on the user request.

    line 36
  9. Very specific:

    If the user needs to understand the high-level overview and core concepts of the Google Antigravity SDK (Agent, Conversation, Connection), …

    line 42
  10. Very specific:

    If the user needs to perform advanced agent configuration, select appropriate models, or understand the critical rules for model …

    line 45
  11. Very specific:

    If the user needs to extend an agent's capabilities by integrating Model Context Protocol (MCP) servers, or configure tool permissions for …

    line 48
  12. Very specific:

    If the user needs to define safety policies, resolve execution order, or restrict agent actions using predicates, read …

    line 51
  13. Very specific:

    If the user needs to debug failed agents, stream logs, or implement error recovery using hooks to make agents robust, read …

    line 54
  14. Very specific:

    If the user needs to monitor costs, track token usage (including thinking tokens), or build custom audit logs for advanced monitoring, read …

    line 57
  15. Very specific:

    If the user needs to see a list of built-in tools and understand their default state, read references/built_in_tools.md.

    line 60
  16. Very specific:

    If the user needs to implement basic agent behavior, streaming responses, or expose internal thoughts, read …

    line 64
  17. Very specific:

    If the user needs to equip an agent with custom capabilities (tools) derived from Python functions, or maintain agent state across tool …

    line 66
  18. Very specific:

    If the user needs to shape an agent's persona, define its system instructions, or dynamically adapt its behavior, read …

    line 69
  19. Very specific:

    If the user needs to build multimodal agents capable of processing images and PDFs, or generating visual content, read …

    line 72
  20. Very specific:

    If the user needs to implement multi-agent delegation, allowing a main agent to spawn and orchestrate subagents for complex tasks, read …

    line 75
  21. Very specific:

    If the user needs to connect an agent to external services via MCP (Stdio or SSE), read examples/getting_started/mcp_tools.md.

    line 78
  22. Very specific:

    If the user needs to create proactive agents that respond to time-based events or file system triggers in the background, read …

    line 80
  23. Very specific:

    If the user needs to intercept agent lifecycle events (e.g., pre/post turn, tool execution, errors) to customize execution flow, read …

    line 83
  24. Very specific:

    If the user needs to implement persistent agents that remember past interactions across sessions, read …

    line 86
  25. Very specific:

    If the user needs to override the default application data directory for agent artifacts, scratch files, and media storage, read …

    line 89
  26. Very specific:

    If the user needs an agent to output structured data (e.g., JSON matching a Pydantic schema) for reliable integration, read …

    line 92
  27. Very specific:

    If the user needs to add, configure, or load agent skills into the Google Antigravity SDK agent, read …

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Antigravity SDK

Installation & Setup

Before proceeding with any Google Antigravity tasks, ensure the environment is ready:

  • Verify Applicability: If operating in an existing codebase, verify that using this Python SDK is possible and appropriate for the project.
  • Check Dependencies: Check if google-antigravity is listed in the project's dependencies (e.g., requirements.txt, pyproject.toml).
  • Install Package: Ensure the google-antigravity Python package is installed.
  • Authentication Setup: Check for a valid GEMINI_API_KEY environment variable or a .env file (required to access Gemini models).
    • If credentials are missing, you MUST actively help the user get set up with an API key by providing the following link:
      • Default to Google AI Studio: https://aistudio.google.com/app/api-keys
    • Explain that the API key can be passed explicitly in code as shorthand (e.g., LocalAgentConfig(api_key="...")) or automatically read from the environment.

Routing Table

Use the following information to dig deeper into specific topics based on the user request. Read the referenced files or explore the directories to find relevant information.

References

  • If the user needs to understand the high-level overview and core concepts of the Google Antigravity SDK (Agent, Conversation, Connection), read references/architecture.md.
  • If the user needs to perform advanced agent configuration, select appropriate models, or understand the critical rules for model identifiers to avoid assumptions, read references/agent_configuration.md.
  • If the user needs to extend an agent's capabilities by integrating Model Context Protocol (MCP) servers, or configure tool permissions for the agent, read references/mcp_integration.md.
  • If the user needs to define safety policies, resolve execution order, or restrict agent actions using predicates, read references/safety_policies.md.
  • If the user needs to debug failed agents, stream logs, or implement error recovery using hooks to make agents robust, read references/error_handling.md.
  • If the user needs to monitor costs, track token usage (including thinking tokens), or build custom audit logs for advanced monitoring, read references/observability.md.
  • If the user needs to see a list of built-in tools and understand their default state, read references/built_in_tools.md.

Examples

  • If the user needs to implement basic agent behavior, streaming responses, or expose internal thoughts, read examples/getting_started/hello_world.md.
  • If the user needs to equip an agent with custom capabilities (tools) derived from Python functions, or maintain agent state across tool execution, read examples/getting_started/custom_tool.md.
  • If the user needs to shape an agent's persona, define its system instructions, or dynamically adapt its behavior, read examples/getting_started/persona_config.md.
  • If the user needs to build multimodal agents capable of processing images and PDFs, or generating visual content, read examples/getting_started/multimodal.md.
  • If the user needs to implement multi-agent delegation, allowing a main agent to spawn and orchestrate subagents for complex tasks, read examples/getting_started/subagents.md.
  • If the user needs to connect an agent to external services via MCP (Stdio or SSE), read examples/getting_started/mcp_tools.md.
  • If the user needs to create proactive agents that respond to time-based events or file system triggers in the background, read examples/getting_started/periodic_trigger.md.
  • If the user needs to intercept agent lifecycle events (e.g., pre/post turn, tool execution, errors) to customize execution flow, read examples/getting_started/hooks.md.
  • If the user needs to implement persistent agents that remember past interactions across sessions, read examples/getting_started/persistence.md.
  • If the user needs to override the default application data directory for agent artifacts, scratch files, and media storage, read examples/getting_started/app_data_dir_override.md.
  • If the user needs an agent to output structured data (e.g., JSON matching a Pydantic schema) for reliable integration, read examples/getting_started/structured_output.md.
  • If the user needs to add, configure, or load agent skills into the Google Antigravity SDK agent, read examples/getting_started/agent_skills.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.