Skill Release Pipeline

Automate packaging, pushing to GitHub, and publishing OpenClaw skills to ClawHub, managing versions and sync across platforms.

Security Scan

The skill's files, instructions, and required actions are consistent with a publish/push pipeline for OpenClaw skills and do not request unrelated credentials or install actions.

Purpose & Capability

Name/description match the included scripts and SKILL.md: the bundle validates a skill folder, commits/creates a git repo, pushes to GitHub, and publishes to ClawHub. All required actions are coherent with a release pipeline; there are no unrelated credentials or unexpected external services referenced.

Instruction Scope

SKILL.md instructs running local scripts and standard CLIs (git, gh, npx clawhub) against the target skill folder. Runtime instructions only read and operate on the provided skill folder (validate, list, commit, push, publish). They do not instruct reading arbitrary system files, environment variables, or sending data to unknown endpoints beyond GitHub and ClawHub.

Install Mechanism

No install spec is present; this is instruction-only with helper scripts included. The scripts are plain shell scripts (no downloads or archive extraction) and run locally, so install risk is low.

Credentials

The skill requires no declared env vars or secrets. It expects the user to be authenticated to GitHub (gh/git) and ClawHub (npx clawhub), which is appropriate for pushing and publishing. No extraneous credentials or config paths are requested.

Persistence & Privilege

The skill is not always-enabled and does not attempt to modify system-wide agent settings or other skills. It only performs repo-level git operations and invokes npx clawhub; no persistent privileges are requested.

Assessment

This skill appears to do exactly what it says: validate a skill folder, push it to GitHub, and publish to ClawHub. Before running it, confirm you trust the repository/folder being published and review the scripts. Practical cautions: (1) the scripts will initialize a git repo, set or overwrite the 'origin' remote URL, commit, and push to the main/master branch — ensure you intend that and have the correct repo ownership/permissions; (2) authenticate gh and clawhub CLIs beforehand (the scripts check auth); (3) do not run these scripts from a folder that contains secrets or credentials you don't want pushed to a remote; and (4) if you need more conservative behavior, run validate.sh first and run push/publish steps interactively rather than the full pipeline.

Skill Publisher

Automate the full lifecycle of publishing OpenClaw skills: package → GitHub → ClawHub.

Prerequisites

• gh CLI authenticated (gh auth status)
• npx clawhub CLI authenticated (npx clawhub whoami)
• A skill folder with a valid SKILL.md

Quick Start

Full Pipeline (package + GitHub + ClawHub)

# From the skill directory
scripts/publish.sh /path/to/skill-folder --repo owner/repo-name --version 1.0.0

Individual Steps

# 1. Validate & package only
scripts/validate.sh /path/to/skill-folder

# 2. Push to GitHub
scripts/push-github.sh /path/to/skill-folder --repo owner/repo-name

# 3. Publish to ClawHub
npx clawhub publish /path/to/skill-folder --version 1.0.0 --slug skill-name

Workflow

Step 1: Prepare the Skill Folder

Ensure the skill folder contains:

skill-name/
├── SKILL.md          (required — YAML frontmatter + markdown body)
├── LICENSE           (recommended — MIT)
├── examples/         (optional — usage examples)
├── scripts/          (optional — helper scripts)
├── references/       (optional — reference docs)
└── assets/           (optional — templates, images, fonts)

SKILL.md frontmatter must include:

---
name: skill-name
description: Clear description of what the skill does and when to activate it
---

Step 2: Push to GitHub

cd /path/to/skill-folder

# Init if needed
git init
git add -A
git commit -m "feat: initial release of skill-name"

# Create repo and push
gh repo create owner/repo-name --public --source=. --push

If the repo already exists:

git remote add origin https://github.com/owner/repo-name.git 2>/dev/null || true
git push -u origin main

Step 3: Publish to ClawHub

# Login if needed (opens browser)
npx clawhub login

# Publish with version
npx clawhub publish /path/to/skill-folder \
  --version 1.0.0 \
  --slug skill-name \
  --name "Display Name" \
  --tags "tag1,tag2"

# Verify
npx clawhub inspect skill-name

Note: ClawHub runs a security scan after publishing. The skill becomes searchable once the scan passes (usually within a few minutes).

Common Tasks

Update an Existing Skill

# 1. Make changes to the skill folder

# 2. Push to GitHub
cd /path/to/skill-folder
git add -A && git commit -m "fix: description of changes"
git push

# 3. Publish new version to ClawHub
npx clawhub publish /path/to/skill-folder --version 1.1.0

Fork an Existing Skill

npx clawhub publish /path/to/skill-folder \
  --version 1.0.0 \
  --slug my-fork-name \
  --fork-of original-skill@1.0.0

Check Publish Status

npx clawhub inspect skill-name
npx clawhub search skill-name

Troubleshooting

Error	Fix
--version must be valid semver	Add --version x.y.z flag
Skill is hidden while security scan is pending	Wait a few minutes, then retry inspect
Not logged in	Run npx clawhub login
gh: not authenticated	Run gh auth login
fatal: remote origin already exists	Safe to ignore, or use git remote set-url

Naming Conventions

• Slug: lowercase, hyphens only (e.g., figma-plugin-writer)
• Repo: match the slug (e.g., openclaw-figma-plugin-writer)
• Version: semver (e.g., 1.0.0, 1.2.3)