Awesome Antigravity Skills

1What it does

A curated list scoped tighter than the ecosystem-wide indexes — this one tracks Antigravity skills specifically: community SKILL.md repositories, skill collections, authoring guides and the tooling that manages them. Where the master awesome-antigravity list maps every surface (rules, MCP, plugins, workflows, extensions), this list goes deeper on the skills corner alone — individual skill repos, multi-skill vaults, and writeups on how the format works. That narrowness is the feature: for someone deciding which skills to adopt, a focused index beats a broad one because every link is in scope. Entries link out to source repositories with one-line descriptions; it is discovery infrastructure, not an installable.

2When to use it

Reach for it when you're picking skills, not surveying the ecosystem — the question "what Antigravity skills exist for X?" is answered faster here than in a list that mixes in MCP servers and plugins. It suits the comparison-shopping phase: before installing a vault, scan here for single-skill repos covering your specific need; a tight single-purpose skill often beats enabling a 300-skill vault for one job. Skip it if you want installable content — everything here links out; and for the whole-ecosystem view (rules, MCP, plugins together) the master awesome list is the better map.

3How to get started

Read it top to bottom once — the list is short enough that a linear scan beats searching. For anything you plan to install, follow the link to the source repo and read its README and license there; the list summarizes, the source is the truth. The sections group by skill category, so a second pass for "what did I miss in my domain" is quick. If you maintain skills yourself, the linked authoring resources are the part most worth bookmarking — they are the format documentation trail.

4Configuration

Nothing to configure — it's a reading list. The practical use is as a periodic re-scan: the skills ecosystem is young and new repos land weekly, so a monthly re-read catches additions that weren't there when you first looked. If you fork it for a team index, the section taxonomy (collections → individual skills → authoring resources) transfers cleanly to an internal wiki.

5Things to know

• Scope discipline is the differentiator — staying skills-only keeps the list short enough to actually finish, which is the point of an awesome-list.
• Complements rather than competes with the big vaults — the vaults are install targets; this is the index that helps you choose among them.
• List quality tracks maintainer attention — check the last-commit date when evaluating freshness; awesome-lists stale quietly.
• CC0-licensed — forking into a team-internal skills index is explicitly free.
• Because it tracks single-skill repos as well as vaults, it is the place to find the small, sharp skills the big collections haven't absorbed yet — the niche ports and one-off packs surface here before they surface anywhere else.
• Evaluate a link the same way you'd evaluate a skill found anywhere: read the source repo's README, check the SKILL.md frontmatter quality, look at last-commit. The list gets you to the door; the repo earns the install.
• For skill authors, a listing here is a distribution channel — the repo's contribution path is the standard awesome-list PR flow, and getting listed is how a new skill finds its first users outside search.
• It ages alongside the format — as SKILL.md conventions settle, the list's older links stay useful because skills are just folders; staleness shows up as missing new repos, not broken old ones.
• Treat the ordering as curation signal, not ranking — the list groups by category rather than quality, and a bottom-of-list entry is not a lesser skill, just a later addition.

6Related on the map

References

• Repository
• Antigravity skills documentation