
Professional Agentic Architect Certification
Skills.google >>> dropped yesterday...

Skills.google >>> dropped yesterday...
>This is taken from the following tweet: https://x.com/googleaidevs/status/2085468449145544780
We’ve put together this cheat sheet of essential slash commands to help you navigate, customize, and execute tasks faster than ever in Google @Antigravity. Whether you're setting up background tasks, tweaking your workspace utilities, or diving into deep research with subagents, these commands will help improve your daily workflow.
🔖 Bookmark this list to save time later.
Get started with Antigravity: https://antigravity.google/
From one of our Mods the one and only u/soundDR
Description from the video:
In this walkthrough, we use Antigravity 2.0 to build two complete custom automations across the Chrome and local OS.
Prompt: Act as an expert Chrome Extension developer and build a Manifest V3 extension that automatically organizes unpinned tabs into native Tab Groups based on their last-accessed time. The time buckets must be exactly: Today, Yesterday, This Week, Last Week, This Month, Last 90 Days, and Archived, calculated strictly using the user's local timezone. When a tab becomes active, its timestamp should update via TTL logic and it should immediately move to the 'Today' bucket. This organization logic must be isolated per window (no cross-window tab moving) and must maintain a stable, fixed left-to-right visual sorting of the tab groups. Persist all tab timestamps using 'chrome.storage.local' to survive browser restarts and Service Worker suspension. Ensure you ignore pinned tabs entirely, and heavily debounce the 'chrome.tabs.onActivated' and 'onUpdated' listeners to prevent Ul flickering and Chrome API rate limits. Please output the complete 'manifest.json' and the 'background.js' service worker code.
Subscribe to Google Antigravity → / @googleantigravity
Google Antigravity is an agentic development platform, evolving the IDE into the agent-first era. Antigravity enables developers to operate at a higher, task-oriented level by managing agents across workspaces, while retaining a familiar AI IDE experience at its core. Agents operate across the editor, terminal, and browser, enabling them to autonomously plan and execute complex, end-to-end tasks elevating all aspects of software development.
To learn more: Website: https://antigravity.go... X: https://x.com/antigravity LinkedIn: / google-antigravity
Trying to figure out which workflow is lighter on background usage between the two Antigravity setups:
For those who have tested both for similar coding tasks:
All the web on one topic in the last 30 days
https://www.youtube.com/live/LcnBRo11mnk?si=Debq54kB2GbPJ-9C
Feedback? Question? Googlers are listening
u/SoundDr Thank you for everything you do for the AGY Community. We really appreciate all your hard work! Please keep up the Googler awesomeness!!!!
Hi! I saw an article about how claude code was configured to meow when it finishes working or asks for permission. This allows you to not constantly check what it is doing, because you will hear meow when you are needed. I decided to do something similar for antigravity cli, so that it sends a desktop notification and makes a sound. I managed to do this when it finishes its work using the Stop hook, but I could not when it asks for my permission. There is a PreToolUse hook, but it does not provide any information about whether agy will ask me for permission for this tool. I can write a script with hardcoded list of tools which are currently autoallowed, but I want solution that works even if I change agy permissions.
Does anyone know a way to make it send a notification only when it asks for permission to execute the tool?
We'll Hassabing our Antigravity CLI community for Open Source & Open Models support all days, everyday... Don't be evil !!!!!! r/GoogleAntigravityCLI
As a 3-year Google AI Pro annual plan subscriber, I feel disappointed with Google for failing to provide the relatively powerful AI that was available when I first subscribed. However, since there are ways the Agy team can overcome this with their skill, I am making these proposals.
This isn't just complaining; it is something worth seriously considering.
Here are some basic facts:
And Google has the Gemini 3.5 Flash-Lite model, which has capabilities similar to the two models listed above. Take a look below.
Regardless of benchmarks, Google's unbeatable wall lies in its multimodal capabilities. Even if tied in benchmarks, no model can surpass Gemini in actual use unless it is fine-tuned. Among publicly serviced AI models, Gemini is like a god in multimodal capability.
Now, here are the proposals:
Of course, you shouldn't just paste this into the system prompt, and you'll need to think about it further. But the concept is this:
When given clear instructions, smaller models perform tasks extremely well—not quite as perfectly as high-performance models, but enough to satisfy users.
Also, I don't know how strictly Agy-Cli limits the max output tokens of models or how small the limit for document generation is set, but its document generation capability is at a pathetic level. Ease this restriction by about 5 times.
and store text communications between agents locally on the individual computer where Agy is installed.
If 3.6 Flash or 3.1 Pro create a Todo list and actively utilize 3.5 Flash-Lite as parallel sub-agents, you can produce better results at a lower cost. If someone is an x20 user, it might be nice to add an option to use the 3.6 Flash model as a sub-agent, but I guarantee that for most users, 3.5 Flash-Lite conducting large-scale research will be more than enough. While it's fine for Flash or Pro alone to research from backend to frontend and do reasoning, it's expensive. It's more efficient to variously utilize cheaper sub-agents and apply the high intelligence of Pro or Flash to subsequent tasks.
For reference, I completely avoided using 3.1 Flash-Lite on the web because its result quality was too poor. But now, I use 3.5 Flash-Lite quite a bit because it's fast and suitable for simple tasks—I was doing it without even realizing it. That's why I looked up benchmark results again. Originally, I was only interested in 3.6 Flash to find a more powerful model and never even thought about 3.5 Flash-Lite, but I realized that what matters in this update isn't 3.6 Flash.
Frankly speaking, Google does not have a single impressive AI model at this point. However, 3.5 Flash-Lite is the most impressive model among them, and if Agy actively utilizes this model, it will dramatically improve work completion quality.
The team developing the AI models failed, but the Agy team can make up for it.
-------
Supplementary explanation for this Text.
To help you understand the text, I am adding 4 screenshots.
example 1
example 2
Having a feature available and having it run automatically are different things. For example, what makes Opus excel is running several geniuses of its own caliber in parallel to gather vast amounts of information, which is why it is expensive.
From the perspective of Agy's developers, they might think, "Why don't you just type in the prompt yourself?" but from a user's perspective, it's not like that.
In the case of a simple prompt, a single Gemini can do the searching, analysis, modification, and even testing all by itself, but it is expensive.
In the case of the 'Prompt to utilize sub-agents', there is a cost to creating sub-agents, but by using 3.5 Flash-Lite—which costs 1/6 of Flash—to find and organize the directory structure, source code files, and framework stack, you can have it investigate more than Flash alone could, at a very high speed and low cost. Following a plan made by an expensive model, the costly coding process can also be investigated via the inexpensive 3.5 Flash-Lite, while 3.6 Flash can directly review it or just create test files. Then, 3.5 Flash-Lite can execute the test files and organize the results.
As we all know, this is no longer an era where we make a single model do all the work. It is an era where the main model controls other AIs, while sub-agents utilize skills (pre-written prompts) to bring about better results.
And one of Gemini's major strengths compared to other models is its blazing-fast token generation capability. Whenever needed, it is easy to create a persona for a sub-agent and spawn an inexpensive sub-agent with that persona.
If you look up reviews on Gemini 3.6 Flash, you'll see. Were the reviews good? Most of it is mockery. That is the market's assessment.
With an inexpensive yet excellent model like 3.5 Flash-Lite, actively utilizing it will save the main AI's context while producing better results at a lower cost.
You shouldn't think, "What can't Agy and Gemini build right now that makes them ask for this?"
This is a post about how to build better results at a lower cost.
And these are also things that the Agy team can fix without putting in major efforts like LLM training.
I wanted to tell you guys about a very different use case I have for the anti-gravity CLI today
So I was hired to install the Wi-Fi in an Airbnb. Pretty simple setup but it is included taking their existing router, turning it into bridge mode, and then running everything through another router, a POE plus gigabit switch and then out to two wireless access points.
It's been a while since I've done any actual technical stuff like that so I was pretty rusty.
So what I did was I grabbed an old laptop of mine, installed Linux Mint, and installed the antique gravity CLI.
I made a project folder of documents that I had typed up before, like hardware we were using, the direction the cables were going to have to be buried in, where it was, why it was going to be used and stuff like that
Running it from that folder, I told it what we were doing and I had it download all of the quick start guides, all the documentation for the hardware, headed organize the plan a little bit better and then I had it download every network CLI tool it thought would be useful. Like wireshark CLI and a couple other packet sniffing tools and management tools.
It was basically my man on the inside configuring the network from within.
I'm not done with it yet but it has been really really really helpful. It's recommendations for how to configure the router for long-term support, for example, we're pretty interesting. And I was only using 3.5 flash high.
When I started getting the router and the switch plugged in and everything hooked up it was even able to figure out that one of the pins on one of the network cables was not working.
It was just so fascinating to see how it coalesced all of the usage from the documentation with the official guides from the hardware and combined with all of the CLI tools it was using.
Very cool, highly recommended
I’m a corporate user of Claude Code and Cursor.
Yesterday I was developing my side project with agy cli and I’m impressed. I was adding feature to the app and usually switched to YouTube to watch something while AI tool do something. I saw in a 30 sec that my feature was added and I was very skeptical.
I’ve opened the app and I saw it’s working like I described, shocked. It was adding packages, rewriting UI, adding backend, pushing cloud build to server and ofc run some linting and test.
It was so fast that blew my mind, Claude code in my work is used with google vertex and it’s so slow that I can literally go take a shower and come back to not finished task.
Btw. I’m using 3.1 pro with high effort.
Thank you google, agy cli is getting really better, I should say competitive to Claude code.
Opinions on Google Open Knowledge Format in markdown? Is someone using it?
AGY Builders,
We are all trying to build useful and scalable workflows for our AGY CLI and ecosystem, but the speed at which we need to learn, build, and deploy new things is incredibly overwhelming. If you are feeling that pressure, you are in the right place here at r/GoogleAntigravityCLI.
Over the past few weeks, I have been testing an "AGY WIKI OKF" setup that I put together myself (after inviting some members of this community to collaborate; mod is not proud). I know some folks might hesitate to trust a tutorial from a random Redditor, but I wanted to share this with the community anyway because it actually works.
I was able to build this because I am all-in on Google and the Antigravity Ecosystem. I’m a truly AGY—I am not some ultra-smart, 10x developer, but I know how to work hard, I dig for the right information, and I iterate.
To build a frictionless, token-efficient knowledge WIKI engine that transforms static documentation or notes (information) into an active, intelligent collaborator—orchestrated entirely by Antigravity CLI.
The core philosophy is simple: treat knowledge management as a clean pipeline and tokens as a premium, finite resource.
By anchoring this architecture to Google’s Antigravity CLI, the AGY WIKI OKF bypasses heavy middleware and complex UI layers, delivering a hyper-focused AI partner built entirely for execution speed, context hygiene, and minimal footprint.
In the agent-first era, a WIKI is no longer just a static graveyard for human notes; it is the operational hard drive for your agents. By maintaining a highly structured WIKI, you ensure that every piece of context is stored in a clean, machine-readable format. This means that whether you are testing a new modular skill or spinning up a specialized agent, your AGY CLI knows exactly where to find the precise context it needs to generate autonomous action, moving you far beyond simple, reactive conversational text.
Reference: Gist on Knowledge Representation
Google’s Open Knowledge Format (OKF) feels like the exact missing piece we've needed for orchestrating multiple AI agents effectively. It provides a vendor-neutral, interoperable standard for storing and sharing organizational knowledge.
Structuring an AGY Wiki using OKF revolutionizes how complex knowledge is shared. By standardizing documentation with concise Markdown and YAML frontmatter, OKF provides a unified taxonomy for cataloging AGY CLI slash commands or skills It is highly token-efficient, stripping away bloated formatting and maximizing context window limits.
AGY CLI WIKI OKF PROMT EXAMPLE
/grillme I want to initialize a brand-new, empty Obsidian vault from scratch that adheres strictly to the Open Knowledge Format (OKF) standard, with the specific intent of potentially open-sourcing or sharing this architecture later. I want a purely blank, skeletal framework with no pre-populated data. Please grill me to define the optimal architectural blueprint for this vault. I need you to interrogate me on: Do not generate the directory structure or files until you are satisfied that you have captured all my requirements for a production-ready, shareable knowledge base.
Core Directory Hierarchy: How should we structure the root (e.g., /concepts, /resources, /indices, /log) to be intuitive for external users? Template Strategy: What base boilerplate templates do we need to ensure every new file is automatically OKF-compliant and structured for consistent metadata? Workflow Logic: Since this is a fresh start, what processes should we bake in for capturing information vs. refining knowledge that could be easily documented for others? CLI Integration: What specific file locations or configurations do we need to ensure this vault plays nicely with the Antigravity CLI from day one? Open-Source & Contributor Documentation: What files should we create to make this a "deployable" standard? Please include requirements for: A README.md with installation and usage instructions. A CONTRIBUTING.md that defines how to add new concepts or schemas. A "System Architecture" document that explains the logic behind the folder structure and metadata fields, ensuring anyone who clones this vault understands how to extend it.
AGY WIKI OKF
├── .agyrc
├── ARCHITECTURE.md
├── CONTRIBUTING.md
├── README.md
├── .agy
│ └── .keep
├── .obsidian
│ ├── app.json
│ ├── appearance.json
│ ├── core-plugins.json
│ └── workspace.json
├── 00-Inbox
│ └── .keep
├── 10-Projects
│ └── .keep
├── 20-Areas
│ └── .keep
├── 30-Resources
│ ├── .keep
│ └── Google Antigravity Documentation.md
├── 40-Archive
│ └── .keep
├── 99-Meta
│ └── Templates
│ ├── Base_Template.md
│ ├── Project_Template.md
│ └── Resource_Template.md
└── Clippings
AGY Builders, I genuinely want your input on this. Please comment, grill me, roast me, ask questions, or give me your raw feedback on this AGY WIKI OKF setup. We are building the foundation to organize and share our data in the BYOD era. Let's build the future together.
AGY Builders: Here is another great example of how amazing it is to build projects with Antigravity CLI.
Google has officially discontinued the Gemini CLI, replacing it with a new command-line interface tool called Antigravity CLI (or agy). The creator behind the Creator Magic channel provides a firsthand look at this transition, exploring its features, pitfalls, and integration into modern development workflows.
agy tool, which is installed via a simple terminal command.agy isn't restricted to just Google's models. It provides access to various models, including Gemini 3.5 Flash, Claude Opus, and GPT-4o, making it a potentially versatile utility.The creator experiments with building a functional "Epic Snake" game using Antigravity CLI and discusses the "endgame" vision: a system where AI agents work in loops, handing off tasks to one another, switching providers to manage token usage, and ultimately self-improving code without needing constant human intervention.
While the multi-model access is a power move, the consensus from the stream is to approach the free tier with caution due to the aggressive rate limits, especially for those looking to build complex projects.
Watch the full deep dive here: https://www.youtube.com/live/kjFi1IuzWY4
What are you building today?
Update: Forgot to mention that to be fair and support `opencode` I plan to upgrade to their $10 /month plan.
I have successfully setup a combo of Antigravity + Opencode + Local LLM but I still believe there is a room for improvement. Please share if possible:
Details are below:
Most recent task:
Here is a summary of the token usage and division of labor:
1. Division of Labor
* Antigravity (Cloud - Google AI Pro): Acted as the Manager. Architected the solutions, researched repository structures, generated the revised implementation/verification plans, and wrote detailed orchestration instructions.
* OpenCode (Local Agent): Acted as the Implementer. Executed the multi-file coding task to modify flow.js and flow_panel.html under explicit manager guidelines.
* Local LLM (ask_local - Qwen 32k on RTX 3090): Acted as the Inspector. Used for git commit analysis, file content analysis, and log reviews, keeping mechanical token queries off the cloud.
2. Approximate Token Breakdown
* Antigravity (Cloud): ~18,000 input / ~2,500 output tokens (high-level reasoning & planning).
* OpenCode (Local): ~15,000 local tokens (code modifications and git staging).
* Local LLM (Local): ~12,000 local tokens (inspecting codebases, git history, and summaries).
By routing code analysis and implementation to ask_local and ask_opencode, nearly 60% of the total token volume was processed locally on your RTX 3090 instead of consuming cloud qu*tas (`f**k mods for blanket filtering this word`).
Monitor running in WSL: