Github
Turn GitHub repos, READMEs, Pages, gists, and Awesome lists into indexed, AI-citable distribution assets for an open-source or devtool product.
Overview
GitHub is an agent skill most often used in Launch (also Grow) that guides GitHub-specific SEO, GEO, README optimization, Pages, gists, and Awesome lists for technical distribution.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill githubWhat is this skill?
- Positions GitHub as Tier 2 technical authority for parasite SEO and GEO
- Covers README, profile README, pinned repos, About, topics, and Website field
- GitHub Pages, gists, and Awesome-style curated navigation lists
- Explicit routing: non-GitHub parasite SEO → other skills; OSS business model → open-source-strategy
- Skill metadata version 1.5.0 with fast-indexing and high AI-citation framing
- Documents GitHub as a Tier 2 Technical Authority platform for SEO and GEO
Adoption & trust: 844 installs on skills.sh; 586 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a strong repo but almost no organic discovery because README, topics, and GitHub Pages are not structured for search engines or AI citations.
Who is it for?
Open-source founders and indie devtools using GitHub as the primary marketing surface alongside code.
Skip if: Medium or non-GitHub parasite SEO campaigns (use parasite-seo or medium-posts) or choosing OSS monetization models without SEO work.
When should I use this skill?
When the user mentions GitHub SEO, parasite SEO, GEO, awesome lists, README or profile README optimization, pinned repositories, Trending, topics, GitHub Pages, gists, or curated navigation lists—or says ‘GitHub’ in a ma
What do I get? / Deliverables
You ship optimized GitHub surfaces—repo metadata, README, pins, and optional Pages or lists—that rank faster and get cited as technical authority in AI answers.
- Optimized repo About, description, topics, and Website linkage plan
- README or profile README structure aligned to SEO and GEO
- Awesome-list or Pages content outline for discovery
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch → seo is canonical because the skill optimizes GitHub surfaces for search and generative-engine citation—primary outcome is discoverability, not repo implementation. SEO subphase fits parasite SEO, README copy, topics, and Pages meant to rank and get cited by ChatGPT and Perplexity.
Where it fits
Stand up a minimal GitHub Pages landing linked from the repo Website field to test positioning before full site build.
Rewrite README and repo topics so target keywords and use cases match how developers search.
Structure docs and lists so Perplexity and ChatGPT cite your repo for category-defining questions.
Maintain an Awesome-style curated list that earns backlinks and ongoing GitHub Explore visibility.
How it compares
Platform-specific GitHub SEO and GEO playbook—not generic social distribution and not infrastructure deployment automation.
Common Questions / FAQ
Who is github for?
Solo builders and maintainers marketing libraries, CLIs, agents, or SaaS-backed repos who want GitHub repos and Pages to rank and appear in AI-generated answers.
When should I use github?
At Launch when polishing README and repo metadata for SEO/GEO, when creating Awesome lists or gists for discovery, and in Grow when refreshing pinned repos and content for ongoing citations.
Is github safe to install?
Review the Security Audits panel on this Prism page before installing; the skill is advisory marketing guidance and does not require granting GitHub tokens by default.
Workflow Chain
Then invoke: open source strategy
SKILL.md
READMESKILL.md - Github
# 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 READ