Skills intent
OpenClaw GitHub Skills: Find, Review & Install SKILL.md
GitHub is useful when a skill is not published through ClawHub or when you want to audit its instructions and supporting files before installation.
openclaw skills install git:owner/repository@ref. The Git source must expose a SKILL.md at its root; use --as when you need to override the inferred slug.Install a reviewed skill repository
openclaw skills search "calendar"
openclaw skills install git:owner/repository@main
openclaw skills list --verbose
openclaw skills check
Replace the example owner, repository, and ref with the source you reviewed. Prefer a release tag or exact commit when the repository supports it.
Review workflow
What to check before installing a GitHub skill
- 1Read SKILL.md completely.
Confirm the stated purpose, activation conditions, commands, tools, files, and network services the skill expects.
- 2Inspect supporting code and dependencies.
A concise SKILL.md can still call scripts or binaries. Review every executable path and install instruction.
- 3Check repository provenance.
Look at the owner, release history, recent commits, issues, license, and whether the documentation points back to the same repository.
- 4Install with the narrowest scope.
Use the active workspace unless the skill genuinely needs to be available to every local agent.
GitHub skills versus ClawHub skills
| Source | Best for | Update behavior |
|---|---|---|
| ClawHub | Discovery, publisher identity, version metadata, scans, and install hints | openclaw skills update tracks the registry install. |
| GitHub | Reviewing source directly or installing an unpublished repository | Reinstall the Git source when you intentionally want a newer revision. |
| Local directory | Developing or testing a skill on the same machine | You control the local files directly. |