publish-skilllisted

# Publishing skills to GitHub Procedure derived from a real publication run. The pitfalls below were hit and verified, not anticipated. ## Before you create anything Creating a public repository is an **outward-facing** action and effectively irreversible — the content reaches search engines and may be indexed even if you delete the repo later. **Ask the user two things before starting:** 1. Public or private 2. Repository name (propose a default — the skill name) Also review the skill content for anything that should not go out: paths containing the username, IP addresses from a home network, hostnames, email addresses, config fragments. What was convenient in a local note becomes a leak in a public repo. ## Repository structure ``` skill-name/ README.md ← bilingual, English first, then the other language SKILL.md ← English version SKILL.<lang>.md ← other language references/ ← scripts and supporting material ``` **Why English in `SKILL.md`:** that is the file loaded as the skill once cloned into `~/.claude/skills/`. English gives wider reach. Keep the other language beside it as `SKILL.<lang>.md` and mention it in the README. If the user works primarily in another language, keep that version locally in `~/.claude/skills/` and publish the English one. Both can coexist. ### README — what it must contain - One sentence stating what this is, at the very top - A pointer that another language