Discofork
Repository brief

VoltAgent/awesome-openclaw-skills

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:45:12.501Z
1mo ago

VoltAgent/awesome-openclaw-skills

Popular, actively maintained curated index of OpenClaw skills. It is a discovery and installation hub rather than a code-heavy application, with 5,400+ skills presented by category from the official OpenClaw Skills Registry. The repo is current and widely forked/starred, so forks are mainly interesting if you want to curate or republish the catalog in a different form.

GitHub
Loading tags...
Stars43,320
Forks4,127
Default branchmain
Last pushed2026-03-26T07:55:11Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if language localization and maintainer workflow docs matter more than having the newest upstream catalog; choose upstream if you want the most current skills index.

Choose this fork if you mainly want a Chinese-readable version of the skills catalog. Prefer upstream if you need the latest curated listings, freshest updates, or an authoritative source of record.

Prefer upstream unless you specifically want a frozen copy. This fork adds no visible value yet and is materially behind on catalog freshness.

Prefer upstream unless you specifically need an old pinned snapshot. This fork adds nothing of its own and is far behind upstream, so it is a poor choice for users who want current skill discovery or installation guidance.

Choose upstream unless you need this specific older snapshot or branding lineage. For normal adoption, the fork offers no added capability and is materially behind current upstream content.

Choose the upstream repo if you want current catalog data and ongoing maintenance. Choose this fork only if you specifically want a branded snapshot and do not care about being current.

Prefer upstream unless you explicitly want a blank starting point for your own fork. This fork adds no visible functionality and is materially behind upstream.

Prefer upstream unless you specifically need this fork's historical branding or a frozen snapshot; it adds no functional improvements and is 246 commits behind.

Choose upstream unless you need this fork’s naming/branding. It has no visible functional advantage and is behind by 36 commits, so adopters should expect stale content.

Choose upstream unless you specifically want a frozen snapshot. This fork adds no visible capabilities and is behind upstream, so it is mainly useful as a static copy.