package-public-skilllisted

# Package Public Skill Run the release pipeline that turns a private skill into a public GitHub release. Pipeline order is fixed: **evaluate → scrub → document → theme → package → stage**. Do not skip scrub. Nothing ships with unresolved scrub findings. ## 1. Evaluate Answer the four questions in `registry/pipeline.md` (worth installing? standalone? scrubbable? explainable on one page?). Any "no" → stop, report the blocker, keep the skill private. Record the verdict in the registry. ## 2. Scrub Run the scanner and resolve every finding before continuing: ```bash python3 scripts/scrub_personal.py <skill-dir> ``` - Replace personal paths with generic ones (`/Users/you/...`, `<your-project>/`). - Replace personal names/emails with the public brand contact or a placeholder. - Remove credentials outright — never allow-list a real secret. - Re-run until exit code 0. Use `--allow` only for intentional public strings (e.g. the brand name). ## 3. Document Copy from `references/` into the candidate skill root and fill every placeholder: - `readme-template.md` → `README.md` (problem, install, usage, license) - `changelog-template.md` → `CHANGELOG.md`, first entry `## [1.0.0] - <today>` - Add `LICENSE` — the owner picks per release (open or commercial). Never state a license or price on any public page that the repo doesn't actually ship with. ## 4. Theme the web page Copy `assets/site-template/` to the release's site folder and replace the `{{PLACEHOLDER}}` tokens (skill