publish-skill-to-github

# publish-skill-to-github — from working skill to repo people can safely clone Getting a skill to **work**, getting it to be **safe to publish**, and getting it to **spread** are three different crafts. This skill covers the last two. Two reframes it enforces: > **SKILL.md is written for an AI. README.md is written for a human.** Different audiences, different voices. A good SKILL.md is terse and assumes the reader is an agent following orders. A good README is evocative and assumes a developer deciding in 30 seconds whether to clone. Write twice; never let one contaminate the other. > **Your working copy is the repo.** Skills live at `~/.claude/skills/<name>/`, and that directory becomes the published repo. So every personal path, host and habit that made the skill useful to *you* is also about to become public — and to break for everyone else. De-personalization is not a nicety; it is the difference between a tool and a diary. **Scope.** Publish-time concerns only: safety gates, repo layout, README, licensing, versioning, distribution, verification. **Not** in scope: writing the skill's recipe (that is the skill's own job), or ongoing maintenance. ## When to trigger Use when the user says any of: - 「把这个 skill 放到我的 github 开源」/ "open-source this skill" - 「给这个 skill 写个 README，参考 XXX 项目的结构」 - "publish this skill as a public repo" - 「这个 skill 能发出去吗」/ "is this safe to open-source?" — the triage in Phase 1 answers exactly this Do **not** use when: - The skill has not bee...