playbooks

home / skills / wwwzhouhui / skills_collection / github-trending

github-trending skill

/github-trending

This skill fetches the top five GitHub trending projects, generates Chinese summaries, and sends them via enterprise WeChat to your team.

npx playbooks add skill wwwzhouhui/skills_collection --skill github-trending

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
812 B
---
name: github-trending
description: 获取 GitHub Trending 前五项目的 README 与摘要，并发送企业微信消息。适用于热门项目跟踪、技术趋势简报与团队分享。
---

# GitHub Trending 摘要推送

## 功能
- 抓取 https://github.com/trending 今日热门前 5 项目
- 拉取每个项目 README
- 生成包含项目是什么、解决问题、技术栈、Star 数量的中文摘要
- 通过企业微信机器人发送摘要

## 脚本
### 1. 抓取与保存
```bash
python fetch_trending.py --output trending_top5.json
```

### 2. 生成摘要并发送
```bash
python send_wecom_summary.py --input trending_top5.json
```

## 配置
- 可选环境变量 `GITHUB_TOKEN` 用于提高 GitHub API 额度
- 可选环境变量 `WEIXIN_WEBHOOK` 覆盖默认企业微信机器人地址

Overview

This skill fetches the top five GitHub Trending projects for today, retrieves each project's README, generates concise summaries, and sends the results to a corporate WeChat (WeCom) robot. It automates trend tracking so teams receive a daily digest of notable open-source projects and their key details.

How this skill works

The tool scrapes GitHub Trending or uses the GitHub API to identify the top 5 projects, pulls each project's README content, and extracts key information (what the project is, the problem it solves, main tech stack, and star count). It generates brief summaries and posts them as messages through a configured WeCom webhook. Optional environment variables allow a GitHub token to raise API limits and a custom WeCom webhook URL.

When to use it

  • Delivering a daily or weekly team digest of hot open-source projects.
  • Monitoring technology trends and identifying emerging libraries.
  • Preparing briefings for engineering or product teams.
  • Automating lightweight scouting for new tools to evaluate.
  • Sharing curated content in Slack/WeCom channels for awareness.

Best practices

  • Set GITHUB_TOKEN to avoid rate limits when fetching repository data.
  • Configure WEIXIN_WEBHOOK to point to a dedicated WeCom robot for summaries.
  • Run the script on a schedule (cron or CI) for consistent digests.
  • Limit README processing to the top README sections to keep messages concise.
  • Sanitize README content to remove large code blocks or binary data before summarizing.

Example use cases

  • Daily 9 AM digest to the engineering team highlighting 5 trending repos and why they matter.
  • Weekly tech radar email that includes one-sentence takeaways and star counts.
  • Onboarding packs that surface current popular tools in the organization’s tech domain.
  • Rapid scouting: identify candidate libraries for proof-of-concept work.
  • Content inspiration for blog posts or internal knowledge shares.

FAQ

Do I need a GitHub token?

A token is optional but recommended. Set GITHUB_TOKEN to increase API rate limits and reduce the chance of being throttled.

How do I change the WeCom destination?

Override the webhook by setting the WEIXIN_WEBHOOK environment variable to your robot’s URL before running the send script.