skill-publisher

# Skill Publisher

End-to-end publishing workflow for agent skills. Covers GitHub, ClawdHub, and skills.sh — from pre-flight checks to installation verification.

## Language

Respond in the same language the user used to invoke this skill. Fall back to English if no language signal is found.

## Prerequisites

```bash
command -v gh >/dev/null || echo "CRITICAL: gh (GitHub CLI) not found — install with: brew install gh"
command -v git >/dev/null || echo "CRITICAL: git not found"
```

Optional (for ClawdHub publishing):
```bash
npx clawhub --help >/dev/null 2>&1 || echo "INFO: clawhub CLI not installed — needed for ClawdHub publishing"
```

## Workflow Overview

The full publishing pipeline has 6 phases:

```
1. Pre-flight Check    → Validate skill structure and content
2. GitHub Publish      → Create repo, push, add topics
3. ClawdHub Publish    → Publish to ClawdHub registry
4. skills.sh Submit    → Submit index request via GitHub issue
5. Install Verify      → Test all installation methods
6. Post-publish        → Summary with all links and install commands
```

Run phases sequentially. If the user only wants a specific phase (e.g., "just submit to skills.sh"), skip to that phase.

## Phase 1: Pre-flight Check

Validate the skill directory before publishing. Check ALL of the following:

### 1.1 Required Files

```bash
SKILL_DIR="<path-to-skill>"  # Ask user or infer from context

# Required
[ -f "$SKILL_DIR/SKILL.md" ] || echo "FAIL: SKILL.md missing"
[ -f "$SKILL_DIR/LICENSE" ]  || echo "FAIL: LICENSE missing"
[ -f "$SKILL_DIR/README.md" ] || echo "FAIL: README.md missing"
```

### 1.2 SKILL.md Frontmatter

Read `SKILL.md` and verify YAML frontmatter contains:
- `name` — required, should be kebab-case
- `description` — required, should be descriptive (used by search engines and skill discovery)
- `version` — required, valid semver

Optional but recommended:
- `metadata.openclaw.emoji`
- `metadata.openclaw.homepage`
- `metadata.openclaw.os`
- `metadata.openclaw.re...

# skill-publisher

[English](README.md) | [中文](README.zh-CN.md)

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
[![Platform: macOS | Linux | Windows (WSL)](https://img.shields.io/badge/Platform-macOS%20%7C%20Linux%20%7C%20Windows%20(WSL)-lightgrey.svg)](https://github.com/bryant24hao/skill-publisher)

> One command to publish your agent skill to GitHub, ClawdHub, and skills.sh.

A Claude Code skill that automates the entire skill publishing pipeline — from pre-flight validation to installation verification across all three platforms.

## Why

Publishing a skill should be simple, but the reality is:

- **GitHub** needs a repo, topics for discoverability, and correct badge links
- **ClawdHub** has a CLI with a known bug (`acceptLicenseTerms`), slug conflicts, and no auto-retry
- **skills.sh** doesn't auto-index — you must submit a GitHub issue to `vercel-labs/skills`
- Install commands in README must match the final repo name on all platforms
- Bilingual READMEs need consistent content and working language switchers

Miss one step and your skill is either unfindable or uninstallable.

**skill-publisher handles the full pipeline in one session.**

## What It Does

```
1. Pre-flight Check    → Validate SKILL.md, README, LICENSE, secrets scan
2. GitHub Publish      → Create repo, push, add discovery topics
3. ClawdHub Publish    → Login, check slug, publish (with bug workaround)
4. skills.sh Submit    → Auto-create index request issue
5. Install Verify      → Test all 3 install methods end-to-end
6. Post-publish        → Summary with all links and commands
```

## Quick Install

```bash
npx skills add bryant24hao/skill-publisher -g -y
```

**Manual**:

```bash
git clone https://github.com/bryant24hao/skill-publisher.git ~/.claude/skills/skill-publisher
```

## Usage

```
/skill-publisher
publish my skill
上架技能
发布 skill 到 clawhub 和 skills.sh
```

## Prerequisites

- **[gh](https://cli.github.com/)** — GitHub CLI (for repo creation a...