Skill Publisher

End-to-end workflow for publishing an AgentSkill directory to ClawHub.

Pre-publish Checklist

☐ 1. Content Internationalization

• SKILL.md: use English (Agent can handle any language, but English description/tags improve search matching on ClawHub)
• Remove hardcoded local paths, usernames (e.g., /mnt/e/Users/...)
• Replace user-specific config with generic placeholders or discovery methods

☐ 2. Meta Verification

cat <skill-dir>/_meta.json

Check:

• name matches the --slug you'll publish with
• version is updated (semver)
• tags are accurate (affects ClawHub search)
• description is concise (this is what agents match against)

☐ 3. Slug Conflict Check

clawhub inspect <slug>

• Returns skill info → slug is taken
  • Yours → publish will overwrite/upgrade
  • Someone else's → rename slug, e.g. my-skill → my-skill-v2
• Errors "not found" → slug is available

☐ 4. Login

clawhub whoami

If not logged in:

clawhub login

Opens a browser for authorization.

Publish

Prerequisites: clawhub CLI must be installed (npm i -g clawhub)

clawhub publish ~/.openclaw/skills/<skill> \
  --slug <slug> \
  --name "Display Name" \
  --version x.y.z \
  --tags "tag1,tag2" \
  --changelog "Release notes"

Parameters

Post-publish Verification

# New versions may be hidden by security scan, wait ~60s
sleep 60

# Check published info
clawhub inspect <slug>

# Confirm search
clawhub search <slug>

Common Errors