How to Publish a Skill to ClawHub

# Pre-publish checklist:

# 1. Test thoroughly across different scenarios
# 2. Add comprehensive error handling
# 3. Write clear skill.md documentation
# 4. Add inline code comments
# 5. Create a detailed README.md
# 6. Remove debug logging and test code
# 7. Verify all permissions are necessary and justified

# Create README.md:
cat > ~/.openclaw/skills/my-skill/README.md << 'EOF'
# My Skill Name

One-sentence description.

## What It Does
Clear explanation of functionality.

## How to Use
Step-by-step usage instructions.

## Examples
Real-world examples with screenshots.

## Requirements
- Dependencies
- API keys needed
- System requirements

## Troubleshooting
Common issues and solutions.
EOF

# 1. Go to https://clawhub.ai
# 2. Click "Sign Up" or "Publish a Skill"
# 3. Choose "Developer Account"
# 4. Complete profile:
#    - Display name
#    - Bio
#    - Website (optional)
#    - GitHub (recommended for credibility)
# 5. Verify your email address

# Create clawhub.json in your skill directory:
cat > ~/.openclaw/skills/my-skill/clawhub.json << 'EOF'
{
  "name": "My Skill Name",
  "tagline": "One-sentence value proposition (max 80 chars)",
  "description": "Detailed description of what your skill does, who it's for, and why they should use it. 2-3 paragraphs.",
  "category": "productivity",
  "tags": ["automation", "email", "scheduling"],
  "version": "1.0.0",
  "license": "MIT",
  "pricing": "free",
  "support_url": "https://github.com/yourname/your-skill/issues",
  "homepage": "https://github.com/yourname/your-skill"
}
EOF

# Categories: productivity, communication, development, data, creative, utility

# Create screenshots directory:
mkdir -p ~/.openclaw/skills/my-skill/screenshots

# Add 3-5 high-quality screenshots showing:
# 1. Main use case (hero screenshot)
# 2. Configuration/setup screen
# 3. Example output
# 4. Error handling (optional but good)

# Screenshot requirements:
# - 1920x1080 or 1280x720 resolution
# - PNG format
# - Real data (not Lorem Ipsum)
# - Clean UI, no clutter

# Demo video (optional but highly recommended):
# - 30-90 seconds
# - Show real usage, not a static demo
# - Upload to YouTube or Vimeo
# - Add URL to clawhub.json

# 1. Package your skill:
cd ~/.openclaw/skills
tar -czf my-skill.tar.gz my-skill/

# 2. Go to ClawHub dashboard → "Publish New Skill"
# 3. Upload my-skill.tar.gz
# 4. Fill in the publishing form:
#    - Metadata (auto-filled from clawhub.json)
#    - Upload screenshots
#    - Add demo video URL
#    - Select category and tags
#    - Write permission justification
# 5. Click "Submit for Review"

# Review typically takes 2-5 business days

# If your submission is rejected, you'll receive feedback:

# Common rejection reasons:
# 1. Insufficient documentation
# 2. Unjustified permissions
# 3. Missing error handling
# 4. Poor code quality
# 5. Security vulnerabilities
# 6. Misleading description

# To resubmit:
# 1. Address ALL feedback points
# 2. Update version number
# 3. Add CHANGELOG.md documenting fixes
# 4. Repackage and resubmit

# Check submission status:
# ClawHub Dashboard → My Skills → View Status

# After approval, your skill is live!

# Managing updates:
# 1. Fix bugs and add features locally
# 2. Update version in skill.md and clawhub.json
# 3. Add entry to CHANGELOG.md
# 4. Resubmit (updates have faster review)

# Handling user feedback:
# - Monitor ClawHub reviews and ratings
# - Respond to support requests (via support_url)
# - Track feature requests
# - Release updates regularly

# Best practices:
# - Semantic versioning (1.0.0 → 1.0.1 for fixes, 1.1.0 for features)
# - Maintain backward compatibility
# - Deprecate features gradually, don't break users