forked from Selig/openclaw-skill
6 custom skills (assign-task, dispatch-webhook, daily-briefing, task-capture, qmd-brain, tts-voice) with technical documentation. Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
# ClawHub Documentation
|
|
|
|
## Overview
|
|
ClawHub functions as a public skill registry for OpenClaw, offering free access to shared, reusable skills. The platform enables users to discover, install, and publish capabilities through a web interface or CLI.
|
|
|
|
## Core Functionality
|
|
A skill comprises a folder with a `SKILL.md` file (plus supporting text files). The registry manages versioned bundles, making them searchable through embeddings-powered discovery rather than keyword-only approaches.
|
|
|
|
## Key Features
|
|
- Semantic search across skill repositories
|
|
- Semantic versioning with changelog tracking
|
|
- Community engagement through stars and comments
|
|
- Moderation systems including reporting mechanisms
|
|
|
|
## Publishing Requirements
|
|
New publishers must maintain GitHub accounts active for at least one week before uploading. This threshold helps mitigate malicious uploads while remaining accessible to legitimate contributors.
|
|
|
|
## Installation
|
|
Users can quickly set up the CLI via npm or pnpm, then search for and install skills using straightforward commands like `clawhub search "calendar"` and `clawhub install <skill-slug>`.
|
|
|
|
## Security Measures
|
|
The platform implements automated protections: skills receiving more than three distinct reports are hidden by default, and moderators can manage content visibility and enforce user restrictions when abuse occurs.
|
|
|
|
## Local Integration
|
|
ClawHub installs skills into `./skills` directories by default, with workspace configurations providing fallback locations. OpenClaw loads these skills in subsequent sessions automatically.
|