Three small fixes: `skill_prefix=true` now survives updates when gbrain is installed, the OpenClaw docs stop sending people to stale ClawHub skills, and `gstack-issue-links` no longer reads other repositories' issue numbers as gstack issues. Why: each one misleads users or /ship today (wrong skill names after every update, April 2026 skill builds, wrong `Refs #N` lines in PR bodies). Nothing to do as a reader. Thanks @fliaron (#4413) and @exGeni (#4421) for the detailed reports. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
1.2 KiB
Publishing native OpenClaw skills to ClawHub
Moved verbatim from CLAUDE.md (token-load reduction).
Status: gstack's user docs no longer send anyone to ClawHub (#4421). Native
registration (./setup --host openclaw) gives OpenClaw's agent the current
/office-hours, /plan-ceo-review and /retro, and the gstack skills were removed
from ClawHub on 2026-11-17.
Workflow
Native OpenClaw skills live in openclaw/skills/gstack-openclaw-*/SKILL.md. These are
hand-crafted methodology skills (not generated by the pipeline) published to ClawHub
so any OpenClaw user can install them.
Publishing: The command is clawhub publish (NOT clawhub skill publish):
clawhub publish openclaw/skills/gstack-openclaw-office-hours \
--slug gstack-openclaw-office-hours --name "gstack Office Hours" \
--version 1.0.0 --changelog "description of changes"
Repeat for each skill: gstack-openclaw-ceo-review,
gstack-openclaw-retro. Bump --version on each update.
Auth: clawhub login (opens browser for GitHub auth). clawhub whoami to verify.
Updating: Same clawhub publish command with a higher --version and --changelog.
Verification: clawhub search gstack to confirm they're live.