Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Added notes.security transparency block
What This Skill Does
Scans up to 1,000 forks of a GitHub repository per run using a three-stage funnel: a bash pre-filter drops inactive or identical clones, parallel sub-agents inspect surviving forks for meaningful diffs and new patterns, and a final report surfaces only forks worth attention. Separately, it reviews ClawHub skills daily, tracks trends, and follows active authors.
Bash pre-filtering eliminates dead forks before any agent tokens are spent, making 1,000-fork analysis practical without proportional cost.
When to use it
- Finding forks that added features you never shipped
- Spotting performance improvements made by community contributors
- Monitoring a popular repo for architectural changes across its fork network
- Daily discovery of new ClawHub skills and emerging usage trends
- Tracking prolific contributors through their fork activity
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Which forks of my repo have made meaningful changes?
- 1Fetches up to 1,000 forks from GitHub's public API using read-only access
- 2Runs bash pre-filter to discard inactive or byte-identical forks
- 3Spawns parallel sub-agents to inspect surviving forks for diff quality, new patterns, and performance changes
- 4Ranks forks by significance and drops empty or noise results
- 5Delivers report to the configured notification channel
Filtered list of forks with notable changes, categorized by type of modification