github

What this skill does

# 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 |
| **GEO** | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers |
| **Curated / navigation lists** | Awesome-style repos | Topic-specific resource directories; backlinks, discovery |

## Surfaces: profile vs repository

| Surface | What it is | Optimization focus |
|---------|------------|---------------------|
| **Profile README** | Public repo **with the same name as the username**; root `README.md` renders on the profile | Personal brand, flagship links, social proof |
| **Pinned** | Up to **6** repos or gists on the profile | Showcase top projects; align with entity signals (**entity-seo**) |
| **Per-repo README** | Root `README.md` on each repo’s **Code** tab | Product landing; install, proof, CTAs |

Changing a normal repo README does **not** change the profile banner unless that content is the **profile README** repo or linked from it.

### Profile README (`username/username`)

**Not the same as a product repo README.** Optimize for **identity + navigation** in ~15–40 lines of rendered content unless the user explicitly wants a long-form CV. Official setup: [Managing your profile README](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme).

| Principle | Do | Avoid |
|-----------|-----|--------|
| **Length** | Short, scannable sections; **omit ToC** unless the file is genuinely long | Applying “500–1,500 words typical for product repos” here |
| **Headings** | `###` blocks (e.g. *What I do · Open source · Find me*) for fast eyeballing | Many nested `##` + long narrative without breaks |
| **Links** | Each primary URL **once** in a **Find me / Connect** line (or badges **or** a slim table—not all three repeating the same destinations) | Duplicate site/LinkedIn/email in badges, tables, and prose |
| **Repos block** | **Bold repo name** + **≤2 short lines** + at most **one** copy-paste command (e.g. `npx skills add …`) — same scan pattern popular profiles use for “flagship OSS” without cloning the repo’s full README | Full feature matrices, changelog, or install docs pasted into the profile file |
| **Layout** | Optional **centered** header (`<div align="center">`) for **name + tagline + badges only**; body stays left-aligned markdown for readability | Center-wrapping the entire README |
| **Optional widgets** | Compact Shields (flat style); optional [github-readme-stats](https://github.com/anuraghazra/github-readme-stats) / [star-history](https://star-history.com) — **third-party**, treat as **conversion/social proof**, not core SEO | Wall of `for-the-badge` badges when the same CTAs are repeated in text |

**Minimal outline (typical profile):**

1. Title + answer-first tagline (+ slim badge row).
2. `### What I do` — identity, proof link(s), **without** repeating the same URLs again later.
3. `### Open source` — bold repo links + pitches + optional one code fence.
4. `### Find me` — single line of deduped links (site · bio · cases · social · email).
5. `### Activity` (optional) — small **github-readme-stats** + **star-history**; **alt text** on `<img>`.

Reference pattern (high-signal, low-noise): scan-first profiles such as [alchaincyf](https://github.com/alchaincyf) — short `###` blocks, bold product/repo names, one “find me” cluster.

**Entity hub pattern:** When the person has a canonical site, lead with it in the **opening line** and mirror the same URL in **Pinned** / **profile About** (if used) so **site ↔ GitHub OSS** stay aligned for **entity-seo**.

### Profile README checklist (short)

- [ ] H1 + **one** answer-first tagline (keywords: role, stack, domain)
- [ ] Canonical **outbound** links (site, social, email) **deduplicated**
- [ ] **Pinned** repos (≤6) match the story told in the README
- [ ] Optional: **Activity** section — group stats / star-history under one heading instead of scattering widgets
- [ ] **Last updated** footnote for freshness (GEO signal)

## Repository home: layout map

| Area | Typical contents | SEO / ops note |
|------|------------------|----------------|
| **Main column** | File list; rendered **root README** below | First screen and H2/H3 carry most narrative |
| **About sidebar** | **Description**, **Website**, **Topics**, releases shortcut, license, languages | Keep Description and README first paragraph consistent; **Website** should match the primary outbound CTA |
| **Other tabs** | Issues, PRs, Actions, etc. | Engagement and freshness signals |

**Website field**: Maintained via repo **Settings** / **About** edit; prefer one canonical docs or product URL aligned with README links.

## In-site discovery (high level)

| Entry | Role | Caveat |
|-------|------|--------|
| **Trending** | Time-windowed visibility | Formula is **not** public; never promise ranking |
| **Explore** | Collections, themes, programs | Useful for patterns and seasonal campaigns |
| **Topics** | Topic pages tied to repository topics | Aligns with Topics metadata (see Topics section below) |
| **Search** | Query across repos and users | README + About + topics drive match quality |

UI and URLs evolve; verify on [github.com](https://github.com/).

```mermaid
flowchart LR
  discovery[Discovery or referral]
  home[Repository home]
  readme[README and About]
  outbound[Site or docs]

  discovery --> home
  home --> readme
  readme --> outbound
```

## Repository Name, About & README (SEO/GEO Priority)

**Ranking weight** (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.

### Repository Name

| Practice | Guideline |
|----------|-----------|
| **Descriptive** | Hint at what the project does |
| **Keyword-rich** | Include primary keywords (`markdown-editor` not `my-project`) |
| **Hyphens** | Separate words (`react-component-library`) |
| **Concise** | Shorter = memorable, shareable |

### About Section (Description)

| Limit | Guideline |
|-------|-----------|
| **350 chars** | Hard limit; GitHub enforces |
| **~128 chars** | Optimal for brevity; often displayed fully |
| **Content** | Primary keyword + natural variations; what it does, who it's for; link to website or docs if space |

**Example**: "A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript."

### Topics

| Limit | Guideline |
|-------|-----------|
| **6–20 topics** | Max 20; 6–10 recommended |
| **~50 chars** each | Per topic |
| **Format** | Lowercase, hyphens, numbers only |
| **Mix** | Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest) |

**Underutilized** but highly effective for discoverability and GEO.

### README Structure & Components

Targets **repository (project) READMEs** unless noted. **Profi