Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
A broad developer-tooling collection spanning RAG applications, multi-agent orchestration, Airflow pipelines, API and backend architecture, accessibility audits, and security analysis. It gives engineers concrete workflows for work such as incrementally migrating AngularJS, profiling agent systems, documenting architecture decisions, and testing realistic API behavior.
WHO IT'S FOR
AI / LLM engineers
building production-ready RAG systems and applications
AI agent / automation builders
optimizing multi-agent orchestration and performance
Data engineers
creating production Apache Airflow DAGs and pipelines
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: All skills in the 300+ skill Antigravity Skill Vault, installed into the current workspace; the listed skill paths are only a bounded selection relevant to the starter tasks · Google Antigravity
Before you start
Run from: The target Antigravity workspace directory
In a terminal, run this from the target workspace. This advanced option installs all skills and is not recommended for most projects because it increases token usage and may activate unrelated skills.
Required resources or existing interface constraints
Use the api-design-principles skill to draft a compact REST API contract for a user service. First ask me for the intended consumers, core use cases, authentication constraints, and required resources. Then propose the resources and endpoints, one representative request/response example, and concise decisions for errors, versioning, pagination, and authentication. Review the result for consistency; do not implement or publish it.
Use the async-python-patterns skill to review one I/O-bound Python workflow at `<path-to-python-file>`. Ask for the runtime constraints and desired concurrency limit, then recommend one small improvement using an appropriate asyncio pattern. Include cancellation behavior, timeout and backpressure handling, structured error handling, and a focused test or debugging check. Propose changes only; do not modify files.
Use the e2e-testing-patterns skill to plan one Playwright or Cypress test for a critical user journey in my application. Ask for the journey, success criteria, chosen framework, relevant page or test-file paths, and available safe test data. Draft the test structure with stable selectors, isolation, tracing, and artifact-capture guidance. Do not execute it, and do not target production or destructive workflows.
Claude
Cursor
Gemini CLI
Copilot
Hermes
Antigravity
DeepSeek