Skip to content

Add ClawHub publish workflow - #7

Merged
michaelmagan merged 6 commits into
mainfrom
add-clawhub-publish-workflow
Aug 23, 2026
Merged

Add ClawHub publish workflow#7
michaelmagan merged 6 commits into
mainfrom
add-clawhub-publish-workflow

Conversation

@michaelmagan

Copy link
Copy Markdown
Contributor

Keeps the clawhub.ai charming-cli skill listing in sync with skills/charming-cli/SKILL.md, mirroring the pattern from #6 (Homebrew).

Uses ClawHub's own reusable skill-publish.yml workflow rather than hand-rolling the CLI call:

  • Dry-run on PRs touching skills/**
  • Real publish on GitHub Release (and manual workflow_dispatch)
  • Publish is idempotent — it fingerprints the skill folder and no-ops if unchanged, so it's safe to run on every release even when the skill itself didn't change

Skills don't support OIDC/trusted publishing yet (the reusable workflow itself errors on that path), so this uses the CLAWHUB_TOKEN secret already set on this repo.

Requires: CLAWHUB_TOKEN secret (done) and the charming-cli slug already claimed under the tambo-labs owner via a manual first publish (done).

Keeps the clawhub.ai charming-cli skill listing in sync with
skills/charming-cli/SKILL.md using ClawHub's own reusable
skill-publish workflow. Dry-runs on PRs touching skills/**, publishes
for real on GitHub Release.
metadata.openclaw.requires.bins only checks presence; it never
installed anything. Adds an install entry so OpenClaw can install
the CLI via npm when it's missing.
Reusable-workflow job permissions can't exceed what the caller
grants; skill-publish.yml requests id-token: write for its own
source-verification step, which the caller wasn't providing.
Org policy requires every action pinned to a full commit SHA.
ClawHub's own skill-publish.yml reusable workflow references
actions/checkout and actions/upload-artifact by tag internally,
which fails that check and blocks the run before any job starts.
Hand-rolling the checkout/setup steps (already SHA-pinned, matching
this repo's other workflows) and calling clawhub CLI via npx avoids
depending on their workflow's own pinning.
sync is a top-level command, not under the skill subcommand group;
skill's own subcommands are publish/verify/tag/rename/merge. Default
scan already finds skills/charming-cli with no --root override
needed, confirmed with a local dry run.
The ClawHub org got created as @charming, not @tambo-labs — the
skill was manually published there as slug 'charming'. clawhub sync
derives the slug from the folder name, so skills/charming-cli/ is
renamed to skills/charming/ (and the SKILL.md name field to match)
to keep automated syncs pointed at the same listing instead of
creating an orphaned charming-cli one.
@michaelmagan
michaelmagan merged commit a000a8e into main Aug 23, 2026
3 checks passed
@michaelmagan
michaelmagan deleted the add-clawhub-publish-workflow branch August 23, 2026 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant