Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Make your skills easy to understand and impossible to ignore
Make your skills easy to understand and impossible to ignore
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Professional documentation and publishing for Clawdbot skills Generate adoption-optimized READMEs and publish to GitHub + ClawdHub with one command.
bash jq (for JSON parsing) gh CLI (GitHub operations) clawdhub CLI (publishing) git
Automates the complete publishing workflow:
Reads your SKILL.md to understand what the skill does Generates 3 one-liner options using proven patterns Creates a README following GitHub best practices: Problem/solution upfront Inverted pyramid structure Emoji headers for scannability Bold outcomes Under 15% text highlighting Updates SKILL.md frontmatter with chosen description
Creates GitHub repository (if doesn't exist) Pushes code to GitHub Publishes to ClawdHub with auto-detected version
clawdhub install skill-publisher
cd ~/clawd/skills/your-skill skill-publisher The script will: Show 3 one-liner options (choose or write your own) Generate README preview Ask for approval Publish to GitHub + ClawdHub
The tool generates options using three proven patterns:
Keep [thing] [desired state] [timeframe] Example: "Keep your Claude access token fresh 24/7"
[Do thing] without [pain point] Example: "Build cross-device tools without hardcoding paths"
Automatically [action] [thing] [when] Example: "Automatically refresh tokens before they expire"
Follows the framework from GitHub's documentation best practices:
Title + subtitle The problem: (1 sentence) This tool: (1 sentence) ๐ Requirements โก What It Does (outcome first, then features) ๐ Installation ๐ง How It Works (result first, then process)
Configuration options Troubleshooting For Developers Implementation details
Reads SKILL.md frontmatter (if exists) Extracts key information: name, description, requirements Parses scripts for dependencies
Analyzes your SKILL.md description and generates 3 options: Pattern A: Continuous benefit format Pattern B: Pain point elimination format Pattern C: Automation format Shows you all 3, lets you choose or write custom.
Uses the template from ~/clawd/templates/README-template.md: Fills in title, problem, solution Extracts requirements from SKILL.md Generates "What It Does" from description Creates installation steps Builds "How It Works" with examples
Checks for gh CLI (guides setup if missing) Reads VERSION file for version number Creates GitHub repo (using gh repo create) Commits and pushes all files Publishes to ClawdHub with clawdhub publish
your-skill/ โโโ SKILL.md # Required: skill description โโโ VERSION # Required: version number (e.g., "1.0.0") โโโ scripts/ # Optional: your scripts โ โโโ main.sh โโโ README.md # Generated by this tool โโโ .gitignore # Optional
No configuration needed. The tool auto-detects everything from: SKILL.md (name, description, requirements) VERSION (version number) scripts/ (code examples, dependencies)
Install GitHub CLI: brew install gh gh auth login
Create a minimal SKILL.md: --- name: your-skill description: Brief description of what it does --- # your-skill More details about your skill here.
Create a VERSION file: echo "1.0.0" > VERSION
GitHub documentation best practices: https://docs.github.com/en/contributing/writing-for-github-docs/best-practices-for-github-docs README template: ~/clawd/templates/README-template.md One-liner formulas: See "One-Liner Generation Patterns" section above
MIT
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.