Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create, validate, security-scan, and publish skills to ClawHub. Use when asked to "make a skill", "publish a skill", "create a new skill", "scaffold a skill"...
Create, validate, security-scan, and publish skills to ClawHub. Use when asked to "make a skill", "publish a skill", "create a new skill", "scaffold a skill"...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Build and publish skills to ClawHub in one flow.
bash {baseDir}/scripts/scaffold.sh <skill-name> [--dir <output-dir>] Creates a new skill folder with SKILL.md template and scripts/ directory. Default output: ./skills/<skill-name>
Edit the generated SKILL.md: Set name and description in frontmatter (description is critical for triggering) Write clear instructions in the body Add scripts/ for executable code, references/ for docs, assets/ for templates
bash {baseDir}/scripts/validate.sh <skill-folder> Checks: Required files exist (SKILL.md) Frontmatter has name and description Naming conventions (lowercase, hyphens) No forbidden files (README.md, CHANGELOG.md, etc.)
bash {baseDir}/scripts/security-scan.sh <skill-folder> Scans for red flags: Remote code execution / eval patterns Data exfiltration (curl to unknown hosts) Environment variable harvesting Prompt injection in markdown files Suspicious file permissions
bash {baseDir}/scripts/publish.sh <skill-folder> --slug <name> --version <x.y.z> Pushes to ClawHub. Requires clawhub login first.
bash {baseDir}/scripts/scaffold.sh my-skill && \ # edit skills/my-skill/SKILL.md ... && \ bash {baseDir}/scripts/validate.sh skills/my-skill && \ bash {baseDir}/scripts/security-scan.sh skills/my-skill && \ bash {baseDir}/scripts/publish.sh skills/my-skill --slug my-skill --version 1.0.0
my-skill/ โโโ SKILL.md โ Required. Frontmatter (name, description) + instructions. โโโ scripts/ โ Optional. Executable code (bash, python, etc.) โโโ references/ โ Optional. Docs loaded on-demand into context. โโโ assets/ โ Optional. Templates, images, files used in output. Key principles: Be concise. Context window is shared real estate. Description in frontmatter is the trigger โ make it comprehensive. Progressive disclosure: SKILL.md body only loads when triggered. Scripts > inline code for deterministic, repeated operations.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.