wells1137-skill-publisher_skill

This skill automates multi-channel publishing of agent skills, installing CI/CD pipelines and delivering releases to ClaWHub, GitHub, and beyond.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill wells1137-skill-publisher

  • _meta.json295 B
  • SKILL.md3.0 KB

Overview

This skill automates multi-channel publishing for Agent Skills repositories, letting you release new versions to ClaWHub, GitHub, and other platforms with a single setup. It installs a GitHub Actions CI/CD pipeline, helper scripts, and configures required secrets so releases are triggered by tag pushes.

How this skill works

The skill clones your target GitHub repository, copies pre-built workflow and helper script templates into the repo, and uses the GitHub CLI to set repository secrets (CLAWHUB_TOKEN and GH_PAT). It commits and pushes the new files, creating workflows that run on tag pushes, PRs, and for submitting to curated lists. After setup, creating a git tag triggers the publish pipeline.

When to use it

  • You maintain one or more Agent Skills in a GitHub repo and need repeatable release automation.
  • You want to publish skill versions to ClaWHub and update GitHub metadata automatically.
  • You need to add GitHub Actions workflows for quality checks, releases, and list submissions.
  • You want to centralize token management and CI/CD setup across multiple skill repos.

Best practices

  • Ensure GH_PAT has repo and workflow scopes and keep CLAWHUB_TOKEN restricted to necessary permissions.
  • Run the setup in a clean branch, review changes, then merge to main to avoid accidental commits.
  • Use semantic version tags (e.g., v1.2.0) to trigger predictable release pipelines.
  • Store any additional platform credentials as GitHub Actions secrets rather than plain files.
  • Test workflows on a fork or staging repo before enabling them on production repositories.

Example use cases

  • Add a publish pipeline to an existing skills repo so tagging vX.Y.Z publishes to ClaWHub and creates a GitHub Release.
  • Onboard multiple skill repositories by running the setup script to ensure consistent workflows and secrets across projects.
  • Automatically submit new or updated skills to curated awesome-lists via a workflow that opens PRs.
  • Enforce quality gates by adding automated checks on pull requests before a release is created.

FAQ

You need CLAWHUB_TOKEN for ClaWHub API access and a GH_PAT with repo and workflow scopes to set secrets and create releases.

How do I trigger the first release after setup?

Create and push a semantic git tag (for example git tag v1.0.0 && git push origin v1.0.0). The publish workflow runs on tag pushes.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational