Skill Publisher
English | 中文
Publish your Claude Code Skills to GitHub with one command. Automated privacy checks, bilingual documentation, and plugin marketplace support.
The Problem
Publishing a Claude Code Skill involves many tedious steps:
| Task | Manual Effort |
|---|
| Privacy check | Read every file, search for tokens/keys |
| Project structure | Create directories, copy files |
| plugin.json | Write config manually |
| README | Write documentation |
| Bilingual docs | Translate everything |
| Git setup | Init, commit, create repo, push |
Total: 30-60 minutes per skill
Hidden Risks
- Accidentally commit API keys or OAuth tokens
- Expose personal file paths (
/Users/yourname/)
- Miss sensitive data in config files
The Solution
This skill automates the entire publishing workflow:
Source Skill
↓ Privacy Scan
↓ Collect User Info
↓ Generate Project Structure
↓ Create Bilingual Docs
↓ Git Init & Push
Published on GitHub
Key Features
- Privacy Scanner: Detect API keys, tokens, personal paths before publishing
- Dual Installation: Support both Git Clone and Plugin Marketplace
- Bilingual Docs: Auto-generate English + Chinese README
- Templates: Consistent project structure every time
- One Command: From source to GitHub in minutes
Requirements
| Requirement | Details |
|---|
| Claude Code | claude.ai/code |
| Python 3.9+ | For privacy check script |
| gh CLI | GitHub command line (brew install gh) |
| Git | Version control |
Installation
Method 1: Git Clone (Recommended)
git clone https://github.com/wshuyi/skill-publisher-skill.git
cp -r skill-publisher-skill/skills/skill-publisher ~/.claude/skills/
Method 2: Plugin Marketplace
/plugin marketplace add wshuyi/skill-publisher-skill
/plugin install skill-publisher@wshuyi/skill-publisher-skill
Usage
Natural Language
Help me publish my-skill to GitHub
发布 ~/.claude/skills/my-skill 到 GitHub
Skill Command
/skill-publisher ~/.claude/skills/my-skill
Workflow
[1/7] Locate skill source
→ Find SKILL.md and related files
[2/7] Privacy scan (CRITICAL)
→ Check for API keys, tokens, personal paths
→ Block if high-severity issues found
[3/7] Collect user info
→ GitHub username
→ License preference
→ Project description
[4/7] Create project structure
→ .claude-plugin/plugin.json
→ skills/{name}/
→ docs/
[5/7] Generate documentation
→ README.md (English)
→ README_CN.md (Chinese)
→ LICENSE
[6/7] Git init & push
→ Initialize repository
→ Create GitHub repo via gh CLI
→ Push to remote
[7/7] Output install instructions
→ Git Clone method
→ Plugin Marketplace method
Privacy Scanner
The built-in scanner checks for:
| Category | Examples | Severity |
|---|
| API Keys | api_key=xxx, AKIA... | 🔴 High |
| OAuth Tokens | oauth_token: xxx | 🔴 High |
| Private Keys | -----BEGIN PRIVATE KEY----- | 🔴 High |
| GitHub Tokens | ghp_xxx, github_pat_xxx | 🔴 High |
| Personal Paths | /Users/yourname/ | 🟡 Medium |
| Email Addresses | user@example.com | 🟢 Low |
Run Manually
python ~/.claude/skills/skill-publisher/scripts/check_privacy.py /path/to/skill
Templates Included
| Template | Purpose |
|---|
plugin.json.template | Plugin configuration |
README.md.template | English documentation |
README_CN.md.template | Chinese documentation |
LICENSE-MIT.template | MIT license |
gitignore.template | Git ignore rules |
Project Structure
skill-publisher-skill/
├── .claude-plugin/
│ └── plugin.json
├── skills/
│ └── skill-publisher/
│ ├── SKILL.md # Core instructions
│ ├── scripts/
│ │ └── check_privacy.py # Privacy scanner
│ └── templates/
│ ├── plugin.json.template
│ ├── README.md.template
│ ├── README_CN.md.template
│ ├── LICENSE-MIT.template
│ └── gitignore.template
├── README.md
├── README_CN.md
└── LICENSE
Lessons Learned
This skill was born from real experience publishing skills:
- Always scan for secrets - Once exposed a GitHub token by reading a config file
- Personal paths leak usernames -
/Users/wsy/ reveals identity
- Bilingual docs matter - Expand your audience significantly
- Templates save time - Consistent structure across all skills
- gh CLI is essential - Faster than web UI for repo creation
FAQ
Q: What if privacy scan finds issues?
A: High severity issues block publishing. Fix them first, then retry.