github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-pos
npx skills add kostja94/marketing-skills --skill github --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Platforms: GitHub Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Why GitHub for SEO | Factor | Effect | |--------|--------| | **Domain authority** | High DA; repos, gists, Pages rank well | | **Fast indexing** | Search engines crawl GitHub frequently | | **AI citation** | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework | | **Technical expertise** | Strong expertise signals; structured docs become AI reference material | | **Cross-platform** | Share across Dev.to, Stack Overflow, forums; amplifies visibility | ## Use Cases | Use case | Format | Purpose | |----------|--------|---------| | **Parasite SEO** | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks |
- Why GitHub for SEO
- Use Cases
- Surfaces: profile vs repository
- Profile README (username/username)
- Profile README checklist (short)
- Repository home: layout map
- In-site discovery (high level)
- Repository Name, About & README (SEO/GEO Priority)
- Repository Name
- About Section (Description)
- Topics
- README Structure & Components
- README GEO / AI Citation
- README Checklist — repository (default)
What does the github skill do?
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-pos
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill github --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.