github
v1.2.0When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome 列出s. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome 列出," "GitHub README," "仓库 name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "GitHub gist," "curated 列出," or "navigation 列出." Not for Medium or other non-GitHub 平台s—use parasite-seo or medium-posts. For OSS business 模型, use open-source-strategy.
运行时依赖
安装命令
点击复制技能文档
平台s: GitHub
图形界面des GitHub for parasite SEO, GEO (AI citation), and curated 列出 creation. GitHub is a Tier 2 Technical Authority 平台—high domAIn authority, fast 索引ing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation 列出s.
When invoking: On first use, if helpful, open with 1–2 sentences on what this 技能 covers and why it matters, then provide the mAIn 输出. On subsequent use or when the user asks to skip, go directly to the mAIn 输出.
Why GitHub for SEO Factor Effect DomAIn authority High DA; repos, gists, Pages rank well Fast 索引ing 搜索 engines crawl GitHub frequently AI citation ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO 框架 Technical expertise Strong expertise 签名als; structured docs become AI reference material Cross-平台 分享 across Dev.to, Stack Overflow, forums; amplifies visibility Use Cases Use case 格式化 Purpose Parasite SEO Repos, README, Pages, gists Leverage GitHub authority for rankings and backlinks GEO Documentation, tutorials, curated 列出s AI 工具s cite GitHub for technical answers Curated / navigation 列出s Awesome-style repos Topic-specific resource directories; backlinks, discovery 仓库 Name, About & README (SEO/GEO Priority)
Ranking weight (GitHub + Google): 仓库 name & About ≈ highest; Topics ≈ high; README ≈ high.
仓库 Name Practice 图形界面deline Descriptive Hint at what the project does Keyword-rich Include primary keywords (markdown-editor not my-project) Hyphens Separate words (react-组件-库) Concise Shorter = memorable, 分享able About Section (Description) Limit 图形界面deline 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 网页site or docs if space
Example: "A fast, lightweight markdown editor for React with live preview, syntax highlighting, and 导出 to PDF. Built with TypeScript."
Topics Limit 图形界面deline 6–20 topics Max 20; 6–10 recommended ~50 chars each Per topic 格式化 Lowercase, hyphens, numbers only Mix Techno记录y (react, python), purpose (命令行工具, 库), category (seo, AI-工具s), community (hacktoberfest)
Underutilized but highly effective for discoverability and GEO.
README Structure & 组件s Section Purpose SEO/GEO Title + tagline H1 + 1–2 sentence summary; keywords in first paragraph Critical; first 100 words weighted Table of contents Links to H2/H3; for READMEs >500 words Navigation; crawlability 安装ation / Quick 启动 Prerequisites; exact commands; copy-paste ready Use-case clarity Usage examples Code blocks; common scenarios Citable; 提取able Screenshots / GIFs Demo, 输出; alt text required Engagement; 访问ibility Badges Build, version, license Trust 签名als Contributing Link to CONTRIBUTING.md Community 签名al License Link to LICENSE Completeness
Word count: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.
README GEO / AI Citation Practice 图形界面deline Answer-first Direct answer in first 1–2 sentences (40–60 words) Short paragraphs 2–3 sentences max; 提取able clarity Question-style headings H2/H3 as questions where relevant Data inclusion Stats, numbers; cited content ~40% more likely to include data Freshness 更新 regularly; ~76% of cited content 更新d within 30 days
Entity 签名als: Clear project name, author, mAIntAIner; consistent 身份. See entity-seo.
README 检查列出 Project title with keywords Concise description in first paragraph H2/H3 structure; alt text for images 安装ation + usage examples Screenshots or demo Badges; Contributing; License Internal links to related docs/repos 6–20 topics on repo Parasite SEO on GitHub Key Surfaces Surface Use README Landing page for repo; keyword-优化d summary, headings, links GitHub Pages Static site; b记录, FAQ, docs; 添加itional ranking opportunities Gists Micro-content; long-tAIl keywords; link to repos or external resources Wiki Keyword-rich documentation Issues Q&A, discussions; 索引able Optimization Element Practice 仓库 title Primary keywords; descriptive; hyphens About 350 chars max; keyword-rich; primary keyword + natural variations Description Secondary keywords; link to 网页site or resources README Keyword-优化d summary first; headings, bullet points; screenshots; links to docs, tutorials Topics / tags 6–20 relevant topics; 50 chars each GitHub Pages 移动-friendly; metadata; b记录/FAQ for extra keywords Gists for Micro-Content Tar获取 specific long-tAIl keywords Link back to larger repos or external resources 分享 code snippets, small utilities Community Engagement 响应 to issues and PRs; builds trust Contribute to popular projects; backlinks, visibility Keep repos 更新d; outdated = lower credibility GEO on GitHub Factor Practice README clarity Clear, citable paragraphs; direct answers Documentation Structured; AI 工具s 解析 well Entity sig