antigravity-skills-reference/docs/maintainers/repo-growth-seo.md

Repo Growth SEO Playbook

This document keeps the repository's GitHub-facing discovery copy aligned with the SEO-focused user docs.

Current position

Preferred positioning:

Installable GitHub library of 1,273+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.

Key framing:

• installable skill library;
• GitHub-first discovery;
• broad multi-tool compatibility;
• bundles, workflows, and onboarding docs;
• useful for both breadth and curated evaluation.

GitHub About settings

Preferred description:

Installable GitHub library of 1,273+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.

Preferred homepage:

https://github.com/sickn33/antigravity-awesome-skills

Preferred topics:

• agentic-skills
• agent-skills
• ai-agents
• ai-agent-skills
• awesome-list
• awesome-lists
• antigravity
• antigravity-skills
• autonomous-coding
• claude-code
• claude-code-skills
• codex-cli
• codex-skills
• cursor-skills
• developer-tools
• gemini-cli
• gemini-skills
• mcp
• ai-workflows
• skill-library

Release notes checklist

When publishing a release:

• include a title that names the main user-facing use case, not only the internal codename;
• mention newly supported tools, new bundles, and onboarding improvements early;
• link back to the most relevant docs in docs/users/;
• keep the first paragraph useful to someone who found the release page from Google.

Suggested opening structure:

1. one-sentence release summary with tool/use-case language;
2. top changes that matter to new and returning users;
3. links to install, bundles, workflows, and relevant comparison pages if needed.

Discussions checklist

Suggested pinned discussion topics:

• Start here: best skills by tool
• Best bundles for new users
• How to choose between Antigravity and other skill libraries

Discussion posts should:

• link to the tool-specific docs in docs/users/;
• answer one search intent cleanly;
• end with a single clear next step such as install, star, or compare.

Content maintenance rules

• Keep README, GitHub About description, and tool-specific user docs semantically aligned.
• Avoid cannibalization by giving each user doc a distinct primary intent.
• Prefer honest comparisons over absolute claims.
• Do not use SEM or paid language in discovery docs unless strategy changes later.