[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71APMEXKAWMXFQM90N3EZHS":3,"skill-same:01M71APMEXKAWMXFQM90N3EZHS":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71APMEXKAWMXFQM90N3EZHS","github",null,"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\" or \"GitHub GEO\". Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fplatforms\u002Fgithub\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"for","oss","business model","open-source","business","use","strategy","geo","Optimization","README","seo","open source marketing","source","marketing","when","open source","open","model","posts","2026-11-10 10:12:30",false,"---\nname: github\ndescription: 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\" or \"GitHub GEO\". Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.\nmetadata:\n  version: 1.3.0\n---\n\n# Platforms: GitHub\n\nGuides 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.\n\n**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.\n\n## Why GitHub for SEO\n\n| Factor | Effect |\n|--------|--------|\n| **Domain authority** | High DA; repos, gists, Pages rank well |\n| **Fast indexing** | Search engines crawl GitHub frequently |\n| **AI citation** | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework |\n| **Technical expertise** | Strong expertise signals; structured docs become AI reference material |\n| **Cross-platform** | Share across Dev.to, Stack Overflow, forums; amplifies visibility |\n\n## Use Cases\n\n| Use case | Format | Purpose |\n|----------|--------|---------|\n| **Parasite SEO** | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks |\n| **GEO** | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers |\n| **Curated \u002F navigation lists** | Awesome-style repos | Topic-specific resource directories; backlinks, discovery |\n\n## Surfaces: profile vs repository\n\n| Surface | What it is | Optimization focus |\n|---------|------------|---------------------|\n| **Profile README** | Public repo **with the same name as the username**; root `README.md` renders on the profile | Personal brand, flagship links, social proof |\n| **Pinned** | Up to **6** repos or gists on the profile | Showcase top projects; align with entity signals (**entity-seo**) |\n| **Per-repo README** | Root `README.md` on each repo’s **Code** tab | Product landing; install, proof, CTAs |\n\nChanging a normal repo README does **not** change the profile banner unless that content is the **profile README** repo or linked from it.\n\n## Repository home: layout map\n\n| Area | Typical contents | SEO \u002F ops note |\n|------|------------------|----------------|\n| **Main column** | File list; rendered **root README** below | First screen and H2\u002FH3 carry most narrative |\n| **About sidebar** | **Description**, **Website**, **Topics**, releases shortcut, license, languages | Keep Description and README first paragraph consistent; **Website** should match the primary outbound CTA |\n| **Other tabs** | Issues, PRs, Actions, etc. | Engagement and freshness signals |\n\n**Website field**: Maintained via repo **Settings** \u002F **About** edit; prefer one canonical docs or product URL aligned with README links.\n\n## In-site discovery (high level)\n\n| Entry | Role | Caveat |\n|-------|------|--------|\n| **Trending** | Time-windowed visibility | Formula is **not** public; never promise ranking |\n| **Explore** | Collections, themes, programs | Useful for patterns and seasonal campaigns |\n| **Topics** | Topic pages tied to repository topics | Aligns with Topics metadata (see Topics section below) |\n| **Search** | Query across repos and users | README + About + topics drive match quality |\n\nUI and URLs evolve; verify on [github.com](https:\u002F\u002Fgithub.com\u002F).\n\n```mermaid\nflowchart LR\n  discovery[Discovery or referral]\n  home[Repository home]\n  readme[README and About]\n  outbound[Site or docs]\n\n  discovery --> home\n  home --> readme\n  readme --> outbound\n```\n\n## Repository Name, About & README (SEO\u002FGEO Priority)\n\n**Ranking weight** (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.\n\n### Repository Name\n\n| Practice | Guideline |\n|----------|-----------|\n| **Descriptive** | Hint at what the project does |\n| **Keyword-rich** | Include primary keywords (`markdown-editor` not `my-project`) |\n| **Hyphens** | Separate words (`react-component-library`) |\n| **Concise** | Shorter = memorable, shareable |\n\n### About Section (Description)\n\n| Limit | Guideline |\n|-------|-----------|\n| **350 chars** | Hard limit; GitHub enforces |\n| **~128 chars** | Optimal for brevity; often displayed fully |\n| **Content** | Primary keyword + natural variations; what it does, who it's for; link to website or docs if space |\n\n**Example**: \"A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript.\"\n\n### Topics\n\n| Limit | Guideline |\n|-------|-----------|\n| **6–20 topics** | Max 20; 6–10 recommended |\n| **~50 chars** each | Per topic |\n| **Format** | Lowercase, hyphens, numbers only |\n| **Mix** | Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest) |\n\n**Underutilized** but highly effective for discoverability and GEO.\n\n### README Structure & Components\n\n| Section | Purpose | SEO\u002FGEO |\n|---------|---------|---------|\n| **Title + tagline** | H1 + 1–2 sentence summary; keywords in first paragraph | Critical; first 100 words weighted |\n| **Table of contents** | Links to H2\u002FH3; for READMEs >500 words | Navigation; crawlability |\n| **Installation \u002F Quick start** | Prerequisites; exact commands; copy-paste ready | Use-case clarity |\n| **Usage examples** | Code blocks; common scenarios | Citable; extractable |\n| **Screenshots \u002F GIFs** | Demo, output; alt text required | Engagement; accessibility |\n| **Badges** | Build, version, license | Trust signals |\n| **Contributing** | Link to CONTRIBUTING.md | Community signal |\n| **License** | Link to LICENSE | Completeness |\n\n**Word count**: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.\n\n### README GEO \u002F AI Citation\n\n| Practice | Guideline |\n|----------|-----------|\n| **Answer-first** | Direct answer in first 1–2 sentences (40–60 words) |\n| **Short paragraphs** | 2–3 sentences max; extractable clarity |\n| **Question-style headings** | H2\u002FH3 as questions where relevant |\n| **Data inclusion** | Stats, numbers; cited content ~40% more likely to include data |\n| **Freshness** | Update regularly; ~76% of cited content updated within 30 days |\n\n**Entity signals**: Clear project name, author, maintainer; consistent identity. See **entity-seo**.\n\n### README Checklist\n\n- [ ] Project title with keywords\n- [ ] Concise description in first paragraph\n- [ ] H2\u002FH3 structure; alt text for images\n- [ ] Installation + usage examples\n- [ ] Screenshots or demo\n- [ ] Badges; Contributing; License\n- [ ] Internal links to related docs\u002Frepos\n- [ ] 6–20 topics on repo\n\n## Parasite SEO on GitHub\n\n### Key Surfaces\n\n| Surface | Use |\n|---------|-----|\n| **README** | Landing page for repo; keyword-optimized summary, headings, links |\n| **GitHub Pages** | Static site; blog, FAQ, docs; additional ranking opportunities |\n| **Gists** | Micro-content; long-tail keywords; link to repos or external resources |\n| **Wiki** | Keyword-rich documentation |\n| **Issues** | Q&A, discussions; indexable |\n\n### GitHub Pages vs README\n\n| Surface | Role |\n|---------|------|\n| **README** | First impression; Stars\u002Fforks; short pitch and deep links |\n| **Pages** | Multi-page **static** site: long docs, blog, changelog |\n\n**Default URL patterns**: A **user or organization site** often uses a `username.github.io` repository and serves at `https:\u002F\u002Fusername.github.io`. A **project site** is published from a given repo and typically appears at `https:\u002F\u002Fusername.github.io\u002Frepository\u002F` (path may vary with settings). See [About GitHub Pages](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpages\u002Fgetting-started-with-github-pages\u002Fabout-github-pages).\n\n**Limits**: Build size, bandwidth, and build-frequency caps change over time—cite [GitHub Pages limits](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpages\u002Fgetting-started-with-github-pages\u002Fgithub-pages-limits) when users need numbers, not hard-coded figures from this skill.\n\n### Optimization\n\n| Element | Practice |\n|---------|----------|\n| **Repository title** | Primary keywords; descriptive; hyphens |\n| **About** | 350 chars max; keyword-rich; primary keyword + natural variations |\n| **Description** | Secondary keywords; link to website or resources |\n| **README** | Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials |\n| **Topics \u002F tags** | 6–20 relevant topics; 50 chars each |\n| **GitHub Pages** | Mobile-friendly; metadata; blog\u002FFAQ for extra keywords |\n\n### Gists for Micro-Content\n\n- Target specific long-tail keywords\n- Link back to larger repos or external resources\n- Share code snippets, small utilities\n\n### Community Engagement\n\n- Respond to issues and PRs; builds trust\n- Contribute to popular projects; backlinks, visibility\n- Keep repos updated; outdated = lower credibility\n\n## GEO on GitHub\n\n| Factor | Practice |\n|--------|----------|\n| **README clarity** | Clear, citable paragraphs; direct answers |\n| **Documentation** | Structured; AI tools parse well |\n| **Entity signals** | Clear project, author identity; see **entity-seo** |\n| **Consistency** | Active maintenance; engagement (stars, forks, watchers) |\n\n## Repository archetypes\n\n| Archetype | Intent | First-screen emphasis |\n|-----------|--------|------------------------|\n| **Product \u002F library** | Installable software, SDK, CLI, service | Install, quickstart, proof (CI, license), support path |\n| **Curated \u002F resource** | Awesome-style lists, indexes | Scope, curation bar, contribution rules |\n\nMatch metrics to type: curated lists optimize for trust and backlinks; product repos optimize for adoption and issue quality.\n\n## Curated \u002F Navigation Lists (Awesome-Style)\n\n**Awesome lists** = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus\u002Fawesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics.\n\n### Examples by Category\n\n| Category | Examples |\n|----------|----------|\n| **Master list** | sindresorhus\u002Fawesome — hub of all awesome lists |\n| **SEO \u002F Marketing** | awesome-seo, awesome-ai-seo, bmpi-dev\u002Fawesome-seo |\n| **AI \u002F ML** | awesome-ai-tools, AITreasureBox, awesome-ai |\n| **Dev tools** | awesome-tools, awesome-cli, awesome-nodejs |\n| **Languages** | awesome-python, awesome-javascript, awesome-go |\n| **Frontend \u002F Backend** | awesome-react, awesome-vue, awesome-django |\n| **Other** | awesome-security, awesome-gaming, awesome-databases |\n\n### When to Create\n\n- You have a niche with many quality resources to curate\n- Existing lists lack coverage of your topic\n- You want a backlink asset and topical authority\n\n### List Structure (sindresorhus\u002Fawesome guidelines)\n\n| Element | Practice |\n|---------|----------|\n| **Title** | Clear, focused (e.g., \"Awesome SEO,\" \"Awesome AI Tools\") |\n| **Description** | Succinct; scope clear |\n| **Sections** | Categorized (e.g., Tutorials, Tools, Articles) |\n| **Items** | Curated, not collected; only include what you recommend |\n| **Item format** | `- [Name](URL) - Brief description of why it's awesome` |\n| **License** | CC0 or similar |\n| **Contributing** | contributing.md for PR process |\n\n### Getting Listed vs. Creating\n\n| Action | Use |\n|--------|-----|\n| **Submit to existing list** | PR to awesome-* repos; follow list format; contact maintainer |\n| **Create new list** | When no list exists for your niche; follow awesome guidelines |\n| **Link between lists** | Link to other awesome lists that cover subjects better |\n\n### Discovery\n\n- **sindresorhus\u002Fawesome** — Master list of awesome lists\n- **AwesomeSearch** — Search across awesome lists\n- **more-awesome** — Directory of awesome lists\n\n## Common Mistakes\n\n| Mistake | Avoid |\n|---------|-------|\n| **Ignoring engagement** | Not responding to issues\u002FPRs reduces trust |\n| **Irregular updates** | Outdated repos signal inactivity |\n| **Incomplete docs** | Lack of clear descriptions frustrates users |\n| **Generic titles** | Missing keywords reduces discoverability |\n| **Thin awesome lists** | Low-quality or uncurated items hurt credibility |\n\n## Output Format\n\n- **Use case** (parasite SEO \u002F GEO \u002F curated list)\n- **Surface scope** (profile vs specific repository; README vs Pages)\n- **Repository name, About, Topics** (if optimizing metadata)\n- **Surface** (README, Pages, gist, awesome repo)\n- **README structure** (sections, word count, GEO practices if applicable)\n- **Optimization** (keywords, structure, links)\n- **Ready-to-use** copy or structure where applicable\n\n## Related Skills\n\n- **parasite-seo**: Parasite SEO strategy; GitHub as Tier 2 technical platform\n- **generative-engine-optimization**: GEO strategy; GitHub for AI citation\n- **open-source-strategy**: Open source commercialization; GitHub as primary distribution\n- **directory-submission**: Directory and curated list submission; awesome lists as curated lists\n- **link-building**: GitHub as link acquisition; repos, gists, awesome lists\n- **entity-seo**: Entity signals (project, author); Organization, Person\n","# Platforms: GitHub\n\nGuides 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.\n\n**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.\n\n## Why GitHub for SEO\n\n| Factor | Effect |\n|--------|--------|\n| **Domain authority** | High DA; repos, gists, Pages rank well |\n| **Fast indexing** | Search engines crawl GitHub frequently |\n| **AI citation** | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework |\n| **Technical expertise** | Strong expertise signals; structured docs become AI reference material |\n| **Cross-platform** | Share across Dev.to, Stack Overflow, forums; amplifies visibility |\n\n## Use Cases\n\n| Use case | Format | Purpose |\n|----------|--------|---------|\n| **Parasite SEO** | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks |\n| **GEO** | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers |\n| **Curated \u002F navigation lists** | Awesome-style repos | Topic-specific resource directories; backlinks, discovery |\n\n## Surfaces: profile vs repository\n\n| Surface | What it is | Optimization focus |\n|---------|------------|---------------------|\n| **Profile README** | Public repo **with the same name as the username**; root `README.md` renders on the profile | Personal brand, flagship links, social proof |\n| **Pinned** | Up to **6** repos or gists on the profile | Showcase top projects; align with entity signals (**entity-seo**) |\n| **Per-repo README** | Root `README.md` on each repo’s **Code** tab | Product landing; install, proof, CTAs |\n\nChanging a normal repo README does **not** change the profile banner unless that content is the **profile README** repo or linked from it.\n\n## Repository home: layout map\n\n| Area | Typical contents | SEO \u002F ops note |\n|------|------------------|----------------|\n| **Main column** | File list; rendered **root README** below | First screen and H2\u002FH3 carry most narrative |\n| **About sidebar** | **Description**, **Website**, **Topics**, releases shortcut, license, languages | Keep Description and README first paragraph consistent; **Website** should match the primary outbound CTA |\n| **Other tabs** | Issues, PRs, Actions, etc. | Engagement and freshness signals |\n\n**Website field**: Maintained via repo **Settings** \u002F **About** edit; prefer one canonical docs or product URL aligned with README links.\n\n## In-site discovery (high level)\n\n| Entry | Role | Caveat |\n|-------|------|--------|\n| **Trending** | Time-windowed visibility | Formula is **not** public; never promise ranking |\n| **Explore** | Collections, themes, programs | Useful for patterns and seasonal campaigns |\n| **Topics** | Topic pages tied to repository topics | Aligns with Topics metadata (see Topics section below) |\n| **Search** | Query across repos and users | README + About + topics drive match quality |\n\nUI and URLs evolve; verify on [github.com](https:\u002F\u002Fgithub.com\u002F).\n\n```mermaid\nflowchart LR\n  discovery[Discovery or referral]\n  home[Repository home]\n  readme[README and About]\n  outbound[Site or docs]\n\n  discovery --> home\n  home --> readme\n  readme --> outbound\n```\n\n## Repository Name, About & README (SEO\u002FGEO Priority)\n\n**Ranking weight** (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.\n\n### Repository Name\n\n| Practice | Guideline |\n|----------|-----------|\n| **Descriptive** | Hint at what the project does |\n| **Keyword-rich** | Include primary keywords (`markdown-editor` not `my-project`) |\n| **Hyphens** | Separate words (`react-component-library`) |\n| **Concise** | Shorter = memorable, shareable |\n\n### About Section (Description)\n\n| Limit | Guideline |\n|-------|-----------|\n| **350 chars** | Hard limit; GitHub enforces |\n| **~128 chars** | Optimal for brevity; often displayed fully |\n| **Content** | Primary keyword + natural variations; what it does, who it's for; link to website or docs if space |\n\n**Example**: \"A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript.\"\n\n### Topics\n\n| Limit | Guideline |\n|-------|-----------|\n| **6–20 topics** | Max 20; 6–10 recommended |\n| **~50 chars** each | Per topic |\n| **Format** | Lowercase, hyphens, numbers only |\n| **Mix** | Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest) |\n\n**Underutilized** but highly effective for discoverability and GEO.\n\n### README Structure & Components\n\n| Section | Purpose | SEO\u002FGEO |\n|---------|---------|---------|\n| **Title + tagline** | H1 + 1–2 sentence summary; keywords in first paragraph | Critical; first 100 words weighted |\n| **Table of contents** | Links to H2\u002FH3; for READMEs >500 words | Navigation; crawlability |\n| **Installation \u002F Quick start** | Prerequisites; exact commands; copy-paste ready | Use-case clarity |\n| **Usage examples** | Code blocks; common scenarios | Citable; extractable |\n| **Screenshots \u002F GIFs** | Demo, output; alt text required | Engagement; accessibility |\n| **Badges** | Build, version, license | Trust signals |\n| **Contributing** | Link to CONTRIBUTING.md | Community signal |\n| **License** | Link to LICENSE | Completeness |\n\n**Word count**: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.\n\n### README GEO \u002F AI Citation\n\n| Practice | Guideline |\n|----------|-----------|\n| **Answer-first** | Direct answer in first 1–2 sentences (40–60 words) |\n| **Short paragraphs** | 2–3 sentences max; extractable clarity |\n| **Question-style headings** | H2\u002FH3 as questions where relevant |\n| **Data inclusion** | Stats, numbers; cited content ~40% more likely to include data |\n| **Freshness** | Update regularly; ~76% of cited content updated within 30 days |\n\n**Entity signals**: Clear project name, author, maintainer; consistent identity. See **entity-seo**.\n\n### README Checklist\n\n- [ ] Project title with keywords\n- [ ] Concise description in first paragraph\n- [ ] H2\u002FH3 structure; alt text for images\n- [ ] Installation + usage examples\n- [ ] Screenshots or demo\n- [ ] Badges; Contributing; License\n- [ ] Internal links to related docs\u002Frepos\n- [ ] 6–20 topics on repo\n\n## Parasite SEO on GitHub\n\n### Key Surfaces\n\n| Surface | Use |\n|---------|-----|\n| **README** | Landing page for repo; keyword-optimized summary, headings, links |\n| **GitHub Pages** | Static site; blog, FAQ, docs; additional ranking opportunities |\n| **Gists** | Micro-content; long-tail keywords; link to repos or external resources |\n| **Wiki** | Keyword-rich documentation |\n| **Issues** | Q&A, discussions; indexable |\n\n### GitHub Pages vs README\n\n| Surface | Role |\n|---------|------|\n| **README** | First impression; Stars\u002Fforks; short pitch and deep links |\n| **Pages** | Multi-page **static** site: long docs, blog, changelog |\n\n**Default URL patterns**: A **user or organization site** often uses a `username.github.io` repository and serves at `https:\u002F\u002Fusername.github.io`. A **project site** is published from a given repo and typically appears at `https:\u002F\u002Fusername.github.io\u002Frepository\u002F` (path may vary with settings). See [About GitHub Pages](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpages\u002Fgetting-started-with-github-pages\u002Fabout-github-pages).\n\n**Limits**: Build size, bandwidth, and build-frequency caps change over time—cite [GitHub Pages limits](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fpages\u002Fgetting-started-with-github-pages\u002Fgithub-pages-limits) when users need numbers, not hard-coded figures from this skill.\n\n### Optimization\n\n| Element | Practice |\n|---------|----------|\n| **Repository title** | Primary keywords; descriptive; hyphens |\n| **About** | 350 chars max; keyword-rich; primary keyword + natural variations |\n| **Description** | Secondary keywords; link to website or resources |\n| **README** | Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials |\n| **Topics \u002F tags** | 6–20 relevant topics; 50 chars each |\n| **GitHub Pages** | Mobile-friendly; metadata; blog\u002FFAQ for extra keywords |\n\n### Gists for Micro-Content\n\n- Target specific long-tail keywords\n- Link back to larger repos or external resources\n- Share code snippets, small utilities\n\n### Community Engagement\n\n- Respond to issues and PRs; builds trust\n- Contribute to popular projects; backlinks, visibility\n- Keep repos updated; outdated = lower credibility\n\n## GEO on GitHub\n\n| Factor | Practice |\n|--------|----------|\n| **README clarity** | Clear, citable paragraphs; direct answers |\n| **Documentation** | Structured; AI tools parse well |\n| **Entity signals** | Clear project, author identity; see **entity-seo** |\n| **Consistency** | Active maintenance; engagement (stars, forks, watchers) |\n\n## Repository archetypes\n\n| Archetype | Intent | First-screen emphasis |\n|-----------|--------|------------------------|\n| **Product \u002F library** | Installable software, SDK, CLI, service | Install, quickstart, proof (CI, license), support path |\n| **Curated \u002F resource** | Awesome-style lists, indexes | Scope, curation bar, contribution rules |\n\nMatch metrics to type: curated lists optimize for trust and backlinks; product repos optimize for adoption and issue quality.\n\n## Curated \u002F Navigation Lists (Awesome-Style)\n\n**Awesome lists** = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus\u002Fawesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics.\n\n### Examples by Category\n\n| Category | Examples |\n|----------|----------|\n| **Master list** | sindresorhus\u002Fawesome — hub of all awesome lists |\n| **SEO \u002F Marketing** | awesome-seo, awesome-ai-seo, bmpi-dev\u002Fawesome-seo |\n| **AI \u002F ML** | awesome-ai-tools, AITreasureBox, awesome-ai |\n| **Dev tools** | awesome-tools, awesome-cli, awesome-nodejs |\n| **Languages** | awesome-python, awesome-javascript, awesome-go |\n| **Frontend \u002F Backend** | awesome-react, awesome-vue, awesome-django |\n| **Other** | awesome-security, awesome-gaming, awesome-databases |\n\n### When to Create\n\n- You have a niche with many quality resources to curate\n- Existing lists lack coverage of your topic\n- You want a backlink asset and topical authority\n\n### List Structure (sindresorhus\u002Fawesome guidelines)\n\n| Element | Practice |\n|---------|----------|\n| **Title** | Clear, focused (e.g., \"Awesome SEO,\" \"Awesome AI Tools\") |\n| **Description** | Succinct; scope clear |\n| **Sections** | Categorized (e.g., Tutorials, Tools, Articles) |\n| **Items** | Curated, not collected; only include what you recommend |\n| **Item format** | `- [Name](URL) - Brief description of why it's awesome` |\n| **License** | CC0 or similar |\n| **Contributing** | contributing.md for PR process |\n\n### Getting Listed vs. Creating\n\n| Action | Use |\n|--------|-----|\n| **Submit to existing list** | PR to awesome-* repos; follow list format; contact maintainer |\n| **Create new list** | When no list exists for your niche; follow awesome guidelines |\n| **Link between lists** | Link to other awesome lists that cover subjects better |\n\n### Discovery\n\n- **sindresorhus\u002Fawesome** — Master list of awesome lists\n- **AwesomeSearch** — Search across awesome lists\n- **more-awesome** — Directory of awesome lists\n\n## Common Mistakes\n\n| Mistake | Avoid |\n|---------|-------|\n| **Ignoring engagement** | Not responding to issues\u002FPRs reduces trust |\n| **Irregular updates** | Outdated repos signal inactivity |\n| **Incomplete docs** | Lack of clear descriptions frustrates users |\n| **Generic titles** | Missing keywords reduces discoverability |\n| **Thin awesome lists** | Low-quality or uncurated items hurt credibility |\n\n## Output Format\n\n- **Use case** (parasite SEO \u002F GEO \u002F curated list)\n- **Surface scope** (profile vs specific repository; README vs Pages)\n- **Repository name, About, Topics** (if optimizing metadata)\n- **Surface** (README, Pages, gist, awesome repo)\n- **README structure** (sections, word count, GEO practices if applicable)\n- **Optimization** (keywords, structure, links)\n- **Ready-to-use** copy or structure where applicable\n\n## Related Skills\n\n- **parasite-seo**: Parasite SEO strategy; GitHub as Tier 2 technical platform\n- **generative-engine-optimization**: GEO strategy; GitHub for AI citation\n- **open-source-strategy**: Open source commercialization; GitHub as primary distribution\n- **directory-submission**: Directory and curated list submission; awesome lists as curated lists\n- **link-building**: GitHub as link acquisition; repos, gists, awesome lists\n- **entity-seo**: Entity signals (project, author); Organization, Person\n",{"name":5,"metadata":53,"description":7},{"version":54},"1.3.0","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fplatforms\u002Fgithub",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add ariadoss\u002Fsuperskills --skill github",{"tool":71,"command":72},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill github",{"tool":74,"command":75},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill github","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fplatforms\u002Fgithub\u002FSKILL.md",true,[],[80,105,129,148,177,193],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":48},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[82,90,91,92,93,94,95,96,97,43,98,99,100,101,102,34,103,104],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":48},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[112,113,93,114,115,116,117,118,119,43,120,121,122,123,124,29,125,126,127,128],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":48},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[131,136,137,138,34,139,140,141,142,143,144,115,145,43,146,147],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":48},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[158,159,160,161,162,163,164,165,166,43,167,168,169,170,171,172,173,174,175,176],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":48},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[179,123,184,185,144,115,186,187,43,188,34,189,190,191,192],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":48},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[200,201,202,203,204,205,206,43,33,34,207],"validate","idea","validate idea","framework","it","minimalist","test","before building"]