Description: Complete workflow for publishing OpenClaw skills to ClawHub - includes authentication troubleshooting, bot detection workarounds, and the mother skill philosophy.
Status: ✅ PRODUCTION READY (Version 1.0.0)
```bash
npm install -g clawhub
```
# Get token from ClawHub settings (format: clh_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
# Then use the CORRECT authentication method (discovered through trial and error):
clawhub login --token "YOUR_TOKEN_HERE" --no-browser
# Verify authentication:
clawhub whoami
# Should show: ✔ your-username
# WRONG METHODS WE TRIED:
# ❌ export CLAWHUB_TOKEN="token" (doesn't work)
# ❌ echo "token" > ~/.clawhub/token (doesn't work)
# ✅ clawhub login --token "token" --no-browser (CORRECT)
# 1. Create skill directory structure
your-skill/
├── SKILL.md
├── references/ (optional)
├── templates/ (optional)
├── scripts/ (optional)
└── assets/ (optional)
# 2. Validate skill structure
./scripts/validate.sh
# 3. Check for personal information (critical for community sharing)
grep -i "C:\\\\\\\\\|/home/\|password\|token\|secret" SKILL.md || echo "Clean"
# IMPORTANT: Version must be valid semver (2.2.0 not 2.2)
clawhub publish /path/to/your-skill \
--slug "your-unique-slug" \
--name "Skill Display Name" \
--version "1.0.0" \
--changelog "Initial release"
# Slug rules:
# - Lowercase, hyphens only
# - Must be globally unique on ClawHub
# - If taken, append "-v2" or "-backup"
# Skill undergoes security scan (takes a few minutes)
clawhub inspect your-slug
# Once scan completes, skill is available at:
# https://clawhub.ai/s/YOUR_USERNAME/your-slug
Symptoms: "We're verifying your browser" page blocks authentication
Solution:
clawhub login --token --no-browser)Symptoms: "Not logged in" despite having token
Solution: Use exact command: clawhub login --token TOKEN --no-browser
Symptoms: "--version must be valid semver" error
Solution: Use proper semver: "1.0.0", "2.2.0" (not "2.2")
Symptoms: "Only the owner can publish updates"
Solution: Check slug availability, use unique slug
clawhub whoami
# Expected: ✔ username
# Create validation script in your skill:
cat > scripts/validate.sh << 'EOF'
#!/bin/bash
echo "=== Skill Validation ==="
[ -f "SKILL.md" ] && echo "✅ SKILL.md exists" || echo "❌ SKILL.md missing"
EOF
chmod +x scripts/validate.sh
# No dry-run option available, so publish small test skill first
If you need browser authentication (for token generation):
export BROWSERBASE_CAMO_FOX=true
export BROWSERBASE_PROXY_TYPE=residential
A mother skill is:
# Check CLI version
clawhub -V
# Check authentication methods
clawhub auth --help
# Get token help
clawhub login --help
# List your published skills
# Visit: https://clawhub.ai/u/YOUR_USERNAME
clawhub-publish-mother-skill/
├── SKILL.md # Main documentation
├── scripts/
│ ├── validate.sh # Validation script
│ └── test-publish.sh # Test publishing
└── references/
├── checklist.md # Publishing checklist
└── camo-fox.md # Bot detection guide
This skill documents approaches discovered through trial and error. If you find better methods, update and share!
HELL YEAH, ClawHub publishing mastered! 🎯
Based on real discovery: clawhub login --token TOKEN --no-browser
British dry humour + canine personas optional but recommended
共 1 个版本