skill-publish

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Package a agent skill into a complete GitHub repository ready for distribution via skills.sh. Generates README, LICENSE, plugin.json, marketplace.json, .gitignore, and the proper directory structure. Optionally initializes a git repo and creates a GitHub repository. This skill should be used when publishing a skill, packaging a skill for distribution, preparing a skill repo, or when the user says 'publish skill', 'package skill', 'release skill', '发布技能', '打包 skill'.

2installs

Sourcepsylch/better-skills

Added on2026-02-22

NPX Install

npx skill4agent add psylch/better-skills skill-publish

SKILL.md Content

View Translation Comparison →

Skill Publish

Package a agent skill into a complete, distributable GitHub repository. Generates all the surrounding files (README, LICENSE, plugin.json, marketplace.json) and optionally creates the GitHub repo.

How It Works

Identify the skill to publish
Optionally review first with skill-review
Collect publishing metadata through dialogue
Generate the repository structure with
```
publish.py
```
Optionally initialize git and create GitHub repo

Dialogue Flow

Step 1: Identify the Skill

Ask the user for the skill directory path. Auto-detect if the current working directory contains a SKILL.md. Accept absolute or relative paths.

Step 2: Pre-Publish Validation

If the

skill-review

skill is available (check if

{SKILL_DIR}/../skill-review/scripts/validate.py

exists), suggest running validation first:

bash

python3 {SKILL_DIR}/../skill-review/scripts/validate.py run --path <skill-path>

If there are failures, recommend fixing them before proceeding. Warnings are acceptable.

If skill-review is not available, do a quick manual check: verify SKILL.md exists and has valid frontmatter with name and description.

Step 3: Collect Metadata

Use AskUserQuestion to gather:

GitHub owner/org — Default: try to infer from
```
git config user.name
```
or
```
gh api user -q .login
```
. Ask user to confirm or change.
Repository name — Default:
```
<skill-name>-skill
```
(e.g.,
```
cors-audit-skill
```
). Suggest the convention but let user override.
Version — Default:
```
1.0.0
```
. Use semver.
License — Default: MIT. Options: MIT, Apache-2.0, GPL-3.0.
Output directory — Where to create the repo. Default: parent directory of the skill.

Step 4: Generate Repository

bash

python3 {SKILL_DIR}/scripts/publish.py generate \
    --skill-path <path> \
    --owner <owner> \
    --repo <repo-name> \
    --version <version> \
    [--license mit|apache2|gpl3] \
    [--output <dir>] \
    [--force]

Where

{SKILL_DIR}

is the directory containing this SKILL.md file.

The script outputs JSON to stdout:

json

{
  "status": "ok",
  "output_dir": "/path/to/output",
  "repo": "owner/repo-name",
  "created": [".claude-plugin/plugin.json", "README.md", "LICENSE", ...],
  "hint": "Repository files generated. Next: git init or gh repo create."
}

Step 5: Post-Generation

Present what was generated, then ask the user what to do next:

Option A: Initialize git repo

bash

cd <output-dir>
git init
git add .
git commit -m "Initial commit"

Option B: Create GitHub repo and push

bash

cd <output-dir>
git init
git add .
git commit -m "Initial commit"
gh repo create <owner>/<repo> --public --source . --push

Option C: Done — User will handle git themselves.

After creation, remind the user:

Edit README.md and README.zh.md to polish auto-generated content
Register on skills.sh if they want public discoverability
Test installation:
```
npx skills add ./ -g -y
```

Generated Repository Structure

<repo-name>/
├── .claude-plugin/
│   ├── plugin.json
│   └── marketplace.json
├── skills/
│   └── <skill-name>/        # Copied from source
│       ├── SKILL.md
│       ├── scripts/
│       └── references/
├── README.md
├── README.zh.md
├── LICENSE
└── .gitignore

Distribution Guide Reference

For details about skills.sh registry, versioning strategy, and publishing conventions, read

references/distribution_guide.md

.

skill-publish

NPX Install

Tags

SKILL.md Content

Skill Publish

How It Works

Dialogue Flow

Step 1: Identify the Skill

Step 2: Pre-Publish Validation

Step 3: Collect Metadata

Step 4: Generate Repository

Step 5: Post-Generation

Generated Repository Structure

Distribution Guide Reference