github by kostja94/marketing-skills
npx skills add https://github.com/kostja94/marketing-skills --skill github指导在 GitHub 上进行寄生虫 SEO、GEO(AI 引用)和精选列表创建。GitHub 是一个二级技术权威平台——域名权威性高,索引速度快,AI 引用概率非常高。可用于仓库、README、GitHub Pages、代码片段和 Awesome 风格的导航列表。
调用时:在首次使用时,如果适用,用 1-2 句话介绍此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用户要求跳过时,直接进入主要输出。
| 因素 | 效果 |
|---|---|
| 域名权威性 | 域名权威性高;仓库、代码片段、Pages 页面排名良好 |
| 快速索引 | 搜索引擎频繁抓取 GitHub |
| AI 引用 | ChatGPT、Perplexity 等技术查询会引用 GitHub;在 GEO 框架中属于二级平台 |
| 技术专业性 | 强大的专业信号;结构化文档成为 AI 参考材料 |
| 跨平台 | 可在 Dev.to、Stack Overflow、论坛等平台分享;放大可见性 |
| 使用场景 | 格式 | 目的 |
|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 寄生虫 SEO | 仓库、README、Pages 页面、代码片段 | 利用 GitHub 的权威性进行排名和获取反向链接 |
| GEO | 文档、教程、精选列表 | AI 工具引用 GitHub 获取技术答案 |
| 精选/导航列表 | Awesome 风格仓库 | 特定主题的资源目录;获取反向链接,提高发现度 |
排名权重(GitHub + Google):仓库名称和关于部分 ≈ 最高;主题 ≈ 高;README ≈ 高。
| 实践 | 指南 |
|---|---|
| 描述性 | 暗示项目功能 |
| 关键词丰富 | 包含主要关键词(使用 markdown-editor 而非 my-project) |
| 连字符 | 分隔单词(react-component-library) |
| 简洁 | 越短越容易记忆和分享 |
| 限制 | 指南 |
|---|---|
| 350 字符 | 硬性限制;GitHub 强制执行 |
| 约 128 字符 | 简洁性最佳;通常能完全显示 |
| 内容 | 主要关键词 + 自然变体;功能描述,目标用户;如果空间允许,可链接到网站或文档 |
示例:"一个快速、轻量级的 React Markdown 编辑器,具有实时预览、语法高亮和导出为 PDF 功能。使用 TypeScript 构建。"
| 限制 | 指南 |
|---|---|
| 6–20 个主题 | 最多 20 个;推荐 6–10 个 |
| 每个约 50 字符 | 每个主题 |
| 格式 | 小写,使用连字符,仅限数字 |
| 混合 | 技术(react, python)、用途(cli, library)、类别(seo, ai-tools)、社区(hacktoberfest) |
未被充分利用,但对发现度和 GEO 非常有效。
| 部分 | 目的 | SEO/GEO |
|---|---|---|
| 标题 + 标语 | H1 + 1-2 句摘要;关键词出现在第一段 | 关键;前 100 个词权重高 |
| 目录 | 链接到 H2/H3;适用于超过 500 词的 README | 导航;可抓取性 |
| 安装 / 快速开始 | 先决条件;精确命令;可复制粘贴 | 使用场景清晰度 |
| 使用示例 | 代码块;常见场景 | 可引用;可提取 |
| 截图 / GIF | 演示、输出;需要替代文本 | 参与度;可访问性 |
| 徽章 | 构建、版本、许可证 | 信任信号 |
| 贡献指南 | 链接到 CONTRIBUTING.md | 社区信号 |
| 许可证 | 链接到 LICENSE | 完整性 |
字数:无硬性限制;产品仓库通常 500–1,500 词。先提供价值,后续扩展。
| 实践 | 指南 |
|---|---|
| 答案优先 | 在前 1-2 句中提供直接答案(40–60 词) |
| 短段落 | 最多 2-3 句;提取清晰 |
| 问题式标题 | 在相关处使用 H2/H3 作为问题 |
| 包含数据 | 统计数据、数字;包含数据的引用内容可能性高出约 40% |
| 新鲜度 | 定期更新;约 76% 的引用内容在 30 天内更新过 |
实体信号:清晰的项目名称、作者、维护者;身份一致。参见 entity-seo。
| 载体 | 用途 |
|---|---|
| README | 仓库的着陆页;关键词优化的摘要、标题、链接 |
| GitHub Pages | 静态网站;博客、常见问题、文档;额外的排名机会 |
| 代码片段 | 微内容;长尾关键词;链接到仓库或外部资源 |
| Wiki | 关键词丰富的文档 |
| Issues | 问答、讨论;可被索引 |
| 元素 | 实践 |
|---|---|
| 仓库标题 | 主要关键词;描述性;使用连字符 |
| 关于部分 | 最多 350 字符;关键词丰富;主要关键词 + 自然变体 |
| 描述 | 次要关键词;链接到网站或资源 |
| README | 关键词优化的摘要在前;标题、项目符号;截图;链接到文档、教程 |
| 主题 / 标签 | 6–20 个相关主题;每个 50 字符 |
| GitHub Pages | 移动端友好;元数据;博客/常见问题用于增加关键词 |
| 因素 | 实践 |
|---|---|
| README 清晰度 | 清晰、可引用的段落;直接答案 |
| 文档 | 结构化;AI 工具解析效果好 |
| 实体信号 | 清晰的项目、作者身份;参见 entity-seo |
| 一致性 | 积极维护;参与度(星标、复刻、关注者) |
Awesome 列表 = GitHub 上特定主题的精选资源列表。功能类似于导航目录;流量高,反向链接多,发现度高。sindresorhus/awesome(44.1万+ 星标)是主列表;现有 6,500+ 个涵盖各种主题的精选列表。
| 类别 | 示例 |
|---|---|
| 主列表 | sindresorhus/awesome — 所有 awesome 列表的中心 |
| SEO / 营销 | awesome-seo, awesome-ai-seo, bmpi-dev/awesome-seo |
| AI / 机器学习 | awesome-ai-tools, AITreasureBox, awesome-ai |
| 开发工具 | awesome-tools, awesome-cli, awesome-nodejs |
| 编程语言 | awesome-python, awesome-javascript, awesome-go |
| 前端 / 后端 | awesome-react, awesome-vue, awesome-django |
| 其他 | awesome-security, awesome-gaming, awesome-databases |
| 元素 | 实践 |
|---|---|
| 标题 | 清晰、聚焦(例如,"Awesome SEO"、"Awesome AI Tools") |
| 描述 | 简洁;范围明确 |
| 章节 | 分类(例如,教程、工具、文章) |
| 条目 | 精选,非收集;仅包含你推荐的内容 |
| 条目格式 | - [名称](URL) - 简要说明其为何出色 |
| 许可证 | CC0 或类似 |
| 贡献指南 | contributing.md 用于 PR 流程 |
| 操作 | 用途 |
|---|---|
| 提交到现有列表 | 向 awesome-* 仓库提交 PR;遵循列表格式;联系维护者 |
| 创建新列表 | 当你的细分领域没有列表时;遵循 awesome 指南 |
| 列表间链接 | 链接到其他覆盖相关主题更好的 awesome 列表 |
| 错误 | 避免 |
|---|---|
| 忽视参与度 | 不回复 Issues/PRs 会降低信任度 |
| 不定期更新 | 过时的仓库表明不活跃 |
| 文档不完整 | 缺乏清晰描述会让用户感到沮丧 |
| 通用标题 | 缺少关键词会降低发现度 |
| 内容贫乏的 awesome 列表 | 低质量或未精选的条目会损害可信度 |
每周安装次数
105
仓库
GitHub 星标数
237
首次出现
13 天前
安全审计
安装于
cursor99
gemini-cli98
kimi-cli98
codex98
opencode98
github-copilot98
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.
| 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 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 |
Ranking weight (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.
| 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 |
| 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."
| 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.
| 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 |
| Installation / Quick start | Prerequisites; exact commands; copy-paste ready | Use-case clarity |
| Usage examples | Code blocks; common scenarios | Citable; extractable |
| Screenshots / GIFs | Demo, output; alt text required | Engagement; accessibility |
| Badges | Build, version, license | Trust signals |
| Contributing | Link to CONTRIBUTING.md | Community signal |
Word count : No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.
| Practice | Guideline |
|---|---|
| Answer-first | Direct answer in first 1–2 sentences (40–60 words) |
| Short paragraphs | 2–3 sentences max; extractable clarity |
| Question-style headings | H2/H3 as questions where relevant |
| Data inclusion | Stats, numbers; cited content ~40% more likely to include data |
| Freshness | Update regularly; ~76% of cited content updated within 30 days |
Entity signals : Clear project name, author, maintainer; consistent identity. See entity-seo.
| Surface | Use |
|---|---|
| README | Landing page for repo; keyword-optimized summary, headings, links |
| GitHub Pages | Static site; blog, FAQ, docs; additional ranking opportunities |
| Gists | Micro-content; long-tail keywords; link to repos or external resources |
| Wiki | Keyword-rich documentation |
| Issues | Q&A, discussions; indexable |
| Element | Practice |
|---|---|
| Repository title | Primary keywords; descriptive; hyphens |
| About | 350 chars max; keyword-rich; primary keyword + natural variations |
| Description | Secondary keywords; link to website or resources |
| README | Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials |
| Topics / tags | 6–20 relevant topics; 50 chars each |
| GitHub Pages | Mobile-friendly; metadata; blog/FAQ for extra keywords |
| Factor | Practice |
|---|---|
| README clarity | Clear, citable paragraphs; direct answers |
| Documentation | Structured; AI tools parse well |
| Entity signals | Clear project, author identity; see entity-seo |
| Consistency | Active maintenance; engagement (stars, forks, watchers) |
Awesome lists = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus/awesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics.
| Category | Examples |
|---|---|
| Master list | sindresorhus/awesome — hub of all awesome lists |
| SEO / Marketing | awesome-seo, awesome-ai-seo, bmpi-dev/awesome-seo |
| AI / ML | awesome-ai-tools, AITreasureBox, awesome-ai |
| Dev tools | awesome-tools, awesome-cli, awesome-nodejs |
| Languages | awesome-python, awesome-javascript, awesome-go |
| Frontend / Backend | awesome-react, awesome-vue, awesome-django |
| Other | awesome-security, awesome-gaming, awesome-databases |
| Element | Practice |
|---|---|
| Title | Clear, focused (e.g., "Awesome SEO," "Awesome AI Tools") |
| Description | Succinct; scope clear |
| Sections | Categorized (e.g., Tutorials, Tools, Articles) |
| Items | Curated, not collected; only include what you recommend |
| Item format | - [Name](URL) - Brief description of why it's awesome |
| License | CC0 or similar |
| Contributing | contributing.md for PR process |
| Action | Use |
|---|---|
| Submit to existing list | PR to awesome-* repos; follow list format; contact maintainer |
| Create new list | When no list exists for your niche; follow awesome guidelines |
| Link between lists | Link to other awesome lists that cover subjects better |
| Mistake | Avoid |
|---|---|
| Ignoring engagement | Not responding to issues/PRs reduces trust |
| Irregular updates | Outdated repos signal inactivity |
| Incomplete docs | Lack of clear descriptions frustrates users |
| Generic titles | Missing keywords reduces discoverability |
| Thin awesome lists | Low-quality or uncurated items hurt credibility |
Weekly Installs
105
Repository
GitHub Stars
237
First Seen
13 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
cursor99
gemini-cli98
kimi-cli98
codex98
opencode98
github-copilot98
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
116,600 周安装
| License | Link to LICENSE | Completeness |