End-to-end workflow for publishing an AgentSkill directory to ClawHub.
/mnt/e/Users/...)bash
cat <skill-dir>/_meta.json
Check:
name matches the --slug you'll publish withversion is updated (semver)tags are accurate (affects ClawHub search)description is concise (this is what agents match against)bash
clawhub inspect <slug>
publish will overwrite/upgrademy-skill → my-skill-v2bash
clawhub whoami
If not logged in:
bash
clawhub login
Opens a browser for authorization.
Prerequisites: clawhub CLI must be installed ( npm i -g clawhub)
bash
clawhub publish ~/.openclaw/skills/<skill> \
--slug <slug> \
--name "Display Name" \
--version x.y.z \
--tags "tag1,tag2" \
--changelog "Release notes"
ParamDescriptionExamplepathSkill directory~/.openclaw/skills/my-skill``--slugUnique identifiermy-skill``--nameDisplay nameMy Skill``--versionSemver version1.0.0``--tagsComma-separated search tagslogseq,notes``--changelogRelease notesInitial release
bash
# New versions may be hidden by security scan, wait ~60s
sleep 60
# Check published info
clawhub inspect <slug>
# Confirm search
clawhub search <slug>
ErrorCauseFixNot logged inNot authenticatedclawhub login``Slug is already takenSlug occupied by another skillRename slug or check ownershipSkill is hiddenSecurity scan in progressWait 60s and retryCTX_MAX_EXCEEDEDContent too largeTrim SKILL.md, move details to references/