Skill Publisher Claw Skill

# Skill Publisher

Prepare a skill for public release. Run through this checklist before publishing any skill to ensure it's reusable, clean, safe, and well-documented.

## When to Use

- Before pushing a skill to a public repo
- Before submitting to ClawdHub
- When reviewing someone else's skill
- Periodic audits of existing published skills

## Quick Checklist

Run through these in order. Each section has detailed guidance below.

```
[ ] 1. STRUCTURE    - Required files present, logical organization
[ ] 2. SECURITY     - No secrets, keys, PII, or sensitive data  
[ ] 3. PORTABILITY  - No hardcoded paths, works on any machine
[ ] 4. QUALITY      - Clean code, no debug artifacts
[ ] 5. DOCS         - README, SKILL.md, examples complete
[ ] 6. TESTING      - Verified it actually works
[ ] 7. GIT          - Clean history, proper .gitignore, good commits
[ ] 8. METADATA     - License, description, keywords
```

---

## 1. Structure Validation

### Required Files
```
skill-name/
├── SKILL.md          # REQUIRED - Entry point, when to use, quick reference
├── README.md         # REQUIRED - For GitHub/humans
└── [content files]   # The actual skill content
```

### SKILL.md Format
Must include:
- **Header**: Name and one-line description
- **When to Use**: Clear triggers for loading this skill
- **Quick Reference**: Most important info at a glance
- **Detailed sections**: As needed

```markdown
# Skill Name

One-line description of what this skill does.

## When to Use
- Trigger condition 1
- Trigger condition 2

## Quick Reference
[Most important info here]

## [Additional Sections]
[Detailed content]
```

### File Organization
- Group related content logically
- Use clear, descriptive filenames
- Keep files focused (single responsibility)
- Consider load order (what gets read first?)

### Anti-patterns
❌ Single massive file with everything  
❌ Cryptic filenames (`data1.md`, `stuff.md`)  
❌ Circular dependencies between files  
❌ Missing SKILL.md entry point  

---...

# skill-publisher-claw-skill

A Claw skill and toolkit for preparing skills for public release.

## Tools

| Script | Description |
|--------|-------------|
| `audit.sh` | Check skill for issues (secrets, paths, quality) |
| `fix.sh` | Auto-fix common issues |
| `scaffold.sh` | Create new skill from templates |
| `publish.sh` | One-command audit → commit → push |
| `analyze.sh` | Size/token analysis and recommendations |
| `validate-links.sh` | Check internal and external links |
| `score.sh` | Quality score (0-100) with grade |
| `changelog.sh` | Generate changelog from commits |

## Quick Start

### Check a skill before publishing
```bash
./audit.sh /path/to/skill
```

### Fix common issues automatically
```bash
./fix.sh /path/to/skill        # Interactive
./fix.sh /path/to/skill --auto # Automatic
```

### Create a new skill
```bash
./scaffold.sh my-new-skill
```

### Publish in one command
```bash
./publish.sh /path/to/skill
```

### Get quality score
```bash
./score.sh /path/to/skill
```

## The Checklist

Every skill is checked against:

1. **STRUCTURE** — Required files, logical organization
2. **SECURITY** — No secrets, keys, PII
3. **PORTABILITY** — No hardcoded paths
4. **QUALITY** — No debug code, clean formatting
5. **DOCS** — README, SKILL.md, examples
6. **TESTING** — Verified functionality
7. **GIT** — Clean history, .gitignore
8. **METADATA** — License, description

## Templates

```
templates/
├── SKILL.template.md      # Skill entry point template
├── README.template.md     # GitHub readme template
├── LICENSE.template       # MIT license
├── gitignore.template     # Standard .gitignore
├── pre-commit-hook        # Git hook for security
└── github-actions/
    └── skill-audit.yml    # CI workflow
```

### Install pre-commit hook
```bash
cp templates/pre-commit-hook /path/to/skill/.git/hooks/pre-commit
chmod +x /path/to/skill/.git/hooks/pre-commit
```

### Add CI to your skill
```bash
mkdir -p /path/to/skill/.github/workflows
cp templates/github-act...