publishing-skillslisted

# Publishing Skills Take a skill that works locally but lives in a cluttered development folder, and derive a **separate, curated release repository** that a stranger can trust and install in one step. ## Core principle A published skill must satisfy **two readers at once**: 1. **The agent user** who skims the README and thinks *"I can see how that would be useful."* 2. **The skill-design expert** who inspects the repo and thinks *"this is well-structured and well-formed — I trust it because the implementation is clearly documented and tested."* Everything below serves those two judgments. Two rules are absolute: - **Never mutate the source.** The messy dev folder stays intact and private. Always work on a **copy**. The release repo is *derived*, not *moved*. - **The release is a curated subset, not a mirror.** Ship what a stranger needs to understand, trust, install, and use — nothing of the private development history. The output is a **standalone single-skill plugin repo**, provider-agnostic: a plain `SKILL.md` any agent can read, with Claude Code plugin install as additive sugar. ## When to use this (and when not) This skill is the **release/distribution last mile**. It assumes the skill already works and is good, and turns it into a clean public repo — it does **not** author or improve the skill itself. - **Publishing an existing, working skill → use this skill.** - **Authoring a new skill from scratch** (scaffold, structure, initial packaging) → use a skill-au