ClawHub

Github Trending

v1.0.0

获取 GitHub 热门趋势项目（每日/每周/每月），访问每个仓库了解项目功能。默认返回前 10 个项目，包含描述、统计数据和从 README 提取的实际功能。用于用户询问 GitHub 趋势、热门仓库、流行项目时。始终用中文输出结果。

⭐ 0· 112·0 current·0 all-time
byZhu Xiaoke@zhuxiaoke27
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (GitHub trending analysis) align with the instructions: fetching GitHub trending pages, visiting repo pages, extracting README snippets and metadata. No unrelated credentials, binaries, or install steps are requested.
ℹ
Instruction Scope
Instructions are focused on scraping GitHub public pages and extracting README content and stats. They explicitly limit README extracts (~500 chars / 3-5 paragraphs) and request sequential fetching to avoid rate limits. One minor note: the SKILL.md suggests optionally caching results to memory/github-trending-{date}.json (writing agent memory/files) though no config paths are declared—this is reasonable for caching but worth being aware of.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk because nothing is downloaded or installed.
✓
Credentials
The skill requests no environment variables, credentials, or access to unrelated config paths. Its behavior (scraping public GitHub pages) does not require secrets.
✓
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform-wide privileges. The optional cache suggestion writes to a skill-specific memory path, which is normal for caching.
Assessment
This skill is internally consistent: it scrapes public GitHub trending pages and repo READMEs and does not ask for secrets or install code. Things to consider before installing: (1) scraping is subject to GitHub rate limits and terms—if you need higher request rates consider using the GitHub API and an appropriate token; (2) caching to memory/github-trending-{date}.json will store fetched public data in the agent's memory—confirm you’re okay with that retention; (3) the skill will fetch many public pages (potentially large) so expect network usage and possible delays; (4) as always, review outputs for any unexpected content and avoid exposing sensitive tokens elsewhere. Overall the skill appears coherent and proportional to its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk977nn422r9dq1mk5wkq4ewjh183rz88

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments