Agent skill

GitHub Weekly Trending

解读用户粘贴的 GitHub 每周 Trending 或开源项目榜单内容，基于用户提供的候选项目、项目 README、GitHub 项目页和 DeepWiki 生成适合公众号发布的 Markdown 文章，并输出到当前项目 markdown 目录。用于 GitHub 周榜解读、每周开源热点、热门开源项目分析、公众号开源项目推荐。

GPL-2.0Auto-check passedDevelopment

Install GitHub Weekly Trending

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-weekly-trending .claude/skills/github-weekly-trending && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .claude/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/digoal/blog/tree/master/skills/github-weekly-trending

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/github-weekly-trending .agents/skills/github-weekly-trending && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .agents/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/github-weekly-trending .cursor/skills/github-weekly-trending && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .cursor/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/digoal/blog.git --path skills/github-weekly-trending

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/github-weekly-trending .gemini/skills/github-weekly-trending && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .gemini/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/github-weekly-trending .github/skills/github-weekly-trending && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .github/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add digoal/blog --skill github-weekly-trending -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install digoal/blog github-weekly-trending --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/github-weekly-trending .opencode/skills/github-weekly-trending && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "github-weekly-trending" agent skill from https://github.com/digoal/blog/tree/master/skills/github-weekly-trending into .opencode/skills/github-weekly-trending/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-weekly-trending", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: github-weekly-trending
GitHub stars: 8.6k
Token cost: ~1.5k tokens
SKILL.md length: 421 words
Files: 1
Skills in repo: 98
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: GPL-2.0

At a glance

Works in 6 steps: 解析用户粘贴的榜单内容 → 筛选项目 → 获取 README 和项目基础信息 → …
Tasks that involve Technical documentation
SKILL.md covers 目标, 触发条件, 数据来源优先级 and 输出文件, plus 7 more sections
Reaches github.com and raw.githubusercontent.com

What it does

GitHub Weekly Trending is an agent skill from digoal/blog. 解读用户粘贴的 GitHub 每周 Trending 或开源项目榜单内容，基于用户提供的候选项目、项目 README、GitHub 项目页和 DeepWiki 生成适合公众号发布的 Markdown 文章，并输出到当前项目 markdown 目录。用于 GitHub 周榜解读、每周开源热点、热门开源项目分析、公众号开源项目推荐。

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation and Markdown. It works with GitHub, Model Context Protocol and MarkItDown. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.

When your agent uses it

Tasks that involve Technical documentation
Tasks that involve Markdown

Example prompts

“/github-weekly-trending”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

解析用户粘贴的榜单内容
筛选项目
获取 README 和项目基础信息
使用 DeepWiki 辅助理解
建立项目事实卡
生成文章

What it can do on your machine

Read from SKILL.md and the folder at commit 69fb793. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and mermaid).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
- raw.githubusercontent.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Weekly Trending loads about 1.5k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 421 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~47
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from digoal/blog at commit 69fb793, republished under its GPL-2.0 licence (© digoal). 421 words, ~1,533 tokens.

Download SKILL.mdSave it as .claude/skills/github-weekly-trending/SKILL.md (or your agent's skills folder).

name: github-weekly-trending
description: 解读用户粘贴的 GitHub 每周 Trending 或开源项目榜单内容，基于用户提供的候选项目、项目 README、GitHub 项目页和 DeepWiki 生成适合公众号发布的 Markdown 文章，并输出到当前项目 markdown 目录。用于 GitHub 周榜解读、每周开源热点、热门开源项目分析、公众号开源项目推荐。

GitHub 每周热门项目解读

目标

读取用户粘贴的 GitHub Trending 周榜或开源项目榜单内容，筛选值得关注的开源项目，先建立可验证的项目事实卡，再生成适合公众号发布的中文 Markdown 文章。

工作流：

用户粘贴榜单内容 -> README / GitHub 项目页 -> DeepWiki -> 项目事实卡 -> 公众号文章 -> 当前项目 markdown 目录 -> 事实校验

触发条件

用户询问以下内容时使用本技能：

GitHub 每周热门项目
GitHub Trending 周榜解读
每周开源热点分析
热门开源项目介绍
公众号开源项目推荐文章
本周值得关注的开源项目

数据来源优先级

来源	用途	可靠性要求
用户粘贴的榜单内容	获取候选项目、语言、本周热度、简介、用户关注点	必须记录用户提供内容的时间和可解析字段
GitHub 仓库页	stars、license、默认分支、release、issue、贡献活跃度	以页面当前展示为准
README / 官方文档	项目定位、核心能力、安装方式、官方示例	项目功能事实的主要来源
DeepWiki MCP	架构、代码组织、模块关系、实现机制	用于辅助理解，不单独作为商业采用或性能结论来源
官方博客 / 官方案例 / release note	采用案例、路线图、重要变更	有明确链接才可引用

禁止把未验证信息写成事实。尤其不要编造公司采用案例、benchmark 结果、创始团队动机、融资信息、客户信息、性能优劣。

输出文件

默认输出 Markdown 文件：

text

markdown/github-weekly-trending-YYYY-WW.md

其中 YYYY 为年份，WW 为 ISO 周数，例如 2026-W15。

在当前项目根目录下创建或复用 markdown/ 目录。如用户指定路径或文件名，按用户要求执行。

操作步骤

Step 1 - 解析用户粘贴的榜单内容

不要主动访问 https://github.com/trending?since=weekly&spoken_language_code= 获取榜单。以用户粘贴的内容作为候选项目输入。

内部记录：

处理时间和时区
输入来源、原始 URL、榜单类型、语言过滤或日期等来源元数据只用于事实校验，不写入最终文章，除非用户明确要求展示
若来源元数据缺失，只在内部事实卡中记为未知；最终文章不要写“用户未提供”等过程性表述

从用户粘贴内容中解析候选项目：

项目名称：owner/repo
项目简介
主要语言
当前 stars
用户粘贴内容中展示的本周新增 stars 或热度指标
仓库地址

当用户只提供 owner/repo 或类似 owner / repo 的项目名时，自动补齐：

标准项目名：去掉 / 两侧空格，规范为 owner/repo
GitHub 仓库地址：https://github.com/owner/repo
DeepWiki MCP repoName 参数：使用同一个标准项目名 owner/repo

示例：用户提供 microsoft / markitdown 时，记录项目名为 microsoft/markitdown，仓库地址为 https://github.com/microsoft/markitdown，并在 DeepWiki MCP 中使用 repoName: "microsoft/markitdown"。

注意：“本周新增 stars”或热度指标以用户粘贴内容为准，不等同于完整历史审计数据。

如果用户粘贴内容无法解析出足够候选项目，先向用户请求补充榜单内容。不要自行抓取 GitHub Trending 页面替代用户输入。

Step 2 - 筛选项目

默认选择 3 个主项目深度解读。用户指定数量时按用户要求执行。

优先选择：

周榜排名靠前
用户粘贴内容中本周新增 stars 或热度指标明显
README 和文档信息充分
有清晰使用场景
对中文开发者或中国技术社区有参考价值

谨慎选择：

刚初始化、代码和文档很少的项目
没有 license 的项目
README 只有愿景、缺少可验证功能的项目
主要信息来自营销页面而非代码或文档的项目

可以增加 2-5 个“简短观察”项目，但不要把每个项目都写成完整深度分析。

Step 3 - 获取 README 和项目基础信息

优先通过 GitHub 仓库页识别默认分支和 README 文件。

README fallback 顺序：

GitHub 仓库首页渲染 README
https://raw.githubusercontent.com/{owner}/{repo}/{default_branch}/README.md
README.rst、README.adoc、README.txt
仓库中的 docs/ 或 README 指向的官方文档

同时记录：

License
最近 release 或 tag
最近提交活跃度
open issues / pull requests 的大致状态
官方文档地址，若存在

Step 4 - 使用 DeepWiki 辅助理解

对每个主项目使用 DeepWiki MCP：

read_wiki_structure：先查看可用文档结构
read_wiki_contents：读取项目整体说明
ask_question：针对架构、核心模块、实现机制、适用场景提问

建议提问：

这个项目的核心架构是什么？
主要模块如何协作？
它解决的核心技术问题是什么？
和常见同类方案相比，设计差异在哪里？
有哪些适合从代码或文档中验证的最佳实践？

DeepWiki 结论必须和 README、代码结构或官方文档交叉检查。不要仅凭 DeepWiki 写企业采用、商业化、融资、性能 benchmark。

Step 5 - 建立项目事实卡

写文章前，先为每个主项目建立事实卡。事实卡可以不出现在最终文章中，但文章必须基于事实卡生成。

每张事实卡包含：

仓库：[owner/repo](https://github.com/owner/repo)
官方一句话定位
主要语言
stars 和用户粘贴内容中的本周新增 stars 或热度指标
license
最近 release / 活跃度摘要
核心能力：3-5 条，必须来自 README 或官方文档
架构摘要：来自 DeepWiki，并和仓库资料交叉验证
适用场景：区分事实和推断
已验证来源链接
不确定信息：明确列出，不得在正文中扩写成事实

Show full SKILL.md (179 more words)Show less

Step 6 - 生成文章

文章结构：

markdown

# 主标题：项目名或本周趋势 + 核心价值

> 副标题：一句话说明本周看点

## 导言

## 本周趋势总览

## 一图看懂本周热点

## 项目一：owner/repo

### 项目定位
### 核心能力
### 架构或工作流图
### 为什么会火
### 适用场景
### 局限与风险

## 项目二：owner/repo

...

## 其他值得关注的项目

## 总结

## 参考资料

导言只保留面向读者的文章信息：

处理时间：YYYY-MM-DD HH:MM:SS 时区
紧接 1-2 段本周趋势判断，例如“本周榜单的核心信号很明确：...”。

导言不要写输入来源、榜单原始 URL、榜单日期范围、语言过滤条件等过程性字段，除非用户明确要求。

最终文章全文禁止出现以下过程性表述或同类变体：

“用户粘贴内容显示”
“用户粘贴”
“用户未提供”
“用户粘贴周榜”
“本文的候选项目只来自... ”
“没有主动抓取... ”
“按原样记录”

需要表达热度来源时，改写为面向读者的自然表述，例如“本周榜单热度为 ...”“榜单数据显示 ...”“当前 GitHub 页面显示 ...”。

每个主项目必须包含：

项目定位：2-3 句话说明它解决什么问题，基于 README 或官方文档
核心能力：表格列出 3-5 个主要功能，只写可验证能力
架构或工作流图：优先使用 Mermaid，基于 README、官方文档、DeepWiki 交叉验证后的模块关系绘制；信息不足时省略
为什么会火：结合榜单热度表现、技术趋势、开发者痛点分析，并明确区分事实和推断
适用场景：给出 2-3 个具体场景；若是推断，使用“适合用于”，不要写成“已经用于”
局限与风险：项目成熟度、文档完整度、生态依赖、license 或运维风险

图表规则

用 Mermaid 或 SVG 增强可读性，但不要为了装饰强行加图。默认优先使用 Mermaid，因为 Markdown 可维护、便于公众号二次编辑。

建议包含：

1 张“本周热点总览”图：展示候选项目 -> 筛选维度 -> 主项目 -> 简短观察项目。
每个主项目最多 1 张架构或工作流图：展示输入、核心模块、输出、外部依赖。
复杂竞品对比可以用 Mermaid quadrantChart、flowchart 或简洁表格，不要重复表达同一信息。

Mermaid 使用规则：

使用 flowchart LR 或 flowchart TD 表达流程、架构、模块关系。
使用简短节点文本，避免长句挤压版面。
节点内容必须来自 README、官方文档、代码结构或 DeepWiki 交叉验证结果。
对推断关系使用节点或图标题标注“推断”，不要画成确定事实。

SVG 使用规则：

仅当用户要求可直接发布的视觉图，或 Mermaid 无法表达清楚时使用内联 SVG。
SVG 必须简洁、可复制到 Markdown，不依赖外部图片资源。
不要使用复杂渐变、装饰性图形或无法在公众号编辑器稳定显示的效果。

示例 Mermaid：

mermaid

flowchart LR
  Input[本周榜单] --> Filter[筛选: 热度 / 文档 / 场景]
  Filter --> Main[3 个主项目深度解读]
  Filter --> Brief[2-5 个简短观察]
  Main --> Verify[README / GitHub / DeepWiki 交叉验证]
  Verify --> Article[Markdown 文章]

以下模块仅在有可靠来源时添加：

真实采用案例
竞品性能对比
可运行代码示例
创始团队或背后公司动机

如果没有可靠公开来源，写“未找到可靠公开来源”，不要补写。

竞品对比规则

竞品对比只比较可验证维度：

官方定位
核心功能
主要语言
部署方式
License
GitHub 活跃度
生态成熟度的可观察指标，例如 release、插件、文档、社区讨论

不要写无来源支持的性能结论。不要使用“全面领先”“碾压”“业界最佳”等不可验证表达。

代码示例规则

优先引用 README 或官方文档中的最小示例。

分级处理：

已本地运行：说明运行环境和结果
未本地运行但来自官方文档：标注“基于官方文档示例整理”
自行整理的伪代码或概念示例：明确标注“示意代码”

不要为了满足格式强行给每个项目写代码示例。

写作风格

面向有基础技术认知的中文开发者
专业、直接、避免夸张营销语
短句为主，少用长从句
多解释“为什么值得关注”，少堆功能清单
标题使用 ## 和 ###，避免超过 3 级标题
表格保持简洁，列数不要过多
事实和推断分开表达

质量校验

提交前逐项检查：

记录了处理时间、时区和用户粘贴内容中的来源信息
未主动抓取 GitHub Trending 页面作为候选项目来源
所有仓库地址可访问
stars、license、语言信息来自 GitHub 当前页面或用户粘贴内容，并区分来源
README / 官方文档链接可访问
DeepWiki 结论没有被单独用作商业采用或性能事实
公司采用案例、benchmark、融资、团队动机都有可靠来源；否则删除或标注未知
竞品对比只包含可验证维度
代码示例标注了来源和验证状态
Mermaid 或 SVG 图表只表达已验证事实或明确标注的推断，节点文本简短可读
Markdown 标题层级、表格、链接格式正确
输出文件位于当前项目 markdown/ 目录，除非用户指定其他路径
全文默认 3000-6000 字；若超过，优先压缩项目数量和重复背景介绍

失败和不确定情况

如果用户没有粘贴榜单内容，向用户请求输入，不要自行抓取 Trending 页面。
如果用户粘贴内容缺少 stars、本周新增 stars、语言等字段，可以用 GitHub 仓库页补充当前字段；缺少的榜单热度字段保持未知。
如果某项目 README 信息不足，降级为“简短观察”，不要做深度解读。
如果 DeepWiki 没有覆盖该项目，以 README、官方文档和仓库信息为主。
如果无法验证某个事实，保留不确定性，不要为了文章完整而补事实。

Files

Just SKILL.md in skills/github-weekly-trending of digoal/blog.

Open the folder on GitHubat commit 69fb793

Compare with similar skills

GitHub Weekly Trending next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Weekly Trending compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
GitHub Weekly Trending this skilldigoal/blog	8.6k	—	~1.5k	Automated safety check: Pass	GPL-2.0	10 days ago
Markdown Without Hard Wrapsprisma/orm	48k	—	~472	Automated safety check: Pass	Apache-2.0	today
Library Documentation Seekerwithkynam/vibecode-pro-max-kit	1.1k	2 repos	~1k	Automated safety check: Notes	MIT	3 mo ago
Update .NET Supported OS Matrixdotnet/core	22k	—	~4.1k	Automated safety check: Pass	MIT	today
README Badges and Headersjal-co/shieldcn	916	—	~4.3k	Automated safety check: Pass	MIT	yesterday
Githits MCPgithits-com/githits-cli	114	—	~2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Markdown Without Hard Wraps
prisma/orm
Official
Keeps Markdown prose on one line per paragraph instead of wrapping at a fixed column, so renderers can reflow it and diffs stay clean.
48k GitHub stars~472 tokensUpdated today
DevelopmentAuto-check passed
Library Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
1.1k GitHub starsUsed in 2 repos~1k tokens
DevelopmentAuto-check: notes
Update .NET Supported OS Matrix
dotnet/core
Official
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
22k GitHub stars~4.1k tokensUpdated today
DevelopmentAuto-check passed
README Badges and Headers
jal-co/shieldcn
Adds shadcn/ui-styled README badges, badge groups, download charts, header banners and sponsor or contributor grids using the shieldcn service.
916 GitHub stars~4.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Githits MCP
githits-com/githits-cli
Route public OSS code, documentation, examples, and package questions to GitHits tools.
114 GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed
Firecrawl Developer Index
firecrawl/skills
Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites.
116 GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed

More from digoal/blog

All 98 skills in this repo

Article Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
8.6k GitHub stars~939 tokensUpdated 10 days ago
Auto-check passed
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
8.6k GitHub stars~4k tokensUpdated 10 days ago
Auto-check passed
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
8.6k GitHub stars~2.2k tokensUpdated 10 days ago
Auto-check passed
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
8.6k GitHub stars~1.5k tokensUpdated 10 days ago
Auto-check passed
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
8.6k GitHub stars~1.8k tokensUpdated 10 days ago
Auto-check passed
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
8.6k GitHub stars~1.4k tokensUpdated 10 days ago
Auto-check passed

Works with

Questions about GitHub Weekly Trending

What does GitHub Weekly Trending do?

When should I use GitHub Weekly Trending?

GitHub Weekly Trending fits situations like: tasks that involve Technical documentation; tasks that involve Markdown.

How do I install GitHub Weekly Trending in Claude Code?

Run `npx skills add digoal/blog --skill github-weekly-trending -a claude-code`. Or copy the skill folder (skills/github-weekly-trending in digoal/blog) into .claude/skills/github-weekly-trending in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Weekly Trending in Codex?

Run `npx skills add digoal/blog --skill github-weekly-trending -a codex`. Or copy the skill folder (skills/github-weekly-trending in digoal/blog) into .agents/skills/github-weekly-trending in your project. Codex loads it when a task matches its description.

Can I use GitHub Weekly Trending in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add digoal/blog --skill github-weekly-trending -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-weekly-trending, .gemini/skills/github-weekly-trending, .github/skills/github-weekly-trending and .opencode/skills/github-weekly-trending in your project.

What does GitHub Weekly Trending need to run?

SKILL.md names no scripts, command-line tools or credentials: GitHub Weekly Trending is instructions for the agent only.

Does GitHub Weekly Trending access the network?

SKILL.md names 2 domains. In commands or code: github.com and raw.githubusercontent.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is GitHub Weekly Trending safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Weekly Trending use?

GitHub Weekly Trending is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Weekly Trending use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Weekly Trending?

Skills that share tags, products or a category with GitHub Weekly Trending: Markdown Without Hard Wraps (prisma/orm, 48k stars), Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars), Update .NET Supported OS Matrix (dotnet/core, 22k stars) and README Badges and Headers (jal-co/shieldcn, 916 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Weekly Trending?

digoal (a GitHub user) maintains it in digoal/blog, which has 8,587 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on September 28, 2026.

Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install GitHub Weekly Trending

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub 每周热门项目解读

目标

触发条件

数据来源优先级

输出文件

操作步骤

Step 1 - 解析用户粘贴的榜单内容

Step 2 - 筛选项目

Step 3 - 获取 README 和项目基础信息

Step 4 - 使用 DeepWiki 辅助理解

Step 5 - 建立项目事实卡

Step 6 - 生成文章

图表规则

竞品对比规则

代码示例规则

写作风格

质量校验

失败和不确定情况

Files

Compare with similar skills

Similar skills

More from digoal/blog

Related

Questions about GitHub Weekly Trending